[issue39040] Wrong attachement filename when mail mime header was too long

Manfred Kaiser added the comment: RFC-2184 was obsoleted by RFC-2231 (https://www.rfc-editor.org/rfc/rfc2231.html) There are also no quoted strings, like google uses. -- ___ Python tracker

[issue39045] Segmentation of string

New submission from Lovi <1668151...@qq.com>: I thought for a long time. I think it's necessary to add a segment method to str type or string module. This method is used to split a string into m parts and return all cases. For example: segment('1234', m=3) -> [('1', '2', '34'), ('1', '23',

[issue39044] Segfault on build for the master branch

Joannah Nanjekye added the comment: Confirmedforgeting to run makedistclean was the problem. -- ___ Python tracker ___ ___

[issue39044] Segfault on build for the master branch

Joannah Nanjekye added the comment: Actually my master had some segfaulting changes that I had moved to it in error. Thanks. Closing this. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue39044] Segfault on build for the master branch

Zachary Ware added the comment: If you updated an unclean checkout, try running `make distclean` before configuring and building again; that often clears this kind of thing up. -- nosy: +zach.ware ___ Python tracker

[issue39044] Segfault on build for the master branch

Change by Joannah Nanjekye : -- nosy: +pablogsal, vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39044] Segfault on build for the master branch

New submission from Joannah Nanjekye : I just pulled changes from upstream and when I build with: ./configure --with-pydebug && make -j Am getting a Segmentation fault: ./python -E -S -m sysconfig --generate-posix-vars ;\ if test $? -ne 0 ; then \ echo "generate-posix-vars failed" ;

[issue39040] Wrong attachement filename when mail mime header was too long

Manfred Kaiser added the comment: thanks for your response. I have found the RFC https://tools.ietf.org/html/rfc2184 Gmail creates wrong Headers, which are not rfc-compliant. The problem is, that many people are using gmail and emails, which were sent from Gmail might be wrong. How can we

[issue39031] Inconsistency with lineno and col_offset info when parsing elif

Change by Lysandros Nikolaou : -- pull_requests: +17068 pull_request: https://github.com/python/cpython/pull/17596 ___ Python tracker ___

[issue39043] Add math.fib() generator

Raymond Hettinger added the comment: Sorry, this isn't sufficiently useful or needed to warrant inclusion in the standard library. -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker

[issue39031] Inconsistency with lineno and col_offset info when parsing elif

Lysandros Nikolaou added the comment: There was a bug in my last PR, hopefully I will get a fix some time later today. The bug is as follows: I only updated the asdl_seq_SET call for an elif without an else, if an else is included then the behavior is like before. After my last PR it looks

[issue39043] Add math.fib() generator

Change by Karthikeyan Singaravelan : -- nosy: +mark.dickinson, rhettinger, stutzbach ___ Python tracker ___ ___ Python-bugs-list

[issue39043] Add math.fib() generator

New submission from Lovi <1668151...@qq.com>: I think it's appropriate to add the generator fib() to the math module. With fib(), some operations will be easier. The generator is like this: def fib(count=None): if count is not None and not isinstance(count, int): raise

[issue21600] mock.patch.stopall doesn't work with patch.dict

Karthikeyan Singaravelan added the comment: Thanks Mario. I think the last patch attached to the issue is complete with tests and needs to be updated master. Feel free to raise a PR. -- ___ Python tracker

[issue37224] test__xxsubinterpreters fails randomly

Kyle Stanley added the comment: > Yep, it has to use the public C-API just like any other module. The > function has a "_Py" prefix and be defined in Include/cpython, right? Yeah, I named it "_PyInterpreterIsFinalizing" and it's within Include/cpython. Definitely open to suggestions on the

[issue37228] UDP sockets created by create_datagram_endpoint() allow by default multiple processes to bind the same port

Kyle Stanley added the comment: Opened a PR that adds the whatsnew entries to master, 3.8, 3.7, and 3.6: GH-17595. -- ___ Python tracker ___

[issue37228] UDP sockets created by create_datagram_endpoint() allow by default multiple processes to bind the same port

Change by Kyle Stanley : -- pull_requests: +17067 pull_request: https://github.com/python/cpython/pull/17595 ___ Python tracker ___

[issue39036] Add center_char attribute to str type

Raymond Hettinger added the comment: Thank you for the suggestion, but this proposal isn't broadly useful enough to warrant adding a new method. -- nosy: +rhettinger resolution: -> rejected stage: -> resolved status: open -> closed ___ Python

[issue39036] Add center_char attribute to str type

Lovi <1668151...@qq.com> added the comment: Sorry, I made a mistake. The center char of '12345' is '3' and the center char of 'abcd' is '' because it doesn't have the most central character. In my opinion, with center_char, when you need the center character of a string you can get it

[issue38993] cProfile behaviour issue with decorator and math.factorial() lib.

AVicennA added the comment: @rhettinger, I did not write nowhere in my post that it's a pure bug. I use "behaviour" instead of it. And it getting me incorrect results everytime, that is why I should wrote it in here for resolving this problem. This is not about getting error message, that

[issue23930] http.cookies.SimpleCookie doesn't parse comma-only separated cookies correctly

Change by Cheryl Sabella : -- stage: patch review -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue38993] cProfile behaviour issue with decorator and math.factorial() lib.

Raymond Hettinger added the comment: This doesn't seem like an appropriate use of the bug tracker. Investigating and explaining cProfile results seems better suited for StackOverflow or some other forum. Then if an actual known bug or potential optimization arises, the bug tracker can to

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

Eric Snow added the comment: I'm out of time and this deserves some careful discussion. I'll get to it next Friday (or sooner if possible). Sorry! -- ___ Python tracker

[issue36406] doctest.testmod(empty_package) raises TypeError in 3.7 (and no errors in 3.6)

Change by Karthikeyan Singaravelan : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue36406] doctest.testmod(empty_package) raises TypeError in 3.7 (and no errors in 3.6)

Brett Cannon added the comment: New changeset aa74a53ad61134911ac7904f24fd2630aeaa8ac8 by Brett Cannon (Miss Islington (bot)) in branch '3.8': bpo-36406: Handle namespace packages in doctest (GH-12520) (GH-17591)

[issue36406] doctest.testmod(empty_package) raises TypeError in 3.7 (and no errors in 3.6)

Brett Cannon added the comment: New changeset d3212036aa2510b9e133ba4bfaf1262d6bcbe7f0 by Brett Cannon (Miss Islington (bot)) in branch '3.7': bpo-36406: Handle namespace packages in doctest (GH-12520) (GH-17592)

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

Eric Snow added the comment: Sorry for the delay, Phil. I'll try to take a look in the next couple of hours. -- ___ Python tracker ___

[issue38904] "signal only works in main thread" in main thread

Eric Snow added the comment: Before 3.8, the "signal" module checked against the thread in which the module was initially loaded, treating that thread as the "main" thread. That same was true (and still is) for the "threading" module. The problem for both modules is that the Python

[issue39042] Use the runtime's main thread ID in the threading module.

New submission from Eric Snow : The threading module has a "main_thread()" function that returns a Thread instance for the "main" thread. The main thread is the one running when the runtime is initialized and has a specific role in various parts of the runtime. Currently the threading

[issue39041] Support GitHub Actions in CI

New submission from Steve Dower : Enable support for GitHub Actions CI to do PR build and test runs. Once stable, we can deprecate Azure Pipelines PR builds. The only regression right now is that test results are not collected in a nice view like AP has. But I think that view is not widely

[issue38993] cProfile behaviour issue with decorator and math.factorial() lib.

AVicennA added the comment: In official documentation: https://docs.python.org/3/library/profile.html was not noted about the difference behaviour of cProfile in command line and into the file. -- ___ Python tracker

[issue37224] test__xxsubinterpreters fails randomly

Eric Snow added the comment: On Sat, Nov 30, 2019 at 9:23 PM Kyle Stanley wrote: > I have a few ideas that I'd like to test out for fixing this failure, and if > any of them produce positive results I'll report back. Sounds good. > Since the failures are still consistently occurring, I

[issue37224] test__xxsubinterpreters fails randomly

Eric Snow added the comment: On Sat, Nov 30, 2019 at 9:23 PM Kyle Stanley wrote: > Based on the above hint, I was able to make some progress on a potential > solution. Thanks Eric. That's great! > Instead of only checking "frame->f_executing", I changed "_is_running()" to > also check the

[issue37776] Test Py_Finalize() from a subinterpreter

Eric Snow added the comment: On Fri, Dec 13, 2019 at 11:22 AM Lewis Gaul wrote: > So it looks like adding a specific testcase for this is likely to weed out an > actual issue here! +1 -- ___ Python tracker

[issue38858] new_interpreter() should reuse more Py_InitializeFromConfig() code

Eric Snow added the comment: Thanks for working on this. It really does have far-reaching benefits, not just for the subinterpreter stuff I'm interested in. :) -- ___ Python tracker

[issue36854] GC operates out of global runtime state.

Eric Snow added the comment: On Wed, Dec 4, 2019 at 4:36 AM STINNER Victor wrote: > Each time I tried to fix a bug in the Python finalization, I introduced worse > bugs :-D :) > We cannot fix all bugs at once, we have to work incrementally. +1 > I like the idea of introducing workarounds

[issue38962] Reference leaks in subinterpreters

Eric Snow added the comment: Thanks for all the work on this! -- nosy: +eric.snow ___ Python tracker ___ ___ Python-bugs-list

[issue39031] Inconsistency with lineno and col_offset info when parsing elif

Change by Guido van Rossum : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue13586] IDLE: Replace selected not working/consistent with find

Zackery Spytz added the comment: I've created a pull request for this issue. Please take a look. -- nosy: +ZackerySpytz ___ Python tracker ___

[issue39040] Wrong attachement filename when mail mime header was too long

R. David Murray added the comment: That header is *completely* non-RFC compliant. If gmail generated that header there is something very wrong in google-land :( The RFC compliant formatting for that header looks like this: Content-Disposition: attachment;

[issue13586] IDLE: Replace selected not working/consistent with find

Change by Zackery Spytz : -- pull_requests: +17065 pull_request: https://github.com/python/cpython/pull/17593 ___ Python tracker ___

[issue39040] Wrong attachement filename when mail mime header was too long

Change by Manfred Kaiser : Added file: https://bugs.python.org/file48777/original_mail_from_gmail.eml ___ Python tracker ___ ___

[issue39040] Wrong attachement filename when mail mime header was too long

Manfred Kaiser added the comment: The mail was sent from the GMail web interface -- ___ Python tracker ___ ___ Python-bugs-list

[issue39040] Wrong attachement filename when mail mime header was too long

Manfred Kaiser added the comment: The original filename is "Schulbesuchsbestättigung.pdf", but when I use the method "get_filename" I got "Schulbesuchsbestättigung.pdf" I removed some headers from the mail for privacy reasons -- Added file:

[issue39040] Wrong attachement filename when mail mime header was too long

Change by Manfred Kaiser : Added file: https://bugs.python.org/file48775/testscript.py ___ Python tracker ___ ___ Python-bugs-list mailing

[issue37776] Test Py_Finalize() from a subinterpreter

Lewis Gaul added the comment: It seems that test_audit_subinterpreter() in _testembed.c was (unintentionally?) doing this already. After fixing #36225 I found this testcase causes a segfault, but works fine when switching back to the main threadstate before calling Py_Finalize(). So it

[issue36406] doctest.testmod(empty_package) raises TypeError in 3.7 (and no errors in 3.6)

Change by miss-islington : -- pull_requests: +17064 pull_request: https://github.com/python/cpython/pull/17592 ___ Python tracker ___

[issue36406] doctest.testmod(empty_package) raises TypeError in 3.7 (and no errors in 3.6)

Change by miss-islington : -- pull_requests: +17063 pull_request: https://github.com/python/cpython/pull/17591 ___ Python tracker ___

[issue36406] doctest.testmod(empty_package) raises TypeError in 3.7 (and no errors in 3.6)

Brett Cannon added the comment: New changeset 8289e27393395ee903bd096d42e07c112d7f15c6 by Brett Cannon (Xtreak) in branch 'master': bpo-36406: Handle namespace packages in doctest (GH-12520) https://github.com/python/cpython/commit/8289e27393395ee903bd096d42e07c112d7f15c6 -- nosy:

[issue1021318] PyThreadState_Next not thread safe

Eric Snow added the comment: On Wed, Dec 11, 2019 at 7:02 AM STINNER Victor wrote: > We may have to fix this API first, and clarify the scope of the different > locks. +1 -- ___ Python tracker

[issue39037] Wrong trial order of __exit__ and __enter__ in the with statement

Brett Cannon added the comment: @Gery please do open a documentation PR! :) -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue39040] Wrong attachement filename when mail mime header was too long

R. David Murray added the comment: Thanks for the report. Can you provide an example that reproduces the problem? Per the RFC, lines may be broken before whitespace in certain places in certain headers, but that does not make the whitespace go away. Only the crlf sequence is removed

[issue36746] Create test for fcntl.lockf()

Joannah Nanjekye added the comment: @victor looks to be the author of the change the introduced the tests that can resolve this. Victor, can we consider this closed. I have no problem closing the issue and the related PR. -- nosy: +vstinner ___

[issue39040] Wrong filename in mail when mime header was too long

Change by Manfred Kaiser : -- title: Wrong filename in when mime header was too long -> Wrong filename in mail when mime header was too long ___ Python tracker ___

[issue39040] Wrong filename in when mime header was too long

Change by Manfred Kaiser : -- keywords: +patch pull_requests: +17062 stage: -> patch review pull_request: https://github.com/python/cpython/pull/17590 ___ Python tracker ___

[issue39037] Wrong trial order of __exit__ and __enter__ in the with statement

Change by Serhiy Storchaka : -- assignee: -> docs@python components: +Documentation -Interpreter Core keywords: +easy nosy: +docs@python stage: -> needs patch ___ Python tracker

[issue39040] Wrong attachement filename when mail mime header was too long

Change by Manfred Kaiser : -- title: Wrong filename in mail when mime header was too long -> Wrong attachement filename when mail mime header was too long ___ Python tracker

[issue39040] Wrong filename in when mime header was too long

New submission from Manfred Kaiser : I'm working on a mailfilter in python and used the method "get_filename" of the "EmailMessage" class. In some cases a wrong filename was returned. The reason was, that the Content-Disposition Header had a line break and the following intention was

[issue36746] Create test for fcntl.lockf()

Dong-hee Na added the comment: @nanjekyejoannah IMHO, tests were added through bpo-22367 I think that we can close this issue. What do you think? -- nosy: +corona10 ___ Python tracker

[issue39039] zlib.error with tarfile.open

jvoisin added the comment: Sure, but as a user, I would expect a better exception, like ValueError or ReadError, along with an error message, instead of an unexpected zlib exception. -- ___ Python tracker

[issue39039] zlib.error with tarfile.open

Christian Heimes added the comment: This file is also an invalid tar file: $ tar xf crash-c10c9839d987fa0df6912cb4084f43f3ce08ca82 gzip: stdin: invalid compressed data--format violated tar: Child returned status 1 tar: Error is not recoverable: exiting now -- nosy:

[issue39038] OverflowError in tarfile.open

Christian Heimes added the comment: The file is not a valid tar file: $ tar xf crash-83a6e7d4b810c6a0bd4fd9dfd6a0b36550034ccf gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error tar: This does not look like a tar archive tar: Skipping to next

[issue39031] Inconsistency with lineno and col_offset info when parsing elif

Pablo Galindo Salgado added the comment: New changeset 3b18b17efcee6f968cf85c543254b3611311e9f4 by Pablo Galindo (Miss Islington (bot)) in branch '3.8': bpo-39031: Include elif keyword when producing lineno/col-offset info for if_stmt (GH-17582) (GH-17589)

[issue27100] Attempting to use class with both __enter__ & __exit__ undefined yields __exit__ attribute error

Change by Géry : -- nosy: +maggyero ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39038] OverflowError in tarfile.open

Change by Karthikeyan Singaravelan : -- nosy: +ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39039] zlib.error with tarfile.open

Change by Karthikeyan Singaravelan : -- nosy: +ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39039] zlib.error with tarfile.open

New submission from jvoisin : The attached file produces the following stacktrace when opened via `tarfile.open`, on Python 3.7.5rc1: ``` $ cat test.py import sys import tarfile tarfile.open(sys.argv[1]) $ python3 test.py ./crash-c10c9839d987fa0df6912cb4084f43f3ce08ca82 Traceback (most

[issue39038] OverflowError in tarfile.open

New submission from jvoisin : The attached file produces the following stacktrace when opened via `tarfile.open`, on Python 3.7.5rc1: ``` $ cat test.py import sys import tarfile tarfile.open(sys.argv[1]) $ python3 test.py ./crash-83a6e7d4b810c6a0bd4fd9dfd6a0b36550034ccf Traceback (most

[issue39037] Wrong trial order of __exit__ and __enter__ in the with statement

Géry added the comment: Thanks @mark.dickinson for the link. Can I open a documentation PR for this? -- ___ Python tracker ___ ___

[issue27495] Pretty printing sorting for set and frozenset instances

Change by SilentGhost : -- nosy: +SilentGhost type: enhancement -> behavior versions: +Python 3.7, Python 3.8, Python 3.9 -Python 3.6 ___ Python tracker ___

[issue39037] Wrong trial order of __exit__ and __enter__ in the with statement

Mark Dickinson added the comment: See issue 27100, which led to a deliberate change in behaviour to look up __enter__ before __exit__. It looks like the documentation (not the PEP text, which shouldn't be considered normative; just the reference manual) needs to be adjusted to match the new

[issue39037] Wrong trial order of __exit__ and __enter__ in the with statement

New submission from Géry : >>> class A: pass ... >>> with A(): pass ... Traceback (most recent call last): File "", line 1, in AttributeError: __enter__ I expected `AttributeError: __exit__`, since PEP 343 states

[issue39031] Inconsistency with lineno and col_offset info when parsing elif

Pablo Galindo Salgado added the comment: New changeset 0ed45d0cbfc7579dfc5527c19aa6e4bb696db2e0 by Pablo Galindo in branch '3.7': [3.7] bpo-39031: Include elif keyword when producing lineno/col-offset info for if_stmt (GH-17582) (#17584)

[issue39031] Inconsistency with lineno and col_offset info when parsing elif

Change by miss-islington : -- pull_requests: +17061 pull_request: https://github.com/python/cpython/pull/17589 ___ Python tracker ___

[issue39033] zipimport raises NameError: name '_boostrap_external' is not defined

Change by Karthikeyan Singaravelan : -- keywords: +patch pull_requests: +17060 stage: -> patch review pull_request: https://github.com/python/cpython/pull/17588 ___ Python tracker

[issue39036] Add center_char attribute to str type

Steven D'Aprano added the comment: What you mean by "center_char" is not clear to me. How is "bc" a character? It looks like two characters to me. How is "1" the center char of "12345"? It looks like the leftmost character to me. Once you have explained what "center_char" does, could you

[issue28254] Add C API for gc.enable, gc.disable, and gc.isenabled

Sergei Lebedev added the comment: I know this patch has already been rejected, but I wanted to give another potential use-case for accessing GC status from C: JIT compilers. Imagine a JIT compiler which uses alternative storage for instance attributes. In order to maintain correctness, it

[issue39034] Documentation: Coroutines

Andrew Svetlov added the comment: I suggest thinking that gather() implicitly creates tasks for running coroutines. The documentation is technically correct, enumeration of all potentially endless list of things that calls `create_task()` for wrapping passed coroutine is not very helpful,

[issue39036] Add center_char attribute to str type

New submission from Lovi <1668151...@qq.com>: I think Python3.9 needs to add the center_char attribute which means the center character of strings to string type, such as the center_char of '12345' is '1' and the center_char of 'abcd' is 'bc'. -- components: Windows messages: 358328

[issue27197] mock.patch interactions with "from" imports

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue27341] mock.patch decorating a generator returns a regular function.

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32952] Add __qualname__ for attributes of Mock instances

Karthikeyan Singaravelan added the comment: create_autospec already does recursive spec setting on the class and it has the attributes/methods mocked to retain attributes but doesn't copy the metadata of the original methods to the mock itself. I am not sure spec_set needs to do more stuff

[issue39033] zipimport raises NameError: name '_boostrap_external' is not defined

Karthikeyan Singaravelan added the comment: Sure Serhiy, I will create one. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue32952] Add __qualname__ for attributes of Mock instances

Change by Serhiy Storchaka : -- nosy: +michael.foord versions: +Python 3.9 -Python 3.8 ___ Python tracker ___ ___ Python-bugs-list

[issue39035] Travis CI fail on backports: pyvenv not installed

New submission from STINNER Victor : Example of failure of a backport from 3.8 to 3.7, PR 17577: https://github.com/python/cpython/pull/17577 """ $ python --version Python 3.6.9 $ pip --version pip 19.3.1 from /home/travis/virtualenv/python3.6.9/lib/python3.6/site-packages/pip (python 3.6)

[issue32952] Add __qualname__ for attributes of Mock instances

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue21600] mock.patch.stopall doesn't work with patch.dict

Mario Corchero added the comment: Makes total sense, I think we should get this for 3.9. Not sure I'll backport this, even if a bugfix it might cause unexpected changes (Though I'd be OK with it, given that calling stop twice causes no issue). I'm happy to push a PR with the proposed change

[issue21600] mock.patch.stopall doesn't work with patch.dict

Karthikeyan Singaravelan added the comment: This sounds like a good idea given the docs and the general agreement in the thread. I would like to target this for 3.9 . Differentiation between the normal patches and the ones from patch.dict is nice but given that docstring indicates LIFO for