As I stated in my PyCon keynote and repeated (though somewhat hidden) in PEP 3000, all PEPs for Py3k are due by April. The end of April is only a few weeks away, so now is the time to start drafting that PEP if you care about Python 3000! This is so that we will be able to concentrate on *implementing* the accepted proposals by June, in time for the planned release 3.0a1.
Your PEP doesn't have to be *accepted* by April 30; but it should be in good shape, have seen some discussion on python-3000 (or python-ideas), and have popular support. We can do the final discussion about acceptance of individual PEPs (including some revisions) after the deadline; but no PEP submitted after the deadline has a chance. This applies to my own pet projects as well; in particular, if I want Abstract Base Classes in Py3k, I will have to write up a PEP by April 30. If you want interfaces or generic functions, likewise, you need to have a decent PEP submitted by April 30! I'm currently working on the new I/O library, and am confident that this will be in a usable shape by the end of this week. fter that, I plan to concentrate on the str/unicode unification, which is by far the riskiest project still to be done. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
