[issue25538] Traceback from __exit__ method is misleading

2020-11-27 Thread Alexander Kurakin
Change by Alexander Kurakin : -- nosy: +kuraga ___ Python tracker <https://bugs.python.org/issue25538> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42372] A crash in do_richcompare

2020-11-18 Thread Alexander Kurakin
Alexander Kurakin added the comment: Ok, close. -- stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue42372> ___ __

[issue42372] A crash in do_richcompare

2020-11-16 Thread Alexander Kurakin
Alexander Kurakin added the comment: Thanks for reply! Is it call of NULL? If so, shoudn't do_richcompare check it? -- ___ Python tracker <https://bugs.python.org/issue42

[issue42372] A crash in do_richcompare

2020-11-16 Thread Alexander Kurakin
New submission from Alexander Kurakin : Sometimes test.py causes a crash in 3.7.9 (and lower to 2018 year or more) on Linux. See also: https://github.com/pandas-dev/pandas/issues/21968 -- components: Interpreter Core files: issue.zip messages: 381113 nosy: kuraga priority: normal

[issue38638] Backtrace of exit phase of context managers

2019-10-30 Thread Alexander Kurakin
New submission from Alexander Kurakin : class CM: def __init__(self): pass def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): raise RuntimeError() if __name__ == '__main__': with CM() as cm: print('Hello

[issue38042] Crash on double list(lxml.etree.iterparse(f))

2019-09-06 Thread Alexander Kurakin
Alexander Kurakin added the comment: Ok, thanks! Good that I was too lazy to open bug in June because our colleague did it better then me :) Seems like the fix doesn't present in current 3.7 version (3.7.4). Will try in 3.7.5 and will close UPD: Oh, closed? Ok. But *no*, it's not fixed

[issue38042] Crash on double list(lxml.etree.iterparse(f))

2019-09-06 Thread Alexander Kurakin
Alexander Kurakin added the comment: Yes, I do. Please read all. 1) According to https://bugs.launchpad.net/lxml/+bug/1833050 (by lxml author's opinion) it's not a lxml bug. 2) I wouldn't said that but according to backtrace we have crash at Python-time. 3) Moreover crash existence depends

[issue38042] Crash on double list(lxml.etree.iterparse(f))

2019-09-05 Thread Alexander Kurakin
Change by Alexander Kurakin : -- title: Crash on double list(lxml.etree.iterparse(f)) Edit -> Crash on double list(lxml.etree.iterparse(f)) ___ Python tracker <https://bugs.python.org/issu

[issue38042] Crash on double list(lxml.etree.iterparse(f)) Edit

2019-09-05 Thread Alexander Kurakin
New submission from Alexander Kurakin : I have a crash in Python 3.x environments and don't have in 2.7. === Crashes in: Python 3.7.4, Anaconda, Linux 64bit, lxml 4.3.3 OR Python 3.7.4, Anaconda, Linux 64bit, lxml 4.4.1 OR Python 3.6.5, Gentoo Linux 64bit, lxml 4.3.3 test.py: import lxml