Created on 2008-12-14 01:31 by jah, last changed 2010-11-18 01:46 by eric.araujo.
| Messages (3) | |||
|---|---|---|---|
| msg77771 - (view) | Author: Jake (jah) | Date: 2008-12-14 01:31 | |
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 |
|||
| msg108717 - (view) | Author: Mark Lawrence (BreamoreBoy) | Date: 2010-06-26 12:22 | |
Could an installation guru please take a look at this? |
|||
| msg121408 - (view) | Author: Éric Araujo (eric.araujo) *  |
Date: 2010-11-18 01:46 | |
Not reading .pydistutils.cfg during CPython’s build seems a good idea to me. I would like confirming opinions. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-11-18 01:46:32 | eric.araujo | set | versions:
+ Python 3.1, Python 2.7, Python 3.2, - Python 2.6 nosy: + barry, eric.araujo, loewis messages: + msg121408 components: + Build |
| 2010-06-26 12:27:50 | l0nwlf | set | nosy:
+ tarek |
| 2010-06-26 12:22:41 | BreamoreBoy | set | nosy:
+ BreamoreBoy messages: + msg108717 |
| 2008-12-14 01:37:40 | jah | set | title: setup.py should not use .pydistutils.cfg -> during Python installation, setup.py should not use .pydistutils.cfg |
| 2008-12-14 01:31:04 | jah | create | |