I recommend not setting these variables at all, or to use wrapper scripts that set them instead. But there's probably some reason why you can't do that... On 3/8/07, Anthony Baxter <anthony at interlink.com.au> wrote: > What do people think about the idea of a version-specific PYTHONPATH > environment variable? Something like PYTHON25PATH or the like. > Reason I ask is that on our production systems, we have a couple of > versions of Python being used by different systems. Yes, yes, in a > perfect world they'd be all updated at the same time, sure. There's > occasionally issues with the PYTHONPATH being pointed at something > like .../lib/python2.4/site-packages or the like, and then have > issues when python2.3 or some other different version is run. If we > allowed people to optionally specify a more specific version this > problem would go away. > > Anthony > -- > Anthony Baxter <anthony at interlink.com.au> > It's never too late to have a happy childhood. > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4