New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mailbox should use email not rfc822 #38679
Comments
The mailbox module uses the rfc822 module as its Of course this has backward compatibility issues, in |
Logged In: YES I've added some sample code to the mailbox documentation |
Logged In: YES So, with the plans to seriously start working deprecating |
Logged In: YES It's a good question. I'd like to say yes so that we can |
Logged In: YES Given the amount of code out there using rfc822, should we |
The reworking of mailbox.py introduced in Python 2.5 adds new mailbox classes that do use email.Message. |
I dunno if this is helpful, but in the 2.5 module, it parses mailboxes |
synx's patch wasn't applying cleanly and broke 2 maildir tests. I'm Question: mailbox.py has one section marked as "classes from the original |
I think removing those old classes in 3.0 would be very sensible. |
I created bpo-2814 with a patch to remove those old classes. |
I removed the old classes in 3k. There remains one usage of rfc822, as |
Yes. That's what mailbox documentation says: Parameter factory is a callable object that accepts a file-like message |
Removed the last rfc822 reference from 3k's mailbox.py in r63091. |
Georg, any special reason for not removing rfc822 references from |
Okay, removed that too in r63096. |
rfc822
from mailbox and test_mailbox.Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: