On Jan 21, 2004, at 11:08 AM, Jack Jansen wrote: > This idea is only half-baked, so please fire away, or tell me to go > ahead, or go hide under a stone. > > I would like a configure option that changes the name of "python" > everywhere: in the executable, in the dynamic library name, the MacOSX > framework name, etc. This would allow you to have two Pythons on a > system that are completely 100% independent of each other. > > The idea was triggered by Michael Hudson, who wanted to install a > debugging-enabled framework build of Python on MacOSX, which shouldn't > interfere with the normal Python (either Apple-installed or > user-installed). It turns out this is doable through meticulous > hacking of the Makefile after configure (and, for now, ignoring the > few hardcoded "Python.framework" references in Lib, but those need > fixing anyway). For other unix systems a similar approach would work > to isolate a debug-python from the normal production python. > > But then I thought of another use: this would allow you to have a > MacPython 2.3.3 distribution as well as the Apple-installed 2.3 > distribution without any interference possible. And there are probably > similar uses on other platforms. I'm +100000 on this; it's good for MacPython, python-dev'ers, and it would also help forks like stackless. -bob
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