➜

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 benjamin.peterson
Recipients benjamin.peterson, lepaperwan
Date 2018-09-15.17:24:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537032266.1986529.1509219928.0CF18418@webmail.messagingengine.com>
In-reply-to <1536994795.73.0.956365154283.issue34686@psf.upfronthosting.co.za>
Content 
On Fri, Sep 14, 2018, at 23:59, Erwan Le Pape wrote:
> 
> Erwan Le Pape <lepaperwan3@gmail.com> added the comment:
> 
> Great! My only concern with that is marshalling of untrusted data at 
> runtime (I know, you shouldn't do that) can become a much more expensive 
> operation.
> 
> Is there any internal use of marshal beyond .pycs used at runtime by the 
> core interpreter that might be affected by such a change?

Writing pycs is the only supported use of marhsal.

> 
> If not, it seems (to me) an acceptable modification of marshal and I'll 
> submit a PR for it.

What exactly are you proposing?
History
Date User Action Args
2018-09-15 17:24:30benjamin.petersonsetrecipients: + benjamin.peterson, lepaperwan
2018-09-15 17:24:30benjamin.petersonlinkissue34686 messages
2018-09-15 17:24:30benjamin.petersoncreate