When I wanted to set PYTHONPATH I had the advantage of
knowing nothing about how Linux/Ubuntu was supposed to work,
so I tried everything. ~/.profile worked for me.
In article mailman.670.1251592772.2854.python-l...@python.org,
Chris Colbert sccolb...@gmail.com wrote:
I'm having an issue with
I don't want to have to modify the path in each and every application.
There has to be a way to do this...
Personally, I don't agree with the Debian maintainers in the order
they import anyway; it should be simple for me to overshadow system
packagers. But that's another story.
P.S. my first
Chris Colbert wrote:
Is there a way to fix this so that the local dist-packages is added to
sys.path before the system directory ALWAYS? I can do this by editing
site.py but I think it's kind of bad form to do it this way. I feel
there has to be a way to do this without root privileges.
Any
Great! That was the solution I was looking for. Thanks!
Chris
On Sun, Aug 30, 2009 at 12:29 PM, Christian Heimesli...@cheimes.de wrote:
Chris Colbert wrote:
Is there a way to fix this so that the local dist-packages is added to
sys.path before the system directory ALWAYS? I can do this by
I'm having an issue with sys.path on Ubuntu. I want some of my home
built packages to overshadow the system packages. Namely, I have built
numpy 1.3.0 from source with atlas support, and I need it to
overshadow the system numpy 1.2.1 which I had to drag along as a
dependency for other stuff. I
On Aug 29, 5:39 pm, Chris Colbert sccolb...@gmail.com wrote:
I'm having an issue with sys.path on Ubuntu. I want some of my home
built packages to overshadow the system packages. Namely, I have built
numpy 1.3.0 from source with atlas support, and I need it to
overshadow the system numpy 1.2.1
