[arch-general] Using "python3 setup.py" in PKGBUILDs

[Auguste Pop]

On Mon, Apr 11, 2011 at 9:40 AM, Allan McRae <allan at archlinux.org> wrote:
> On 11/04/11 10:48, Oon-Ee Ng wrote:
>>
>> On Mon, Apr 11, 2011 at 6:57 AM, Aaron DeVore<aaron.devore at gmail.com>
>>  wrote:
>>>
>>> I recently started creating/maintaining packages for the AUR. One
>>> request I've run up against is allowing users to relink
>>> /usr/bin/python to /usr/bin/python2, but still have package building
>>> work. Apparently the current policy is to use "python setup.py" for
>>> Python 3 packages, but that breaks Python 3 package building for users
>>> who relink. Using "python3 setup.py" fixes that problem.
>>>
>>> Could that policy change? I searched around for a conversation, but
>>> couldn't find anything. Also, the policy itself is undocumented in the
>>> wiki and /usr/share/pacman/PKGBUILD-python.proto.
>>>
>>> -Aaron DeVore
>>>
>> AFAICR users who relink python to python2 are on their own. This
>> breaks repo packages as well, not just AUR packages.
>>
>
> Correct.  This currently breaks all sort of stuff so is completely
> unsupported.
>
> Allan
>

relinking python is a bad idea, but imho, explicitly envoking python3
when packaging it not.
using python to install python3 packages is like linking to foo.so
instead of foo.so.3.