3 ms·

You're doing God's work, man. Thank you for helping me avoid that headache. I'm sticking with pip

• yrro 8y ago
  I wouldn't go that far. I would absolutely love for some tool, and pipenv as as fine as any other, to replace everything else. But right now it doesn't seem to be ready.
  • scrollaway 8y ago
    It's absolutely not ready, as I made clear in several comments :) I just said pipenv is the most promising one. I agree it's frustrating. I'm planning to donate some of my time to the project to help the situation. I hope others can too.
    • yrro 8y ago
      Well I filed these as bugs this morning and got mixed feedback; the 'install -e .' but was caused by a stale Pipefile in the parent directory that I did not create, but at least removing it makes things work. Unfortunately upstream does not consider a stale copy of the python interpreter copied to dozens of directories on the filesystem that will never be patched to be an issue, so from my PoV pipenv gets a big raspberry and I'll stick with manually running 'python -m venv' which has gotten this right since Python 3.3!