Martijn Faassen wrote:

Stefan Behnel wrote: [snip]

...

I had the same problem with Pyrex 0.9.3.1 and it's solved by the original patch by Martijn. I resent it to the Author of Pyrex just this morning, so they should know. But it's never bad to have more people bug them...

Agreed the more people bug them politely about this, the better. :)

Did this get in now? No new release yet...

I didn't get any reply back.

Note that I think someone else is taking care of the Pyrex gcc 4.0 compat releases right now, not Greg Ewing, so it may be useful to mail to him too if you haven't already. From the homepage it appears to be Giovanni Bajo.

I don't know if maintainership has changed there, and I also don't have his email address. What about the intermediate solution of putting etree.c into SVN? Since each checkin encourages running the test suite anyway, it should always be up to date and can just be committed with the changes. That way people don't need to patch Pyrex. However, most current linux distributions seem to have the patch integrated, so it should rarely be a problem nowadays. Stefan