Closed AliaumeL closed 2 years ago
@AliaumeL Is there a reason why you're using setup.py
instead of setup.cfg
? Using the latter is recommended by https://packaging.python.org/en/latest/tutorials/packaging-projects/#configuring-metadata
@AliaumeL Is there a reason why you're using
setup.py
instead ofsetup.cfg
? Using the latter is recommended by https://packaging.python.org/en/latest/tutorials/packaging-projects/#configuring-metadata
You are right, it was because I am used to setup.py
and it has syntax highlighting/linting/completion in my editor. As it contains roughly the same options and should not be modified so often I am not against the setup.cfg
file.
This PR contains several key changes
pkg_resources
setup.py
virtualenv
As this PR mostly moves files around and does not remove « old code » from the
knowledge.py
file I believe it should be accepted as-is, with the promise of getting rid of legacy code in the future.