Migrate to hatch + modern python packaging

[Saransh-cpp]

I tested this locally, and both pip and conda builds work without any errors! To be on the safer side, could someone please test it out locally with pip and with conda (@wigging)?

[codecov]

Codecov Report

Merging #182 (f36a314) into develop (85769f2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #182   +/-   ##
========================================
  Coverage    96.65%   96.65%           
========================================
  Files           11       11           
  Lines         1197     1197           
========================================
  Hits          1157     1157           
  Misses          40       40           

[wigging]

@Saransh-cpp I can try to install this with conda and will let you know if I have any issues. Also, what is hatch?

[Saransh-cpp]

hatch is a modern build backend that handles packaging and building stuff for a python library. Most of the Python projects right now use setuptools which was the original replacement for the broken distutils backend, but the development of hatch is picking up more speed than the development of setuptools in terms of meeting the new PEPs. For instance, the editable install without a setup.py file was just introduced in setuptools, whereas it already exists in hatch - see https://peps.python.org/pep-0660/) -

(took more than a year to be introduced in the main setuptools repository) -

This will not affect the frontend or the user-facing functionalities in any way, but now hatch would be handling the packaging stuff of liionpack instead of setuptools.

[wigging]

I created a conda environment using the hatch branch and ran the basic_16p2s.py example and everything works fine.

[wigging]

Regarding modern approaches to packaging in Python. Using a src directory is the preferred approach these days.

[TomTranter]

Hi @Saransh-cpp looks good thanks for this. I tested conda install locally too