[issue39131] signing needs two serialisation passes

R. David Murray added the comment: Ideally this should be exposed by extending the content manager. Instantiating MIME classes is part of the old API, not the new. The code in the PR may well be correct, but class should be hidden from the normal user (of the new API). I'm not sure what th

[issue39131] signing needs two serialisation passes

Change by Jasper Spaans : -- keywords: +patch pull_requests: +17149 stage: -> patch review pull_request: https://github.com/python/cpython/pull/17695 ___ Python tracker ___ __

[issue39131] signing needs two serialisation passes

New submission from Jasper Spaans : When creating multipart/signed messages, this currently require two serialisation passes: once to extract the flattened contents to be signed, and once to actually serialise the message. The PR this ticket will be linked to contains a new class, MIMEMultipa