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 r.david.murray
Recipients barry, brandon-rhodes, eric.araujo, joegod, ncoghlan, r.david.murray, serhiy.storchaka
Date 2014-08-05.18:19:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1407262760.7.0.0807183558365.issue21091@psf.upfronthosting.co.za>
In-reply-to
Content
is_multipart is *not* part of the provisional API, though; only is_attachment is.

So per my understanding of the provisional rules, we should either make is_attachment a method in both 3.4 maint and 3.5, or make is_multipart emit a deprecation warning in 3.5.  

I lean toward the former for backward compatibility reasons, with Serhiy's addition of making it emit a warning if not called in 3.4.
History
Date User Action Args
2014-08-05 18:19:20r.david.murraysetrecipients: + r.david.murray, barry, ncoghlan, eric.araujo, brandon-rhodes, serhiy.storchaka, joegod
2014-08-05 18:19:20r.david.murraysetmessageid: <1407262760.7.0.0807183558365.issue21091@psf.upfronthosting.co.za>
2014-08-05 18:19:20r.david.murraylinkissue21091 messages
2014-08-05 18:19:20r.david.murraycreate