Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-June/120143.html below:

[Python-Dev] segfault - potential double free when using iterparse

• Previous message: [Python-Dev] segfault - potential double free when using iterparse
• Next message: [Python-Dev] [compatibility-sig] making sure importlib.machinery.SourceLoader doesn't throw an exception if bytecode is not supported by a VM
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 6/12/2012 9:40 AM, Alon Horev wrote:
> Hi All,
>
> First of all, I'm not opening a bug yet as I'm not certain whether this
> is a CPython bug or lxml bug.

lxml is more likely, making this a topic for python-list and whatever 
lxml list.

...
> from lxml.etree import iterparse
...

> anyone familiar with these kind of bugs in c extensions/cpython/lxml?
> could you give pointers to what I should be looking for?

I would ask the generic question on python-list and report the problem 
to lxml folks also.

> some version info:
> CPython version: 2.7.2 on linux.

2.7.3 has 6 months more of bugfixes, and if there is a problem with 
python, you would have to demonstrate a problem with that or a more 
recent build.

-- 
Terry Jan Reedy

• Previous message: [Python-Dev] segfault - potential double free when using iterparse
• Next message: [Python-Dev] [compatibility-sig] making sure importlib.machinery.SourceLoader doesn't throw an exception if bytecode is not supported by a VM
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4