mwh@users.sourceforge.net writes: > Index: sysconfig.py > =================================================================== > RCS file: /cvsroot/python/python/dist/src/Lib/distutils/sysconfig.py,v > retrieving revision 1.44 > retrieving revision 1.44.6.1 > diff -C2 -d -r1.44 -r1.44.6.1 > *** sysconfig.py 6 Dec 2001 20:51:35 -0000 1.44 > --- sysconfig.py 7 Oct 2002 10:38:33 -0000 1.44.6.1 > *************** > *** 24,40 **** > EXEC_PREFIX = os.path.normpath(sys.exec_prefix) > > ! # Boolean; if it's true, we're still building Python, so > ! # we use different (hard-wired) directories. > ! > ! python_build = 0 > ! > ! def set_python_build(): > ! """Set the python_build flag to true. > > ! This means that we're building Python itself. Only called from > ! the setup.py script shipped with Python. > ! """ > ! global python_build > python_build = 1 Hmm, I wonder if I should put a do-nothing set_python_build back in for 2.2.2. Does anyone call this from their build scripts? I guess it's possible... Cheers, M. -- GET *BONK* BACK *BONK* IN *BONK* THERE *BONK* -- Naich using the troll hammer in cam.misc
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