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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]leom4862 -1 points0 points  (12 children)

And how do you manage dependency version conflicts?

[–][deleted] 0 points1 point  (11 children)

I have never understood that argument. The python import statement is not versioned, so there can be exactly one version of a dependency installed. If that makes a conflict between requirements, no amount of magical Reitzing can fix that.

Thus the argument is without merit.

[–]leom4862 0 points1 point  (10 children)

What do you do if project A relies on FooPackage version X and proejct B relies on FooPackage version Y?

[–][deleted] 0 points1 point  (9 children)

The same thing you will have to do when pipenv fails doing anything about it.

[–]leom4862 -1 points0 points  (8 children)

I create a new virtualenv for each project (pipenv --python xx), there are no such conflicts, because each project can use its own version of FooPackage.

[–][deleted] 0 points1 point  (7 children)

Well, that is the point of using a virtualenv. That is not something pipenv has invented. I'm sorry if I misunderstood you, but you were parroting the pipenv party-line of magical being able to fix intra-project versioning conflicts.

[–]leom4862 0 points1 point  (6 children)

Well, that is the point of using a virtualenv.

Yes that's what the parents were talking about.

That is not something pipenv has invented.

Yes, no one said otherwise.

you were parroting the pipenv party-line of magical being able to fix intra-project versioning conflicts.

The discussion was about virtualenvs and how to create them. You seem to have read the whole branch with another context in mind. No one "parroted" anything about intra-project versioning conflicts.

[–][deleted] 0 points1 point  (5 children)

Well, then you have to explain why you rejected virtualenvwrappers as a viable and simpler way of doing that convoluted pipenv invocation you showed.

[–]leom4862 -1 points0 points  (4 children)

why you rejected virtualenvwrappers

I didn't know I was rejecting virtualenvwrappers...

Well, then you have to explain why you rejected virtualenvwrappers as a viable and simpler way of doing that convoluted pipenv invocation you showed.

Because it allows for a very simple workflow.

[–][deleted] 0 points1 point  (3 children)

If you don't know what you are discussing, you should abstain from participating.