StaticTuple... naming, maintenance, ...

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...

> Purely from the discussion, it _sounds like_ cost (2) here is small;
> many of the gains can Just Happen without the code being different.
> So cost (1) is probably the determining factor.  Not being the one
> shouldering the cost, it's easy to say, but I'd as soon not have a
> sudden gear-switching flag day unless the compat cost is fairly
> significant.  I'd be fine with saying "Using pyrex will work
> correctly, using cython will work better" either temporarily or
> indefinitely, or if the costs are significant and growing, adding "and
> at $FUTURE_TIME we'll stop trying to keep pyrex working".


So, maintaining compatibility with pyrex probably isn't terrible. The
hardest part is that the "official" builds should be done with cython
0.11.3, or we won't see the actual benefit.

However, I believe "official" builds are always done on a developers
(read Martin's) machine, so we can try to make that work there.

Though it is a little bit like what we are running into now when
extensions don't quite get built for the nightlies. Everything works
when you do it manually, but you need a built-in safety check or things
will fail silently in the automated builds...

I also don't know what version of Pyrex we want to maintain support for.
Some of the changes are at least 0.9.6 (being able to export a C api.)

I would love to make it 0.9.8+, which means we would get:
  cdef list foo

support. (that can translate 'foo.append()' into PyList_Append() rather
than having to do all of that manually...)



Also, the cython dependency only effects people building from source. If
you have a packaged version or from the tarball, then we will have
generated the .c files for you...

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrLZjsACgkQJdeBCYSNAAMMmQCfVMjRQL6M4WrQzUAs5fVV07Tt
yf4AoIZFMSBo16seYxk7ib+RMcOEarbs
=MfQj
-----END PGP SIGNATURE-----