Re: [Python-3000] email libraries: use byte or unicode strings?
Barry Warsaw <[email protected]>
| Newsgroups | gmane.comp.python.mime.devel,gmane.comp.python.python-3000.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Nov 6, 2008, at 1:15 PM, Guido van Rossum wrote: >> But if that's not the case, wouldn't it make more sense to keep >> email out of >> the initial 3.0 release, rather than put a half-broken version in >> with >> special "we can totally change the API for the next release" >> dispensation? > > Tough call. I'm inclined to give people *something* in 3.0 with the > promise we'll fix it in 3.1, rather than withholding it altogether. I think that's the right thing to do, because large parts of the API will be the same, and where ever it's possible, we should provide a migration path for the new API (e.g. DeprecationWarnings, etc.). - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSRM7zXEjvBPtnXfVAQKlMQP/YxW+AWdFb83NC9mpL3uBZrNkEygKlcp6 IoyehmucOfCmPGp8dwCkw/BP9qCoKXkFyCnMbIuLOhbyzYfPsPD822voGjeLNb2O bYPMoMSOdlUPJaV4trdGd3RR7KIYAwhXymWW1MxnkyfDZ1mNyRRJyR3SMPJiLZoL /MDfrcchcGQ= =z39Z -----END PGP SIGNATURE-----