(Quality behind the chiller)
Since 3.6, the implementation of the email package has been significantly expanded and the associated documentation has changed significantly. It ’s not a secret, it ’s written clearly.
The email package itself has been relatively nice (I think) for some time, but the documentation was still old up to 3.5. For example, regarding RFC, I was pointing to an obsolete person (for example, RFC 2822 instead of RFC 5322) (conversely, other than that, there shouldn't be much difference, but at the beginning of the document, I'm curious. RFC 5322 is from 2008). The 3.6 documentation is generally up-to-date.
3.6 is still in a new category and is not available as standard on major Linux distros. It's almost like Python 2 or 3.4, 3.5. A quick check revealed that CentOS 7 (but epel) was 3.4 and Ubuntu 16.04 was 3.5. I don't know SUSE (Asobi Taiyo). Of course, if you rely on pyenv or Anaconda, you can use 3.6 series (as of May 2017)
When developing in the old Python3 environment, it is better to specify the version and read the 3.6 document without reading it. Of course, that's generally the case, but when it comes to minor updates, the Python documentation tends to kindly write diffs as "added from version xx", so I tend to cut corners.
However, the email package is almost "rewritten", so you need to "care" more. If you look directly at a document such as EmailMessage (For example), it looks like "No". (There is "New in 3.6" at the beginning of the page, but if you try to look at the documentation about the class directly, you may miss it).
The one called Legacy API is 3.5 or earlier. If you're using 3.5 or earlier, it's only natural to rely on older manuals.
Recommended Posts