On 19Mar2015 19:57, Sturla Molden <sturla.mol...@gmail.com> wrote:
Orion Poplawski <or...@cora.nwra.com> wrote:
It would be good to get some feedback from the broader python community
before implementing anything, so I'm asking for feedback here.
On my systems I have /use/bin/python for the system and ~/anaconda/python
for me. Apple and Ubuntu can do whatever they want with their Python's, I
am not touching them. The main thing is to keep the system Python and the
user Python separate. That is, both the executable and the folder where
packages are installed. Whatever I install for myself can fuck up
~/anaconda, but is not allowed to mess with the system files or system
folders.
Me too. I keep my default virtualenvs in ~/var/venv, and have personal "py2"
and "py3" scripts that invoke via the venvs.
Having a similar separation in the system would be a good thing, for the same
reasons.
Also, it would let the OS supplier keep a _much_ smaller package/addon list for
the "core" admin python instance, making QA etc easier and more reliable.
Popular OSes let the local sysadmin (== "the user") pull in all sorts of stuff
to the "system" Python, even from the supplier's repositories. Having a walled
off "core" admin python as well seems very prudent.
Cheers,
Cameron Simpson <c...@zip.com.au>
conclude that this language as a tool is an open invitation for clever
tricks; and while exactly this may be the explanation for some of its appeal,
/viz./ to those who like to show how clever they are. I am sorry, but I must
regard this as one of the most damning things that can be said about a
programming language.
- Edsger Dijkstra, _The Humble Programmer_ (CACM, Ocotber, 1972)
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
