-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyproject.toml instead of setup.py #115
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I'm in favor of this in principle (been slowly converting all of my projects to pyproject.toml).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good if all the places the version is currently hardcoded in the codebase used from importlib import metadata; version = metadata.version(__package__)
instead, to dynamically retrieve this value from pyproject.toml.
"requests", | ||
"scipy", | ||
] | ||
scripts = {slider="slider.__main__:main"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this correct? I believe this will cause a console_scripts
entry point to be installed and add an executable named slider
to the user's PATH
. This is not what slider currently does: it's invoked with python -m slider
, as on the docs.
This patch removes
setup.py
in favour ofpyproject.toml
, which follows the relatively new way of building Python packages specified by PEP-621.