Message126637
> PyString_AsString() only "works on subclasses" if their internal
> representation is the same as type str. So we can't say "subclass of
> str" without *also* specifying that the subclass store its contents in
> exactly the same way as an object of type str...
There's no point in subclassing str if you're using a different
representation. You're not only wasting space, but some things will
behave badly (precisely because of lot of C functions will call
PyString_Check() and then PyString_AsString()).
So, what you call a limitation isn't really one.
> which means all we've really done is to make the specification longer
> and more complicated
That doesn't follow from the above. |
|
Date |
User |
Action |
Args |
2011-01-20 19:31:11 | pitrou | set | recipients:
+ pitrou, pje, exarkun, ods, eric.araujo, r.david.murray, riffm, andreypopp |
2011-01-20 19:30:56 | pitrou | link | issue10935 messages |
2011-01-20 19:30:56 | pitrou | create | |
|