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 tseaver
Recipients barry, tseaver
Date 2010-04-05.17:42:00
SpamBayes Score 0.0009409057
Marked as misclassified No
Message-id <1270489322.03.0.368739706632.issue8318@psf.upfronthosting.co.za>
In-reply-to
Content
Import of the multifile module emits a DeprecationWarning, but the
warning is either incomplete:

- The documentation[1] states that the 'email' module is to be
  preferred, but doesn't describe what APIs should be used from that
  module.

- In fact, the 'email' module doesn't appear to provide an equivalent
  API to the 'multifile' module.

or perhaps inappropriate, as not all handling of 'multipart' MIME is
email related (e.g., processing HTTP form POSTs which include file uploads).

At a minimum, the docs for 'multifile' should include examples showing
the "preferred" way to implement its own native examples using
the'email' module's APIs.


[1] http://docs.python.org/library/multifile.html
History
Date User Action Args
2010-04-05 17:42:02tseaversetrecipients: + tseaver, barry
2010-04-05 17:42:02tseaversetmessageid: <1270489322.03.0.368739706632.issue8318@psf.upfronthosting.co.za>
2010-04-05 17:42:00tseaverlinkissue8318 messages
2010-04-05 17:42:00tseavercreate