Requirements should be for `path` not `path.py` and then other errors

[psycojoker]

Requirements should be for `path` not `path.py` and then other errors

[QSchulz]

I wanted to play and at least test this out since your example gallery isn't working (another issue).

Please give us more info on that.

Using path.py, it found some super old version that doesn't work. I changed it to path and it worked fine.

Thanks for this report. I think it would make sense to send a Pull Request for that. Though, I can already tell you I'll comment asking whether we couldn't use pathlib instead (which is a standard library, so does not need to be added to requirements.txt).

Since path.py has been replaced by path, I'd expect it to keep compatibility.

I suspect that is because the .egg is a zipfile so you need to open it that way.

Just tried on a clean virtualenv on Linux and cannot reproduce. Can you still reproduce today? Wondering how pip treats packages which failed to install since you manually fixed it after it failed.

[Jwink3101]

It has been a (long) while since I wrote this and it looks like the code has changed a lot since then. Based on the dates, this was from 0c6e83fd7.

Also, I don't recall the details but I agree strongly that if you require python 3.4+, you should be using pathlib!

I don't know how pip will treat a missing package or how your code will work with stdlib pathlib (probably fine?)

I can try again later when I am home.

[twdragon]

Confirmed for master, fixed by replacement of path.py module name with just path. Need to be fixed ASAP