[issue515074] Extended storage in new-style classes

Change by admin : -- github: None -> 36073 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue515074] Extended storage in new-style classes

Amaury Forgeot d'Arc added the comment: Most concrete variable-sized types don't use tp_basicsize to know where the data lives. For example, PyBytesObject has a "char ob_sval[1];" member, and PyBytes_AsString() looks at this fixed offset. For this reason, additional data cannot be stored before

[issue515074] Extended storage in new-style classes

Dave Abrahams added the comment: I have no idea. I don't work with low-level python much anymore. Sorry Sent from my moss-covered three-handled family gradunza On May 17, 2013, at 8:54 PM, Ethan Furman wrote: > > Ethan Furman added the comment: > > David, is this still a need? Or, put anot

[issue515074] Extended storage in new-style classes

Ethan Furman added the comment: David, is this still a need? Or, put another way, has Python change enough in the last 11 years that you can now do what you wanted? -- nosy: +ethan.furman ___ Python tracker

[issue515074] Extended storage in new-style classes

Dave Abrahams added the comment: I can't imagine what kind of "positive response" you'd want from me. I responded to the last question asked. I certainly don't know whether this is still an issue, though. -- nosy: +dabrahams status: pending -> open _

[issue515074] Extended storage in new-style classes

Mark Lawrence added the comment: I'll close this unless there's a positive response within a couple of weeks. -- nosy: +BreamoreBoy status: open -> pending ___ Python tracker _

[issue515074] Extended storage in new-style classes

Daniel Diniz added the comment: Seems very out of date. -- nosy: +ajaksu2 priority: normal -> low stage: -> test needed ___ Python tracker ___