Robert Bradshaw, 22.01.2010 08:24:
> It seems we're due for another release...

Very much +1.


> Does anyone have anything else they'd like to see
> in sooner rather than later? Any blockers?

According to trac, there are no real blockers for 0.12.1. The only real
bugs targeted for that release are #473 (MSVC problem) and #467. The latter
one can be bad in rare cases but shouldn't do much harm normally (and isn't
exactly trivial to get right).


> Otherwise I'll start  
> rolling alphas and testing on the freshly-minted Sage 4.3.1.

Please do.


> I'd like to see an 0.13 soon thereafter.

Big +1 again. I'm fine with 0.13.0 being "not 100% stable" but would love
to have it out there so that people can use the new features and find bugs.


> I'm imagining a big release  
> where we pull in a bunch of stuff that's been "almost ready" for a  
> while:
> 
> 1. Safe type inference (on by default)
> 
> This seems to be basically ready, but is too big of a change for an  
> x.y.z release.

Ok with me, but that's in cython-devel already. Would you want to roll back
the implementation or just disable the feature by default? The latter
should basically revert to the original behaviour already, AFAICT.


> 2. Closures

Sure, let's get that one out and then take a look at where that gets us.
There hasn't been such a major new feature in Cython for a while, and this
will enable tons of new use cases and forms the basis for quite a lot of
other Python features (e.g. lambda and generators).


> Craig Citro wants to run another battery of tests on it

Can we add that to the regular test suite somehow?


> 3. C++ support

I can't say I'm anywhere near up-to-date with the status of that, but if
you think it's at a somewhat stable point, so that existing features won't
have to get rolled back and replaced, I'm fine with adding it (or parts of
it) in 0.13. It's always good to enable users to exercise new features
early, and especially the signature overloading support should be very
useful to Cython's optimiser by itself.

What about the Fortran integration? Is there anything we can add from that
already? If we get a part of that in, we might be able to attract other
Fortran users. Some of them may even end up participating in the further
development. Putting this on more shoulders is the best way to push it further.

Stefan

_______________________________________________
Cython-dev mailing list
Cython-dev@codespeak.net
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to