[Mageia-dev] Python Packaging Policy

andre999 andr55 at laposte.net
Wed Jul 13 12:11:30 CEST 2011


philippe makowski a écrit :
> 2011/7/13 Michael scherer<misc at zarb.org>:
>>
>> I would be in favor of treating python2 and python 3 as 2 differents languages.
>> The rational is that :
>> - we cannot garantee to have support for both
>> -  we will likely have some module who would be updated only on
>> python 3 sooner or later
>> - we will need to do upgrade of package at different time, since both python2 and python3 are
>> released at different time.
>>
>> So rather than a complex scheme that will confuse packagers, just consider they
>> are separate, and use the almost same policy ( with s/python/python3/ )
> And how do you manage package that support both P2 and P3 ?
> (same source)

If we use misc's approach, we could minimize the urgency of the conversion.
If upstream supports both, we could either add a virtual provides in P2 and P3 
for that (to be used only by such packages), or support just P3 (or maybe just P2).
I don't know which is best, but I'd still like to help out.

>> Regarding a review of all package, that sound like daunting task :/
> yes, but do you see another solution ?
> we can have a priority list

-- 
André


More information about the Mageia-dev mailing list