[David A] > > It's not too terrible, but I'd like it a lot better if types would > > just use tp_basicsize to find the beginning of the variable stuff > > so we could embed the memory in the type itself. 'Course, I've > > forgotten more than I knew about that code, so I might be barking > > up the wrong banyan. [Chris T] > That's exactly what I want to do, but I have to find > out how the variable part of types is used at the moment, > and I admit I didn't understand it, yet. > > The place where user stuff should go is where instances > have their slots. With meta-types, it now happens that > types become instances, but types refuse to have slots. > This needs to be changed, everything else is a workaround. You're right. And David has the right idea. The problem is that for convenience I defined the variable part of a type object as a private structure (etype). It's a lot of work to change that -- not very deep perhaps, but a lot of refactoring code that does deep things. To remind myself of this task, I've added a new SF bug: python.org/sf/591586 --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4