[issue8318] Deprecation of multifile inappropriate or incomplete

Changes by Terry J. Reedy : -- stage: needs patch -> committed/rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue8318] Deprecation of multifile inappropriate or incomplete

Changes by Terry J. Reedy : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue8318] Deprecation of multifile inappropriate or incomplete

Terry J. Reedy added the comment: Multifile *is* gone in 3.x; done deal. If you want 2.7 docs improved, submit suggested change, even as text in message. -- assignee: -> d...@python components: +Documentation -Library (Lib) nosy: +d...@python, terry.reedy versions: -Python 2.5, Pytho

[issue8318] Deprecation of multifile inappropriate or incomplete

Tres Seaver added the comment: For the sake of completeness: the Zope2 trunk and its current stable branch now no longer use the multifile module, thanks to the following patch: http://svn.zope.org/Zope/trunk/src/OFS/tests/testRanges.py?rev=110704&r1=110402&r2=110704 That diff might serve a

[issue8318] Deprecation of multifile inappropriate or incomplete

Tres Seaver added the comment: > Could you do me a favor and add that use case the set of use cases in > the email wiki? Done. The code in Zope which still uses 'multifile' is in the tests for HTTP 'Range' support: http://svn.zope.org/*checkout*/Zope/trunk/src/OFS/tests/testRanges.py?conte

[issue8318] Deprecation of multifile inappropriate or incomplete

R. David Murray added the comment: Depending on the feature, I might agree with that, but I wasn't involved in that decision. If email only supports something structured with proper MIME headers and multifile is more general (which I *think* is the case, but I haven't actually tried to run a

[issue8318] Deprecation of multifile inappropriate or incomplete

Tres Seaver added the comment: > [T]here [may be] things you can do with multifile that you can't (yet) > do with the facilities from the email package. If so, these will most > > likely be considered bugs in the email package. Surely the presence of such a feature would make the deprecation

[issue8318] Deprecation of multifile inappropriate or incomplete

R. David Murray added the comment: It's not inappropriate, since the facilities *in* the email package are supposed to support other MIME use cases (such as HTML). That it isn't clear how to convert is certainly a doc bug at the very least. However, I wouldn't be entirely surprised to find

[issue8318] Deprecation of multifile inappropriate or incomplete

New submission from Tres Seaver : 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'