>> While "current" is frowned upon[0], this is not what caused your package
>> breakage. The culprit it that scripts have #!/usr/bin/pythonX.Y shebangs -
>> if they were unversioned, the package would continue to work with new
>> Python.
>
> Those are changed by python distutils, that's why a rebu
> While "current" is frowned upon[0], this is not what caused your package
> breakage. The culprit it that scripts have #!/usr/bin/pythonX.Y shebangs -
> if they were unversioned, the package would continue to work with new
> Python.
Those are changed by python distutils, that's why a rebuild fixe
"Alexandre Rossi" wrote:
>Hi,
>
>The current version of my package does not launch in unstable
>following the switch of the current python version. I think it is
>because of the "current" keyword in the "XS-Python-Version" tag. A
>rebuild fixes the problem.
>
>Is this appropriate fix?
>-XS-Pyth
* Alexandre Rossi , 2010-06-23, 10:53:
The current version of my package does not launch in unstable
following the switch of the current python version. I think it is
because of the "current" keyword in the "XS-Python-Version" tag. A
rebuild fixes the problem.
Is this appropriate fix?
-XS-Python
4 matches
Mail list logo
