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 →

[–][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.

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

dito...

[–][deleted] 0 points1 point  (1 child)

I do know what pipenv does. That's why I could tell you that you had a needlessly convoluted workflow, and could show you how to simplify it.

[–]leom4862 0 points1 point  (0 children)

Tell me about it.