"Martin v. Löwis" <martin at v.loewis.de> writes: > Jack Jansen wrote: >> 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. > > Why can't you configure with an entirely different --prefix, such as > /just/for/me? I think this would be tricky on OS X, which looks for frameworks in fixed places. It really would be nice to have the framework have a different name. But this may be an OS specific problem. Cheers, mwh -- ... so the notion that it is meaningful to pass pointers to memory objects into which any random function may write random values without having a clue where they point, has _not_ been debunked as the sheer idiocy it really is. -- Erik Naggum, comp.lang.lisp
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