-
Notifications
You must be signed in to change notification settings - Fork 156
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
versioneer doesn't work on recent pip when PEP 517 build is triggered #192
Comments
It's not |
@daa adding https://github.com/warner/python-versioneer#quick-install If you read the linked pip comment, it explicitly says that "pandas has a versioneer.py sitting next to setup.py", so it's not a telluric problem. |
@Juanlu001 You are right, my comment wasn't thoughtful enough. |
I can confirm this and additionally it was introduced with pip version 19. This works fine <19.
|
so what would be the best workaround ATM? |
I don't know exactly since which version of pip but versioneer works again for me (19.2.3). |
…port Unfortunately I did not find a better solution for a still open python-versioneer/python-versioneer#192 so we might just reconsider (not) using versioneer altogether in the future
I got this same error when installing the DonkeyCar 3. code on the Nvidia Nano: I had downgraded to pip 19.0 to get around the following error in pip 20.0.2: I also tried 19.2.3 and got the same legacy error above. Anyone have any suggestions? |
Weird, I'm using pip>20 now and it works just fine with versioneer. Did you try to upgrade your setuptools version, too? |
@dmccreary I am having the same problem. I am trying to install DonkeyCar. I downgraded to pip 19 after having AttributeError: module 'setuptools.build_meta' has no attribute 'legacy' error. Did you have any solution to this issue ? |
I'm having a similar issue as well with the Donkey Car. Did anyone find a solution yet? |
Could people affected by this issue try this? |
Hi @astrojuanlu,
I tried this solution you suggest and it worked fine. Unfortunately, it's in one of my company's private repositories. Would you like the pip output in verbose mode? |
Thanks @KikeM! No need to, I was about to ask the original reporter to close this issue... but it's me 🤡 closing! |
…port Unfortunately I did not find a better solution for a still open python-versioneer/python-versioneer#192 so we might just reconsider (not) using versioneer altogether in the future
See for example:
(by @guydou)
The root cause is this one: pypa/pip#6163, see for example:
The text was updated successfully, but these errors were encountered: