that is certainly more black and white than reality. I am one of those 100 users and I would (will) certainly go through the code that I use on a daily basis (and the other code that I use
I certainly appreciate any help, but this is not just a matter of amount of time, but also of risk, the risk of introducing bugs. The package that you are using, Scientific Python, is the lesser of my worries, as the individual parts are very independent. My other package, MMTK, is not only bigger, but also consists of many tightly coupled modules. Moreover, I am not aware of any user except for myself who knows the code well enough to be able to work on such an update project. Finally, this is not just my personal problem, there is lots of NumPy code out there, publically released or not, whose developers would face the same difficulties. Konrad. -- ------------------------------------------------------------------------------- Konrad Hinsen | E-Mail: hinsen@cnrs-orleans.fr Centre de Biophysique Moleculaire (CNRS) | Tel.: +33-2.38.25.56.24 Rue Charles Sadron | Fax: +33-2.38.63.15.17 45071 Orleans Cedex 2 | Deutsch/Esperanto/English/ France | Nederlands/Francais -------------------------------------------------------------------------------