This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mgiuca
Recipients georg.brandl, loewis, mgiuca
Date 2008-08-20.16:15:00
SpamBayes Score 1.52739e-06
Marked as misclassified No
Message-id <1219248902.32.0.539918037799.issue3565@psf.upfronthosting.co.za>
In-reply-to
Content
A similar issue came up in another bug
(http://bugs.python.org/issue3613), and Guido said:

"IMO it's okay to add encodebytes(), but let's leave encodestring()
around with a deprecation warning, since it's so late in the release cycle."

I think that's probably wise RE this bug as well - my original
suggestion to REPLACE tostring/fromstring with tobytes/frombytes was
probably a bit over-zealous.

I'll have another go at this during some spare cycles tomorrow -
basically taking my current patch and adding tostring/fromstring back
in, to call tobytes/frombytes with deprecation warnings. Does this sound
like a good plan?

(Also policy question: When you have deprecated functions, how do you
document them? I assume you say "deprecated" in the docs; is there a
standard template for this?)
History
Date User Action Args
2008-08-20 16:15:02mgiucasetrecipients: + mgiuca, loewis, georg.brandl
2008-08-20 16:15:02mgiucasetmessageid: <1219248902.32.0.539918037799.issue3565@psf.upfronthosting.co.za>
2008-08-20 16:15:01mgiucalinkissue3565 messages
2008-08-20 16:15:00mgiucacreate