[issue42340] KeyboardInterrupt should come with a warning

2020-11-12 Thread Benjamin Fogle
Change by Benjamin Fogle : -- keywords: +patch pull_requests: +22151 stage: -> patch review pull_request: https://github.com/python/cpython/pull/23255 ___ Python tracker <https://bugs.python.org/issu

[issue42340] KeyboardInterrupt should come with a warning

2020-11-12 Thread Benjamin Fogle
Change by Benjamin Fogle : Added file: https://bugs.python.org/file49595/sigint_condition_1.py ___ Python tracker <https://bugs.python.org/issue42340> ___ ___ Python-bug

[issue42340] KeyboardInterrupt should come with a warning

2020-11-12 Thread Benjamin Fogle
Change by Benjamin Fogle : Added file: https://bugs.python.org/file49597/sigint_tempfile.py ___ Python tracker <https://bugs.python.org/issue42340> ___ ___ Python-bug

[issue42340] KeyboardInterrupt should come with a warning

2020-11-12 Thread Benjamin Fogle
Change by Benjamin Fogle : Added file: https://bugs.python.org/file49598/sigint_zipfile.py ___ Python tracker <https://bugs.python.org/issue42340> ___ ___ Python-bug

[issue42340] KeyboardInterrupt should come with a warning

2020-11-12 Thread Benjamin Fogle
New submission from Benjamin Fogle : This is related to bpo-29988, and I'm happy to move this to there. I made this a separate issue because this is a workaround, not a fix as was being discussed there. Also unlike bpo-29988, this is not restricted to context managers or finally blocks. TL

[issue42340] KeyboardInterrupt should come with a warning

2020-11-12 Thread Benjamin Fogle
Change by Benjamin Fogle : Added file: https://bugs.python.org/file49596/sigint_condition_2.py ___ Python tracker <https://bugs.python.org/issue42340> ___ ___ Python-bug

[issue31976] Segfault when closing BufferedWriter from a different thread

2017-11-07 Thread Benjamin Fogle
Change by Benjamin Fogle <benfo...@gmail.com>: -- type: -> crash ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31976> ___ __

[issue31976] Segfault when closing BufferedWriter from a different thread

2017-11-07 Thread Benjamin Fogle
Change by Benjamin Fogle <benfo...@gmail.com>: -- keywords: +patch pull_requests: +4287 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

[issue31976] Segfault when closing BufferedWriter from a different thread

2017-11-07 Thread Benjamin Fogle
New submission from Benjamin Fogle <benfo...@gmail.com>: To reproduce: ``` import threading import io import time import _pyio class MyFileIO(io.FileIO): def flush(self): # Simulate a slow flush. Slow disk, etc. time.sleep(0.25) super().flush() raw = My

[issue27517] LZMACompressor and LZMADecompressor raise exceptions if given empty strings twice

2016-10-30 Thread Benjamin Fogle
Benjamin Fogle added the comment: Ah, thank you. Good catch. I have reworked the patch to handle both cases. -- Added file: http://bugs.python.org/file45286/lzma_2.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue27517] LZMACompressor and LZMADecompressor raise exceptions if given empty strings twice

2016-07-14 Thread Benjamin Fogle
Benjamin Fogle added the comment: The above code demonstrates two separate issues. One with the decompressor, and one with the compressor. In the compressor example, the first output differs from the rest because it is a file header which is always emitted. That behavior is correct

[issue27517] LZMACompressor and LZMADecompressor raise exceptions if given empty strings twice

2016-07-14 Thread Benjamin Fogle
New submission from Benjamin Fogle: To reproduce: >>> import lzma >>> c = lzma.LZMACompressor() >>> c.compress(b'') b'\xfd7zXZ\x00\x00\x04\xe6\xd6\xb4F' >>> c.compress(b'') b'' >>> c.compress(b'') Traceback (most recent call last): File "&