-
Notifications
You must be signed in to change notification settings - Fork 391
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
PEP517 #537
Comments
@Alessandro-Barbieri, could you take a look at the changes on the branch https://github.com/ncclient/ncclient/tree/einarnn-pep517 Thanks! |
We already have versioneer installed sistem wide and your vendored versioneer is clashing with it |
I always package ncclient in an isolated environment to avoid clashes. I have attached a source tar.gz file you can try installing if you like. I am not an expert on the implications of PEP517 or exactly what problems are being caused overall by the way we use versioneer, so if you have explicit feedback on changes you would recommend, I'd be happy to get that. Please feel free to try this: ncclient-0.6.13 5.g3b2cd19.tar.gz
|
Or this one: ncclient-0.6.13 6.g2413a91.tar.gz |
In gentoo we use system packages and we don't use pip for installing
|
@Alessandro-Barbieri, the changes I have made seem to work in a fairly standard environment, and the I am not an expert in Python packaging, and I am not currently prepared to roll back the use of However, I am open to any suggestions PRs related to my perhaps incorrect updates on the branch |
Don't use gpep517. Try this instead: remove versioneer.py and install this versioneer instead https://github.com/python-versioneer/python-versioneer They define |
Could you move the buildsystem to PEP517?
The text was updated successfully, but these errors were encountered: