On Fri, Sep 25, 2009 at 7:22 AM, Stefan Teleman
<stefan.teleman at gmail.com> wrote:
> On Thu, Sep 24, 2009 at 23:37, Cyril Plisko <cyril.plisko at mountall.com>
> wrote:
>> On Fri, Sep 25, 2009 at 5:23 AM, Stefan Teleman
>> <stefan.teleman at gmail.com> wrote:
>>> Webrev at:
>>>
>>> http://cr.opensolaris.org/~steleman/6751764/
>>
>> Stefan,
>>
>> I see you are using python 2.4 for Python stuff. Shouldn't it be 2.6
>> instead ? I believe the policy was to incrementally migrate all the
>> new/updated things to python 2.6 and optionally deliver support for
>> previous (2.4 and 2.5) versions.
>
> That would require an updated ARC Case, because i would be removing
> SVN interfaces from Python 2.4 and introducing them in Python 2.6, and
> the point right now is to upgrade and provide a recent version of
> Subversion.
You may elect to provide both :)
> Python 2.4 isn't going away any time soon, and we don't have hard and
> fast rules about abandoning Python 2.4 and moving everything to 2.6.
>
It worth noting, however, that PSARC 2009/043 declares Python 2.4 obsolete.
>From that case materials:
Projects delivering Python modules are required to deliver them
for all non-Obsolete versions of Python that are shipped on the
system. New projects do not have to deliver Python modules for
Obsolete versions, but existing modules must be delivered for
all versions.
It looks like the language used there doesn't leave you too much room
for maneuvering.
--
Regards,
Cyril
