[petsc-dev] [petsc4py] going to stop support for petsc-2.3.2 and petsc-2.3.3

[Lisandro Dalcin]

Maintaining backward compatibility for petsc4py against petsc-2.3.2
and petsc-2.3.3 is making my head explode. Every feature from newer
PETSc releases I want to support forces me to emulate the call using
the older API's (and in some cases private data structures), or write
some extra code in order to generate a runtime error about the
unsupported feature/call/whatever. Additionally,  Barry seems to have
lost control of his fingers, and make changes to petsc-dev that affect
petsc4py at its heart (like the COOKIE->CLASSID rename and the SETERRQ
macro redefine).

If any of you out there is still interested in running 2.3.2/2.3.3
from Python, speak now and offer help for maintaining this. If you one
shows up, I'll COMPLETELY REMOVE all traces of 2.3.2/2.3.3 backward
compatibility support from petsc4py repositories (at petsc.cs.iit.edu
and Google Code).


-- 
Lisandro Dalcin
---------------
CIMEC (INTEC/CONICET-UNL)
Predio CONICET-Santa Fe
Colectora RN 168 Km 472, Paraje El Pozo
Tel: +54-342-4511594 (ext 1011)
Tel/Fax: +54-342-4511169