Python conflicting with other python when installed from packages

[Ruslan Mahmatkhanov]

John Hein wrote on 05.06.2012 21:09:
> Ruslan Mahmatkhanov wrote at 16:14 +0400 on Jun  5, 2012:
>   >  Baptiste Daroussin wrote on 05.06.2012 16:07:
>   >  >  Hi,
>   >  >
>   >  >  With pkgng build on pointyhat I discovered that all the python packages when
>   >  >  built on pointyhat, tinderbox or even poudriere all conflicts which each other
>   >  >  meaning you can't install multiple python version in parallel without
>   >  >  overwritting files with old package system and pkgng just forbid you to install
>   >  >  the second package to avoid overwritting the file.
>   >  >
>   >  >  The thing is that they are conflicting only for the bin/2to3 file. It would be
>   >  >  nice if this file could be for example prefixed with the release of python like:
>   >  >
>   >  >  bin/py27-2to3 or something like that. I'm aware that when just installing from
>   >  >  ports only the first version of python installed got it, but if you are thinking
>   >  >  in package only world it can't works that way.
>   >  >
>   >  >  regards,
>   >  >  Bapt
>   >
>   >  Packages that using 2to3 to convert their code on install to be python3
>   >  compatible looking exactly for `2to3' executable. So such a modification
>   >  would require modifying all the setup.py's according the python version
>   >  user has installed as default. It's just a though. I didn't see how to
>   >  resolve this correctly.
>
> One way: pull out 2to3 to its own separate port and have those
> ports that need it specify the dependency.  And, no, I don't
> have patches.

Well, then we'll get separate 2to3 ports that is conflicting :). I'm not 
sure that 2to3 is the same in all python distributions.

-- 
Regards,
Ruslan

Tinderboxing kills... the drives.