@ziatdinovmax I have a couple of suggestions for your consideration:
Pool all setup protocol into pyproject.toml. PEP 621 began the transition of Python setup to the "non-python" pyproject file. In GPax, the setup.py file is not necessary. We can pool all build instructions into the pyproject.toml file.
CI code can be slightly refactored for clarity.
Similarly, I have developed a procedure for on-the-fly semantic versioning from tags, similar to the old versioneer.py method, but my method is a few lines and relies on dunamai to grab the current HEAD's tag. I use this combined with "API-key-free" publishing to PyPI, my CI procedure, and GH environments to securely publish any new tagged release. The environment configuration requires manual confirmation before any release, in case you were worried about over-automation causing unintended things to happen. EDIT: there is a better way to do this using hatchling. See here.
Implement dependabot for automatic version bumps, and version-lock all dependencies. I think this is just good practice to ensure your code works even if a dependency releases an update that should be backwards compatible, but isn't. Example of that here.
The most recent example I have of all of this can be found here, with a slightly less recent example here.
I am more than happy to implement these QOL changes.
@ziatdinovmax I have a couple of suggestions for your consideration:
pyproject.toml. PEP 621 began the transition of Python setup to the "non-python" pyproject file. In GPax, thesetup.pyfile is not necessary. We can pool all build instructions into thepyproject.tomlfile.Similarly, I have developed a procedure for on-the-fly semantic versioning from tags, similar to the oldEDIT: there is a better way to do this usingversioneer.pymethod, but my method is a few lines and relies on dunamai to grab the current HEAD's tag. I use this combined with "API-key-free" publishing to PyPI, my CI procedure, and GH environments to securely publish any new tagged release. The environment configuration requires manual confirmation before any release, in case you were worried about over-automation causing unintended things to happen.hatchling. See here.The most recent example I have of all of this can be found here, with a slightly less recent example here.
I am more than happy to implement these QOL changes.