[issue2619] Document PEP 3118

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: I'm just going to close this. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue2619] Document PEP 3118

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: The bulk of the C-API is in r66476. Somebody definitely needs to review it; I mostly extracted it directly from the PEP, and I understand that's a little different from reality here. I'll lower priority, and we can close it after some looks

[issue2619] Document PEP 3118

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: I documented the memoryview object in r66357. If you're really nice to me, maybe I'll do the C-API, too. :) -- priority: critical -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]>

[issue2619] Document PEP 3118

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Should this be a release blocker? -- type: feature request -> behavior ___ Python tracker <[EMAIL PROTECTED]> ___

[issue2619] Document PEP 3118

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: As a reminder, I want to mention that PEP 3118 itself needs to be updated (see #3560). -- nosy: +pitrou ___ Python tracker <[EMAIL PROTECTED]> ___

[issue2619] Document PEP 3118

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Upon further inspection, it seems none of the new buffer protocol is documented. (The old functions are still present in the 3.0 docs.) -- title: Document memoryview -> Document PEP 3118 __ Tracker