Re: [Python-Dev] Is there any remaining reason why weakref callbacks shouldn't be able to access the referenced object?

2016-10-22 Thread Nathaniel Smith
On Sat, Oct 22, 2016 at 3:01 AM, Nick Coghlan wrote: > On 22 October 2016 at 16:05, Nathaniel Smith wrote: >> On Fri, Oct 21, 2016 at 8:32 PM, Nick Coghlan wrote: >> But PEP 442 already broke all that :-). Now weakref callbacks can >> happen before __del__, and they can happen on objects that ar

Re: [Python-Dev] Is there any remaining reason why weakref callbacks shouldn't be able to access the referenced object?

2016-10-22 Thread Nick Coghlan
On 22 October 2016 at 16:05, Nathaniel Smith wrote: > On Fri, Oct 21, 2016 at 8:32 PM, Nick Coghlan wrote: > But PEP 442 already broke all that :-). Now weakref callbacks can > happen before __del__, and they can happen on objects that are about > to be resurrected. Right, but the resurrection c

Re: [Python-Dev] Adding bytes.frombuffer() constructor to PEP 467 (was: [Python-ideas] Adding bytes.frombuffer() constructor

2016-10-22 Thread Nick Coghlan
On 22 October 2016 at 07:57, Chris Barker wrote: > I'm still confused about the "io" in "iobuffers" -- I've used buffers a lot > -- for passing data around between various C libs -- numpy, image > processing, etc... I never really thought of it as IO though. which is why a > simple frombuffer() se