I've been looking through a few F4E repos recently and I see most have setup.py or setup.cfg files. I noticed this one also has a partial pyproject.toml file. We could move these setup files entirely to pyproject.toml files to keep up to date with the latest python packaging recommendations
While updating we could also move to a src/jade layout instead of the jade folder structure. The version could be moved to the pyprojects and we could make use of import importlib.metadata to make the jade.__version__ attribute or if we are really keen then we could make use of the setuptools_scm to track the version for us.
Describe the solution you'd like
pyproject.toml instead of setup.py + setup.cfg
src/jade instead of jade folder structure
importlib.metadata or setuptools_scm to get version number
Describe alternatives you've considered
could also leave things as they are
Additional context
while setup.py is not depreciated the command commonly associated with a setup.py file python setup.py install is now depreciated and pyproject.toml is "strongly recommened" for python packaging
I've been looking through a few F4E repos recently and I see most have setup.py or setup.cfg files. I noticed this one also has a partial pyproject.toml file. We could move these setup files entirely to pyproject.toml files to keep up to date with the latest python packaging recommendations
While updating we could also move to a
src/jade
layout instead of thejade
folder structure. The version could be moved to the pyprojects and we could make use ofimport importlib.metadata
to make thejade.__version__
attribute or if we are really keen then we could make use of the setuptools_scm to track the version for us.Describe the solution you'd like
Describe alternatives you've considered could also leave things as they are
Additional context while setup.py is not depreciated the command commonly associated with a setup.py file
python setup.py install
is now depreciated and pyproject.toml is "strongly recommened" for python packaging