[issue1022] use bytes for code objects

Guido van Rossum added the comment: We won't be doing it this way. -- resolution: remind -> rejected status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ __

[issue1022] use bytes for code objects

Changes by Sean Reifschneider: -- assignee: -> gvanrossum priority: -> low resolution: -> remind __ Tracker <[EMAIL PROTECTED]> __ ___ Python

[issue1022] use bytes for code objects

Brett Cannon added the comment: I have security/stability issues with code objects having mutable bytecode. This would allow someone to possibly crash the interpreter with crappy bytecode. I also have a worry that someone might come up with some clever way of causing different code to execute t

[issue1022] use bytes for code objects

Changes by Martin v. Löwis: -- keywords: +patch __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue1022] use bytes for code objects

Guido van Rossum added the comment: I'll defer thinking about this until post-a1. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> __ ___ Pyt

[issue1022] use bytes for code objects

New submission from Neal Norwitz: This patch has a hack to read in marshaled code objects. Bytes can't be marshaled currently (they are stored as strings). So when reading a marshaled code object, the hack converts them to bytes. All tests except test_modulefinder pass. The issue is that si