[Python-bugs-list] [Bug #129854] old PYTHONPATH confuses setup.py [build|install]
noreply@sourceforge.net
noreply@sourceforge.net
Fri, 16 Feb 2001 21:35:16 -0800
Bug #129854, was updated on 2001-Jan-23 13:18
Here is a current snapshot of the bug.
Project: Python
Category: Build
Status: Closed
Resolution: Fixed
Bug Group: None
Priority: 5
Submitted by: pj99
Assigned to : akuchling
Summary: old PYTHONPATH confuses setup.py [build|install]
Details: Some of the Makefile actions set the value of PYTHONPATH
to the python libraries being built, intentionally over-
riding the ambient value, such as in the Makefile line:
349: export PYTHONPATH; PYTHONPATH="`pwd`/Lib"; \
But the lines that invoke setup.py:
163: ./python$(EXE) $(srcdir)/setup.py build
431: ./python$(EXE) $(srcdir)/setup.py install
don't override PYTHONPATH, and when I first tried to
build and install Python 2.1, on a system configured
to be running Python 2.0, these setup lines failed,
with the complaint:
AttributeError: 'distutils.sysconfig' module has no attribute
'set_python_build'
which is a sensible complaint, given that 2.0 sysconfig
lacks 'set_python_build', 2.1 has it, and setup.py invokes
it.
Would it make sense to be overriding PYTHONPATH for these
lines of the Makefile as well?
Follow-Ups:
Date: 2001-Feb-16 21:35
By: akuchling
Comment:
Good point! Fixed in revision 1.20 of the top-level Makefile.pre.in, so
this should be correct in 2.1beta1.
-------------------------------------------------------
For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=129854&group_id=5470