MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/Python/comments/8fztrr/xkcd_python_environment/dy9g2l3/?context=3
r/Python • u/themonsterpus • Apr 30 '18
388 comments sorted by
View all comments
Show parent comments
0
It can.
mkproject NewProject pip install whatever # Running code later on python /path/to/NewProject/code.py
0 u/leom4862 May 01 '18 And how do you manage dependency version conflicts? 1 u/[deleted] May 01 '18 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. 1 u/leom4862 May 01 '18 What do you do if project A relies on FooPackage version X and proejct B relies on FooPackage version Y? → More replies (10)
And how do you manage dependency version conflicts?
1 u/[deleted] May 01 '18 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. 1 u/leom4862 May 01 '18 What do you do if project A relies on FooPackage version X and proejct B relies on FooPackage version Y? → More replies (10)
1
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.
1 u/leom4862 May 01 '18 What do you do if project A relies on FooPackage version X and proejct B relies on FooPackage version Y? → More replies (10)
What do you do if project A relies on FooPackage version X and proejct B relies on FooPackage version Y?
→ More replies (10)
0
u/[deleted] May 01 '18
It can.