[petsc-dev] Python 2.2

[Matthew Knepley]

So if RHEL supports it for 20 years, we should?

  Matt

On Wed, Feb 3, 2010 at 11:29 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
>  We should keep it. The important date is not when  new feature is
> introduced but when the packagers actually distribute it.
>
>   Barry
>
> On Feb 3, 2010, at 9:57 AM, Satish Balay wrote:
>
>  On Wed, 3 Feb 2010, Matthew Knepley wrote:
>>
>>  The last release of Python 2.2 was May 30, 2003. The fixes Satish
>>> has just put in are pretty ugly. At what point do we give up on an
>>> antiquated Python?
>>>
>>
>> I think its good if we can keep configure working for a wide rane of
>> python versions [whatever the user has].
>>
>> One timeline we can use is - RHEL/CentOS EOL dates. RHEL3/CentOS3 with
>> python2.2 is supported till Oct 31, 2010, RHEL4/CentOS4 with default
>> python2.3 is supported til Feb 29, 2012.
>>
>> Or drop python2.2 for next release... Barry can decide...
>>
>> Satish
>>
>
>


-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100203/667b82fb/attachment.html>