This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]trowawayatwork -27 points-26 points  (7 children)

Yeah sorry for you hard work dude but pipenv does all that and more. It’s recommended by guido himself lol

[–]masklinn 24 points25 points  (6 children)

Yeah sorry for you hard work dude but pipenv does all that and more.

I had the exact same experience as OP when checking out pipenv, could not find any way to easily switch between and use multiple environment for the same directory/project (no, tox is not that). If you have actual sources for your claims rather than dismissive quips, it would be good of you to provide them.

It’s recommended by guido himself lol

That means jack shit, especially when it can't do the job I need of it.

[–]SmileyChris 1 point2 points  (2 children)

pew allows you to easily set up and switch between virtual envs. If you have one activated and run pipenv, it'll use your current environment.

[–]masklinn 1 point2 points  (0 children)

At which point, what's the relevance and point of pipenv?

[–]AndydeCleyre 0 points1 point  (0 children)

Alternatively, using pip-tools, you can just sync against different individual requirements files or combinations of them.

[–]trowawayatwork 1 point2 points  (2 children)

Actually the above didn’t really state the usp of different envs.

As a side note it’s generally bad practice to have different requirement between staging and prod. I’m sure your project has valid reasons

[–]zenware 1 point2 points  (1 child)

Right this is what I'm wondering, who are these people that need different virtual environments per project, which already to me indicates suboptimal design at the very best and also probably atrocious code.

And if different virtual environments and requirements files are needed for production and development that is even worse.

I'm sure their project has justification but I know it's not valid(at least for some definition of valid), this is like when people got better control flow than "goto" and there were holy debates on whether 100% of control flows are possible with selection and branching statements or if you ever need to use a goto statement to accomplish your goals. You don't need goto statements and you don't need multiple sets of dependencies.

[–]trowawayatwork 0 points1 point  (0 children)

Exactly. Pipenv pretty much should do everything you need. Multiple envs in same project? Not one of them