"Maciej (Matchek) BliziƄski" <[email protected]> writes:

> 2013/7/19 Peter FELECAN <[email protected]>
>> (snip)
>> 3. 2.7 becomes the default python for our distribution, thus new
>>    packages depends on it and the gar python recipe adapts to this but
>>    using CSWpy- prefix; I'm hesitating to add that we can obsolete
>>    CSWpython-xxx by CSWpython27-xxx
>
> I can imagine the following scenario:
>
> User: I upgraded CSW stuff and my application is not working, it fails
> with "ImportError: No module named foo"
> Us: Which Python are you using?
> User: Python 2.6
> Us: We made Python 2.7 the default and we're removing Python 2.6 support.
> User: But my application requires Python 2.6.
> Us: Then update your application.
> User: It's a third party application, we cannot modify it.

What about this:

> 2013/7/19 Peter FELECAN <[email protected]>

>> I'm still hoping that someone explains me why code written for 2.6
>> cannot be run by a 2.7 interpreter.

which is, I think, crucial to our discussion.
-- 
Peter
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
.:: This mailing list's archive is public. ::.

Reply via email to