[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 'python-build-system'
From: |
Ludovic Courtès |
Subject: |
Re: 'python-build-system' |
Date: |
Thu, 09 May 2013 22:29:28 +0200 |
User-agent: |
Gnus/5.130005 (Ma Gnus v0.5) Emacs/24.3 (gnu/linux) |
Nikita Karetnikov <address@hidden> skribis:
>> With these changes in place, OK to commit.
>
> I've just pushed both patches. Please have a look.
>
>> To answer your previous question, this ‘wrap’ phase serves a different
>> (but related) purpose than the ‘native-search-paths’ thing: it ensures
>> that the ‘bzr’ program, when run by the user, finds all its Python
>> modules.
>
> I know. But why do we need to use 'native-search-paths' to set
> PYTHONPATH if we wrap all executables anyway? What is the purpose of
> 'native-search-paths' in this case?
Not all Python packages have binaries, and when they do, they can often
be used either as stand-alone binaries or as Python modules.
Does that clarify?
Ludo’.