On 7/23/07, Kevin Cozens [EMAIL PROTECTED] wrote:
David Gowers wrote:
The what's new document for each release is a good resource for these
kinds of problems, especially its porting section:
http://docs.python.org/whatsnew/porting.html
The last two items on that page seem to be the more
David Gowers wrote:
The what's new document for each release is a good resource for these
kinds of problems, especially its porting section:
http://docs.python.org/whatsnew/porting.html
The last two items on that page seem to be the more likely candidates that
could cause problems. I don't
BTW, Nick Coghlan said:
The most likely culprit is that some of the code is using PyMem_Free on
a pointer allocated with PyObject_Malloc (or vice-versa). This has
always been illegal, but prior to 2.5 the Python memory allocator tied
itself in knots to try to avoid crashing when client code broke
Hi,
On Fri, 2007-07-20 at 10:11 +0930, David Gowers wrote:
I mean python 2.6 -- that's SVN python's current version number. I
believe a release is due fairly soon.
Have you contacted the python developers then? This looks a lot like a
regression in Python and I guess they would like to hear
On 20 Jul, David Gowers wrote:
I mean python 2.6 -- that's SVN python's current version number. I
believe a release is due fairly soon.
Definitely not, not this year.
First, there will be some 3.0 alpha releases starting
at the end of August(?).
Version 2.6 will come after 3.0 has stabilized
David Gowers wrote:
Using Python 2.6, typing 'import gegl' at the interpreter prompt
causes the following crash to immediately happen:
[snip]
I'm also pretty sure that the bug lies in the pygegl module, as I've
compiled and used many other modules for Python 2.6, with no problems,
and I ran
On Thursday 19 July 2007 19:28, Kevin Cozens wrote:
David Gowers wrote:
Using Python 2.6, typing 'import gegl' at the interpreter prompt
causes the following crash to immediately happen:
[snip]
I'm also pretty sure that the bug lies in the pygegl module, as
I've compiled and used many
On 7/20/07, Joao S. O. Bueno Calligaris [EMAIL PROTECTED] wrote:
I have only tested pyGEGL with the 2.4 version of Python. It
possible (or very likely?) that something has changed in the 2.6
version of Python. I don't have the 2.6 version installed at the
moment so I can't investigate this
