Steven D'Aprano <steve+pyt...@pearwood.info> added the comment: Alexey, I'm afraid I can't make heads or tails of your bug report. You've gone into a detailed description of the "bad results" you have, but you haven't explained *why* they're bad, or what you were expecting.
I'm afraid that I found understanding your test case code a hard slog. A much simpler test case showing input, expected output, and actual output is appreciated. It might help if you read this: http://sscce.org/ Its written for Java programmers, but the same applies to any programming language. Please don't go straight to assumptions about the cause of the bug ("memory corruption") until you can demonstrate that there actually is a bug. Ivan has spent significant effort to understand your test case, thank you Ivan, and concludes: > This is not a bug, everything work correctly. so I'm going to close the bug report. If you disagree with Ivan's conclusion, please write back with reasons why you disagree. It would also significantly help if you can provide a simpler test case that demonstrates expected results and actual results (and preferably input data small enough to fit inline in the testcase script, if possible). ---------- nosy: +steven.daprano resolution: -> not a bug stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33186> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
