>So here's a question (speaking as someone that has never had to go near >the email module, and is unlikely to do so anytime soon): is this >something that should hold up the release of Python 3.0?
I'm not sure. I noticed the email problems because I was trying to port a web framework to py3k, and eventually ran into too many problems with the cgi module (which were due partially to email's shaky handling of Unicode). The email problems are hard, and none of us really has the time to resolve them quickly, so if the release was delayed due to email, we couldn't say when it would be "done". That doesn't seem attractive. On the other hand, ripping email out completely will break a number of other modules that rely on it for MIME and RFC822 handling. At the moment, they're limping along by casting bytes to latin1 (if I remember correctly), which works mostly. I think the only sensible answer is to leave it as is with warnings. Maybe the hypothetical new module should be called email2 or something. -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
