-
Notifications
You must be signed in to change notification settings - Fork 262
Q: any plans/possibility to avoid patching versioneer.py? #816
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
They haven't responded to issues or PRs in years at this point. |
That said, I'm open to forking, opening a PR, and using that fork unless the fixes we need are eventually included. |
Ah, I didn't know that it is not active |
Maybe if we find that we need to hack on it again for this or another project, we could make a nipy fork to consolidate effort and get more eyes on it. |
yarikoptic
added a commit
to dandi/dandi-cli
that referenced
this issue
Sep 27, 2019
Majority of the setuptools specification is within setup.cfg, versioneer (patched, see nipy/nibabel#816 on related discussion) provides version "management", setup.py is minimalistic, pyproject.toml provides build dependencies Time will show how well it serves us ;)
jwodder
pushed a commit
to dandi/dandi-schema
that referenced
this issue
May 20, 2021
Majority of the setuptools specification is within setup.cfg, versioneer (patched, see nipy/nibabel#816 on related discussion) provides version "management", setup.py is minimalistic, pyproject.toml provides build dependencies Time will show how well it serves us ;)
Dropped versioneer. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I wondered if you (@effigies) anyhow considered/discussed with versioneer.py to make it possible to have versioneer.py needed functionality without nibabel patching it?
The text was updated successfully, but these errors were encountered: