Re: [Numpy-discussion] the direction and pace of development

[Konrad H. <hi...@cn...>]

On Wednesday 21 January 2004 22:28, Perry Greenfield wrote:

> contributed code as well). You have to remember that how easily
> contributions come depends on what the critical mass is for
> usefulness. For something like numarray or Numeric, that critical
> mass is quite large. Few are interested in contributing when it
> can do very little and and older package exists that can do more.

I also find it difficult in practice to move code from Numeric to Numarra=
y.=20
While the two packages coexist peacefully, any C module that depends on t=
he C=20
API must be compiled for one or the other. Having both available for=20
comparative testing thus means having two separate Python installations. =
And=20
even with two installations, there is only one PYTHONPATH setting, which=20
makes development under these conditions quite a pain.

If someone has found a way out of that, please tell me!

> many times in the past. Often consensus was hard to achieve.
> We tended to lean towards backward compatibilty unless the change
> seemed really necessary. For type coercion and error handling,
> we thought it was. But I don't think we have tried shield the
> decision making process from the community. I do think the difficulty
> in achieving a sense of consensus is a problem.

I think you did well on this - but then, I happen to share your general=20
philosophy ;-)

Konrad.
--=20
-------------------------------------------------------------------------=
------
Konrad Hinsen                            | E-Mail: hi...@cn...
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
-------------------------------------------------------------------------=
------