Issue 1102469: rfc822 Deprecated since release 2.3? (original) (raw)
Issue1102469
Created on 2005-01-14 17:40 by tungwaiyip, last changed 2022-04-11 14:56 by admin. This issue is now closed.
Messages (3) | ||
---|---|---|
msg23962 - (view) | Author: Wai Yip Tung (tungwaiyip) | Date: 2005-01-14 17:40 |
rfc822.Message is still subclassed by minetool.Message and httplib.HTTPMessage. It should either 1. upgrade httplib etc to the email package. 2. or make a note in the rfc822 page that it is still being in use 3. or undeprecate rfc822. | ||
msg23963 - (view) | Author: Simon Percivall (simon.percivall) | Date: 2005-01-15 05:30 |
Logged In: YES user_id=329382 No, rfc822 is actually not deprecated. It's also used in other parts of the stdlib. Look at the Python-Dev thread from August 2004 "Removing stuff from 2.4". | ||
msg23964 - (view) | Author: Anthony Baxter (anthonybaxter) ![]() |
Date: 2005-01-17 14:20 |
Logged In: YES user_id=29957 rfc822 is currently in a state of PendingPendingDeprecation. It would have gained a PendingDeprecationWarning in 2.4, but as you point out, we're still using it in the stdlib. This is going to be fixed in 2.5 - the stdlib won't be using it any further. Nonetheless, the warning on the documentation page saying "Use email, instead" is still valid. I'd hate for people to start using rfc822 at this very late stage in it's life. Marking as 'wontfix' |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:56:09 | admin | set | github: 41440 |
2005-01-14 17:40:50 | tungwaiyip | create |