[issue44429] Tkinter Flow Geometry Manager

Gary Davenport added the comment: Just an update on this issue. I did make 2 packages available on pypi.org: https://pypi.org/project/flowframe/ and https://pypi.org/project/tkinterflow/ Thank you very much for your help. -- resolution: -> works for me stage: -> resolved status

[issue44660] email.feedparser: support RFC 6532 section 3.5

Francis Johnson added the comment: The first paragraph of section 3.5 states two positions that the RFC holds on Content-Transfer-Encodings: (1) “allows newly defined MIME types to permit content-transfer-encoding;” and (2) “allows content-transfer-encoding for message/global (see Section 3.7)

[issue44660] email.feedparser: support RFC 6532 section 3.5

R. David Murray added the comment: Having looked at the cited part of the RFC (but not tried to analyze it in detail), I think you are correct. I've also glanced at your PR, and I think your approach is correct in broad outline, but I haven't looked at the details. For full message/global

[issue44730] unittest.mock.patch does not work as a decorator on generator functions

Change by Gareth Williams : -- keywords: +patch pull_requests: +25860 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27315 ___ Python tracker ___

[issue44694] Message from BytesParser cannot be flattened immediately

R. David Murray added the comment: I suspect maxheaderlen=0 works because it causes the original lines to be re-emitted without any folding or other processing. Without that, lines longer than the default max_line_length get refolded. Can you provide an example of an input message that trig

[issue44685] Email package issue with Outlook msg files

R. David Murray added the comment: That file appears to be a binary file? By itself it isn't enough to reproduce the problem. Can you provide a complete script as well as the email message you are parsing that demonstrates the problem? By "looks like any other eml file", are you including

[issue44722] RFC: string Multiline Formatter

creative-resort added the comment: Thank you for your kind guidance :) -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue42357] Wrong Availability for signal.SIGCHLD

Andrei Kulakov added the comment: This can be closed (fixed). -- nosy: +andrei.avk ___ Python tracker ___ ___ Python-bugs-list mail

[issue42357] Wrong Availability for signal.SIGCHLD

Zachary Ware added the comment: You are correct, thanks for the ping Andrei. And thank you for the patch, Maiyun! -- nosy: +zach.ware resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.8, Python 3.9 ___

[issue44720] Finding string in iteratively deleted object cause segfault

Change by Dennis Sweeney : -- keywords: +patch nosy: +Dennis Sweeney nosy_count: 1.0 -> 2.0 pull_requests: +25862 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27316 ___ Python tracker

[issue44720] Weakref proxy crashes on null tp_iternext slot.

Dennis Sweeney added the comment: Here's a simpler reproducer: not_an_iterator = lambda: 0 class A: def __iter__(self): return weakref.proxy(not_an_iterator) a = A() list(a) I opened a PR. -- title: Finding string in iterat

[issue44719] Incorrect callable object crashes Python 3.11.0a0

Dennis Sweeney added the comment: I think GH-27313 will fix this -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue44693] Unclear definition of the "__future__" module in Docs

Steven D'Aprano added the comment: What exactly is a "pseudo-module"? I can only imagine it is something like sys, which exists internally in the interpreter but doesn't have an independent existence as a .py .dll or .so file. That's not the case with `__future__`, which is an *actual* modul

[issue38291] Deprecate the typing.io and typing.re pseudo-modules

Change by Ken Jin : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Pytho

[issue44693] Unclear definition of the "__future__" module in Docs

Terry J. Reedy added the comment: I agree with Steven's more careful analysis and with canning 'pseudo'. Current suggestion. A *future statement*, "from __future__ import *feature* ...", directs the compiler to compile the current module using syntax or semantics that will become standard

[issue44674] dataclasses should allow frozendict default value

Gianni Mariani added the comment: @Arjun - this is about default values (See the bug description - Using a frozendict as a default value) Try this: from frozendict import frozendict from dataclasses import dataclass @dataclass class A: a: frozendict = frozendict(a=1) This used to work

<    1   2