-
-
Notifications
You must be signed in to change notification settings - Fork 184
Move entry_points and setup_requires to setup.cfg #176
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
Comments
So we would have to change the setuptools dependency version (currently at 30.3.0) |
@FlorianWilhelm, I am trying to implement this, but I am not sure how to proceed about Any hints? Just require sphinx anyway? |
@abravalheri, thanks for giving this a try! I think we might not even need BTW, we map the |
It seems that |
@abravalheri, thanks. I think we can close this now. We should keep in mind though that we need to remove the |
Version 3.0 of PyScaffold still has two parameters (
entry_points
andsetup_requires
) insetup.py
instead ofsetup.cfg
due to historical reasons and limitations ofsetuptools
at that point. It seems now possible according to this stackoverflow question. We should thus make use of this possibility in PyScaffold version 3.1 and also movesetup_requires
tosetup.cfg
to completely get rid of any configuration insetup.py
with the exception of Cython extensions. These will hopefully be supported in futuresetuptools
version by some syntax insetup.cfg
.The text was updated successfully, but these errors were encountered: