Stefan Krah added the comment:
This is actually a lot of work, I don't think I'll have time for it.
Please just reopen if you think there's a chance that someone will take the
task.
--
resolution: - wont fix
stage: - resolved
status: open - closed
Changes by Stefan Krah stefan-use...@bytereef.org:
--
assignee: skrah -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14198
___
___
Changes by Nick Coghlan ncogh...@gmail.com:
--
versions: -Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14198
___
___
Kristján Valur Jónsson krist...@ccpgames.com added the comment:
Stefan, I just want to point out this issue, if you are touching 2.7:
http://bugs.python.org/issue10538
Do you think it merits being fixed?
--
nosy: +krisvale
___
Python tracker
Stefan Krah stefan-use...@bytereef.org added the comment:
Kristj??n Valur J??nsson rep...@bugs.python.org wrote:
Stefan, I just want to point out this issue, if you are touching 2.7:
http://bugs.python.org/issue10538
Do you think it merits being fixed?
I think so. A patch would be
New submission from Stefan Krah stefan-use...@bytereef.org:
Nick's comment from #10181:
It occurs to me that one thing that *could* be backported to early versions
are some of the documentation improvements on how to correctly handle the
lifecycle of fields in Py_buffer. That gets messy
