[New-bugs-announce] [issue4655] setup.py should not use .pydistutils.cfg
Jake
report at bugs.python.org
Sun Dec 14 02:31:05 CET 2008
New submission from Jake <jah.mailinglist at gmail.com>:
When installing python 2.6, I used:
./configure --prefix=/home/name/usr
Installation was fine and everything was installed to:
~/usr/lib/python2.6
But the .so files were installed to:
~/usr/lib/python
As ~/usr/lib/python was (no longer) declared in my PYTHONPATH, I ran
into import issues. The problem was due to a forgotten file:
~/.pydistutils.cfg
So this is clearly a user error, but I wonder if it is something which
should be avoided at the setup.py level.
When installing python, the installation locations are derived from the
results of ./configure. When setup.py is eventually called, the
installation locations can change. This seems undesirable. Would it be
better if setup.py instructed distutils to ignore any configuration file
so that the installation directories matched what was used by the rest
of 'make install'?
Related: http://bugs.python.org/issue1180
----------
components: Installation
messages: 77771
nosy: jah
severity: normal
status: open
title: setup.py should not use .pydistutils.cfg
type: behavior
versions: Python 2.6
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue4655>
_______________________________________
More information about the New-bugs-announce
mailing list