On 14/09/2010 11:17, Antoine Pitrou wrote:
Hello,
Like the email package, nntplib in py3k is broken (because of
various bytes/str mismatches; I suppose the lack of a test suite didn't
help when porting).
I would like to take the opportunity to improve the API a bit; no heavy
re-architecting, but simply a bunch of changes to make it higher-level.
Is it acceptable?
(and, yes, I would add a test suite)
Given that backwards incompatible changes are likely to be unavoidable
due to the bytes / str issue, taking the opportunity to cleanup and
improve the API sounds great. Just a shame we didn't get to it for 3.0,
but thank you for picking this up.
Michael
Regards
Antoine.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
READ CAREFULLY. By accepting and reading this email you agree, on behalf of
your employer, to release me from all obligations and waivers arising from any
and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap,
clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and
acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in perpetuity, without
prejudice to my ongoing rights and privileges. You further represent that you
have the authority to release me from any BOGUS AGREEMENTS on behalf of your
employer.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
