"BAW" == Barry A Warsaw <bwarsaw@cnri.reston.va.us> writes: "Guido" == Guido van Rossum <guido@cnri.reston.va.us> writes:
Guido> There are several other things I can think of now that were Guido> planned for 1.6: revamped import, rich comparisons, revised Guido> coercions, parallel for loop (for i in L; j in M: ...), Guido> extended slicing for all sequences. I've also been thinking Guido> about making classes be types (not as huge a change as you Guido> think, if you don't allow subclassing built-in types), and Guido> adding a built-in array type suitable for use by NumPy. I've Guido> also received a conservative GC patch that seems to be fairly Guido> easy to apply and has some of Tim Peters' blessing. BAW> All very cool things that could easily wait until 1.7. After BAW> all, what's in a number? If, as Andrew puts forth, getting a BAW> stable Python release with Unicode is very important for BAW> Python's future positioning, then I say let's go with his more BAW> modest list, mainly Unicode, sre, and Distutils. We've already BAW> got string meths, tons of library improvements, and sundry BAW> other things. That's a good enough laundry list for the next BAW> release. We've had this conversation before, so it'll comes as no surprise that I agree with you. Question: If we go with the feature set you've described, when will those features be ready? What kind of schedule could we set for releasing the first alpha? Jeremy