-
Notifications
You must be signed in to change notification settings - Fork 84
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
Replace path.py with path #174
Conversation
Ah, I see... |
Per the history, Python 2.7 support was dropped in 13.2, but the project was renamed in 13.0. That should mean that 13.0 and 13.1 should be installable on Python 2.7. However, when I went to confirm this fact, I found that indeed no version of path is installed:
That's a bug. Correction: Support for Python 2.7 was dropped in 12.0. It was in 13.2 that support for Python 3.5 was dropped. |
Thanks @jaraco for digging into this. Since Python 2.7 is so ancient, I wonder if pytest-plugins will drop support so this PR can be merged? |
Co-authored-by: Jason R. Coombs <jaraco@jaraco.com>
Many thanks for your contribution. We're currently working on dropping support for Python 2.7 so a lot of these sorts of issues should be cleared up soon. |
Unless there's some obscure backwards-compatibility reason, I think you should import path instead of path.py.
This actually leads to a problem downstream on conda-forge: since the conda-forge path.py package is just a wrapper for path, no package named path.py is installed, leaving pip in an inconsistent state due to this package's explicit dependence on path.py.
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=286865&view=logs&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=e5c8ab1d-8ff9-5cae-b332-e15ae582ed2d&l=210