Barry Warsaw wrote: > A reminder: the second betas of Python 2.6 and 3.0 are schedule for > tomorrow. I will try to hang out on #python-dev today and will start > looking at the trackers and buildbots. Hopefully, we're on track to get > the releases out! > > If there is anything you need a decision on, please follow up to this > thread. I'm inundated with email so I can't watch every thread on the > mailing lists. Or ping me on #python-dev. I'll be checking in the fix for issue 2235 shortly (the problem with __hash__ not being inherited in 2.x). A pre-review from Guido would have been nice (since monkeying with typeobject.c is always a somewhat delicate operation), but it looks like he didn't get a chance to get back to it after Europython. I'm also going to forward port the underlying implementation to Py3k (so that a non-existent hash is indicated by PyObject_HashNotImplemented in tp_hash at the C level as well as by __hash__ = None at the Python level). Cheers, Nick. _______________________________________________ Python-3000 mailing list Python-3000 at python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/ncoghlan%40gmail.com -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia --------------------------------------------------------------- http://www.boredomandlaziness.org
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4