On Wed, Jun 30, 2010 at 02:12:18PM +0200, Stefano Rivera wrote:
Would you happen to know if that option is new or we can safely use this also for e.g. backports?I don't know. I need to do some more historical research.
ok.
Would it perhaps be better to always pass this option, also for specific versions of Python?The problem isn't with versions of python, but the different libraries that setup.py may be using.
It seems we are talking about different things: I proposed that (in the cases where your proposed option works) not only the unversioned python path is ensured when using the default Python, but also the versioned python path is used when using a non-default Python (e.g. for a project where Python 2.6 is not supported, built for a system where Python 2.6 is the default compiler).
It looks like I need to do some more testing, I've found some packages that would FTBFS with this.
Too bad.Even if you cannot solve it, please do post more details about it, in case others reading this might have ideas.
Regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
