Fixing docs is fine - please checkin.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Fredrik Lundh wrote:
> Georg Brandl wrote:
>
>>> The example code causes segfaults and probably always has (at last to 2.2)
>>
>> Interesting! From a naive POV, the docs' example is quite right.
>
> except that it doesn't work?
I wanted to say: From looking at the docs only, it should be alrigh
Georg Brandl wrote:
> Okay, now that I stumbled over and read the c.l.py thread, I think that we
> should
>
> * remove the faulty example (the correct one is already in there)
> * add a note to PyList_New that the new list must be filled with items
>before handing it to Python code or using
Georg Brandl wrote:
>> The example code causes segfaults and probably always has (at last to 2.2)
>
> Interesting! From a naive POV, the docs' example is quite right.
except that it doesn't work?
the problem is that it's using a *high-level* API to manipulate objects
that are not properly init
The release candidate is done - we creep ever closer to 2.5 final. Hoooray!
All future 2.5 releases (including 2.5 final!) will now be done from the new
release25-maint trunk
(svn+ssh://[EMAIL PROTECTED]/python/branches/release25-maint) - so any
changes you want to see after 2.5c1 and before 2.
