"Martin v. Löwis", 28.01.2011 01:02:
Am 27.01.2011 23:53, schrieb Stefan Behnel:
"Martin v. Löwis", 24.01.2011 21:17:
If the string is created directly with the canonical representation
(see below), this representation doesn't take a separate memory block,
but is allocated right after the PyUnicodeObject struct.
Does this mean it's supposed to become a PyVarObject?
What do you mean by "become"? Will it be declared as such? No.
Antoine proposed
that, too. Apart from breaking (more or less) all existing C subtyping
code, this will also make it harder to subtype it in new code. I don't
like that idea at all.
Why will it break all existing subtyping code? See the PEP: Only objects
created through PyUnicode_New will be affected - I don't think this can
include objects of a subtype.
Ok, that's fine then.
Stefan
_______________________________________________
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
