[issue3608] memoryview constructor has no deallocator

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- resolution: -> wont fix status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3608] memoryview constructor has no deallocator

Roger Upole <[EMAIL PROTECTED]> added the comment: Aha, thanks. I'll go that route for now. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Pytho

[issue3608] memoryview constructor has no deallocator

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > As background, what I need is an equivalent of > PyBuffer_New(size), which creates an object that manages its > own buffer memory, and is not based on another object at all. Well, you can create either a bytes or bytearray object with an i

[issue3608] memoryview constructor has no deallocator

Roger Upole <[EMAIL PROTECTED]> added the comment: As background, what I need is an equivalent of PyBuffer_New(size), which creates an object that manages its own buffer memory, and is not based on another object at all. ___ Python tracker <[EMAIL PROTECTED]>

[issue3608] memoryview constructor has no deallocator

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- priority: -> normal ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list m

[issue3608] memoryview constructor has no deallocator

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Well, this is not a bug in itself. Memoryview objects are designed to give access to a memory area backed by another object - they don't "own" the memory by themselves (in the sense that you e.g. own a reference to a PyObject). Please note by

[issue3608] memoryview constructor has no deallocator

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- assignee: -> teoliphant nosy: +pitrou, teoliphant ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3608] memoryview constructor has no deallocator

Roger Upole <[EMAIL PROTECTED]> added the comment: Well it existed up until a couple hours ago ;). Looks like it was recently changed to PyMemoryView_FromBuffer. However, it still has the same issue. ___ Python tracker <[EMAIL PROTECTED]>

[issue3608] memoryview constructor has no deallocator

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: PyMemoryView_FromMemory doesn't exist. Do you mean PyMemoryView_FromBuffer or PyMemoryView_FromObject? -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]>

[issue3608] memoryview constructor has no deallocator

New submission from Roger Upole <[EMAIL PROTECTED]>: When using PyMemoryView_FromMemory to create a new object, you have to pass in a preallocated buffer. However, there's no way to specify a routine to free the memory, and it leaks when the object is destroyed. -- components: Interpret