News for hackers. Stuff that matters.
Re:Python Environment by collyw on Monday April 30, 2018 @01:46PM (#16960673)
As a Python dev it looks like I need to do some reading as I am still using virtualenv (it usually works fine but I have do encounter the occasional issue).

Can anyone give me a rundown of the benefits of other systems over virtualenv?

On a side note I hope Python isn't going to turn into a shambles like JavaScript - its certainly starting to look like it as far as package managers go.

Re:Python Environment by scrollaway on Tuesday May 01, 2018 @03:45AM (#16965262)
JS isn't in shambles; in fact, their package manager situation is excellent: Use yarn, period. It could be better (yarn isn't default yet), but I would love for the Python ecosystem to get to: "Use pipenv and setup.cfg, period".

But as I said, it's too young. If you use pipenv, you still have to interact with pip, so that's two binaries whose commands you have to remember. And urgh, it's so slow. And it's kinda useless for libraries... pipenv doesn't publish stuff, pipfiles aren't appropriate for packages.

But we'll get there. One day. Hopefully it won't be too late.

Re:Python Environment by collyw on Tuesday May 01, 2018 @07:30AM (#16966144)
So what are the benefits over virtualenv? You have given me the downside of another binary to manage. What do I get in return?
Re:Python Environment by scrollaway on Wednesday May 02, 2018 @02:57AM (#16974739)
I've not given you anything other than a warning that it's too young.

Pipenv is promising. That means at some point I'm fairly certain it'll be and deserve to be the standard in Python packaging. In the mean time, it doesn't.

Re:Python Environment by collyw on Wednesday May 02, 2018 @05:43AM (#16975382)
That still doesn't answer the question of what it will (eventually) give me over virtualenv.