M.-A. Lemburg schrieb: > Hi Walter, > > if the bytes type does turn out to be a mutable type as suggested > in PEP 358, then please make sure that no code (C code in > particular), relies on the constantness of these byte objects. > > This is especially important when it comes to codecs, since > the error callback logic would allow the callback to manipulate > the byte object contents and length without the codec taking > note of this change. > > I expect there to be other places in the interpreter which would > break as well. > > Otherwise, you end up opening the door for segfaults and > easy DOS attacks on Python3.
If the user does not need to change these bytes objects and this is needed in more places, adding an "immutable" flag for "internal" bytes objects only settable from C, or even an immutable byte base class might be an idea. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
