[Python-Dev] PyWeakref_GetObject() borrows its reference from... whom? (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Mon Oct 10 18:27:46 EDT 2016
- Previous message (by thread): [Python-Dev] PyWeakref_GetObject() borrows its reference from... whom?
- Next message (by thread): [Python-Dev] PyWeakref_GetObject() borrows its reference from... whom?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nathaniel Smith wrote:
IIRC to handle this gilectomy adds per-object mutexes that you have to hold whenever you're mucking around with that object's internals.
What counts as "mucking around with the object's internals", though?
If I do the C equivalent of:
x = somedict[5]
x.dosomething()am I mucking around with the internals of somedict? Intuitively, I would not think so. But the way PyDict_GetItem currently works, this would be dangerous.
-- Greg
- Previous message (by thread): [Python-Dev] PyWeakref_GetObject() borrows its reference from... whom?
- Next message (by thread): [Python-Dev] PyWeakref_GetObject() borrows its reference from... whom?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]