Skip to content
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

Switch to setuptools-scm instead of versioneer. #1545

Merged
merged 1 commit into from
Jul 14, 2020

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Apr 30, 2020

Rationale

Versioneer seems to break with PEP517 and newer packaging tools. The supported tool is setuptools-scm.

Implications

Better-working installs.

@greglucas
Copy link
Contributor

Overall looks good to me and a positive to get rid of the forked versioneer code, but I'm not an expert on packaging at all. Do we need to pin setuptools_scm to a minimum version or anything like that to still work with Python 3.5 for now?

@dopplershift
Copy link
Contributor

I like the change. This is what I've switched to elsewhere.

@QuLogic
Copy link
Member Author

QuLogic commented Jul 13, 2020

Well, CI passes, so I guess 3.5 should be fine? Anyway, if we do #1518, we won't have to worry about 3.5.

Copy link
Contributor

@dopplershift dopplershift left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say go ahead and merge. If this is done @QuLogic go ahead and self-merge I'd say.

@QuLogic QuLogic merged commit 54ec20d into SciTools:master Jul 14, 2020
@QuLogic QuLogic deleted the setuptools-scm branch July 14, 2020 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants