-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Use static setuptools metadata #1116
Conversation
Yeah, I still use bumpversion. I'd like to use it on other projects as well too. I'm going to target a future release for this work, after we get a 1.0 release out with some of the current work pending. |
Reported the bumpversion issues here #1117 |
7dda1fe
to
1421fb5
Compare
Rebased on top of |
😄 @agjohnson - just stumbled upon gold here, the bumpversion issues that got introduced in package-lock.json are already |
Updated to latest master. I've included the Jinja fix from #1316. |
f13e6d8
to
68aed97
Compare
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.
This is really nice work 💯 looking forward to getting rid of setup.py all-together.
I'll do a version bump in another PR, so I might move the version to setup.cfg there.
@@ -86,73 +86,11 @@ def run(self): | |||
|
|||
|
|||
setup( | |||
name='sphinx_rtd_theme', | |||
version='1.0.1alpha1', |
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.
Shouldn't we also have the version in setup.cfg?
This migrates most of the metadata keys to the new static/declarative
setup.cfg
.Also, I tried fixing the bumpversion configuration, but when I tried
bumpversion micro
it introduced a few bugs in thepackage-lock.json
and whitespace changes insetup.cfg
, so I am not sure if we are still using it.