[issue40612] Make traceback module's formatting of SyntaxError more similar to system formatting

Guido van Rossum added the comment: My current PR does not strip trailing whitespace. It only strips a single trailing newline (since this is usually but not always present, and we don't want to its presence to cause an extra blank line, nor do we want its absence to cause the text lin

[issue40612] Make traceback module's formatting of SyntaxError more similar to system formatting

Guido van Rossum added the comment: (And, to be clear, I don't *want* to strip trailing spaces.) -- ___ Python tracker <https://bugs.python.org/is

[issue40627] Bus error on 'except E as a.b:'

New submission from Guido van Rossum : This seems due to some new check in pegen: >>> try: ... pass ... except E as a.b: ... pass ... Bus error: 10 -- messages: 368860 nosy: gvanrossum, lys.nikolaou, pablogsal priority: normal severity: normal stage: needs patch sta

[issue40627] Bus error on 'except E as a.b:'

Guido van Rossum added the comment: Oh, looks like https://github.com/python/cpython/pull/20083 fixes it. -- keywords: +patch message_count: 1.0 -> 2.0 pull_requests: +19397 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull

[issue40627] Bus error on 'except E as a.b:'

Guido van Rossum added the comment: Sorry! -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed superseder: -> PEG Parser: Invalid targets for augassign and except succeed ___ Python tracker <https://

[issue40246] Different error messages for same error - invalid string prefixes

Guido van Rossum added the comment: We should run the tests with the old parser in at least one build. -- ___ Python tracker <https://bugs.python.org/issue40

[issue40661] The new parser segfaults when parsing invalid input

Guido van Rossum added the comment: How costly is PyErr_Occurred()? That worries me most, otherwise I’d accept this right away. -- ___ Python tracker <https://bugs.python.org/issue40

[issue40661] The new parser segfaults when parsing invalid input

Guido van Rossum added the comment: I see almost no time difference for 'make time_stdlib': before 3.471, after 3.451. But I see a serious difference for 'make time_compile': before 3.474, after 4.996. That's over 40% slower (on the extreme case, xxl.py). I

[issue40661] The new parser segfaults when parsing invalid input

Change by Guido van Rossum : -- keywords: +patch pull_requests: +19462 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/20159 ___ Python tracker <https://bugs.python.org/issu

[issue40612] Make traceback module's formatting of SyntaxError more similar to system formatting

Change by Guido van Rossum : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue13601] sys.stderr should be line-buffered when stderr is not a TTY

Guido van Rossum added the comment: Can you submit a PR and CC me? -- ___ Python tracker <https://bugs.python.org/issue13601> ___ ___ Python-bugs-list mailin

[issue40661] The new parser segfaults when parsing invalid input

Guido van Rossum added the comment: Zac: The reproducer here apparently uses a long string of weird accented characters. I'm not sure how to generalize from that to other things that Hyothes* could find. But maybe this helps: https://github.com/python/cpython/pull/20106#issueco

[issue40669] PEG Parser benchmarks fail if memory_profiler is not installed

Guido van Rossum added the comment: Why not just install it? -- ___ Python tracker <https://bugs.python.org/issue40669> ___ ___ Python-bugs-list mailin

[issue40661] The new parser segfaults when parsing invalid input

Guido van Rossum added the comment: Unfortunately, I do not understand enough about how Hypothes* works to be helpful here, other than by offering encouragement. (And please don't try to educate me. I have too many other things.

[issue40669] PEG Parser benchmarks fail if memory_profiler is not installed

Guido van Rossum added the comment: Soon nobody will remember to look at the memory stats at all. But I will review. -- ___ Python tracker <https://bugs.python.org/issue40

[issue40661] The new parser segfaults when parsing invalid input

Guido van Rossum added the comment: Okay, deferring the blocker. But I'll still land Lysandros' fix ASAP. -- priority: release blocker -> deferred blocker ___ Python tracker <https://bugs.pytho

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.10

Guido van Rossum added the comment: Too bad nobody took any action here after the positive outcome of the discussion at the summit. -- components: +Interpreter Core -Library (Lib) stage: -> needs patch type: -> behavior versions: -Pyth

[issue42474] improve test coverage for TracebackException's __eq__

Guido van Rossum added the comment: New changeset 44ca05afc89c9967f5dbc6c3ad89fc298c460e93 by Irit Katriel in branch 'master': bpo-42474: test TracebackException comparison to non-equal instances (GH-23522) https://github.com/python/cpython/commit/44ca05afc89c9967f5dbc6c3ad89fc

[issue42482] TracebackException should not hold reference to the exception traceback

Guido van Rossum added the comment: For background, see https://github.com/iritkatriel/cpython/pull/3#issuecomment-734640036 -- it seems the link to exc_traceback was added with little concern for the original design of TracebackExceptionGroup. The question is, can we get rid of it, even

[issue42474] improve test coverage for TracebackException's __eq__

Guido van Rossum added the comment: Irit, can you,do the manual backports? -- ___ Python tracker <https://bugs.python.org/issue42474> ___ ___ Python-bugs-list m

[issue42195] Inconsistent __args__ between typing.Callable and collections.abc.Callable

Guido van Rossum added the comment: Now that I've seen and reviewed KJ's implementation using _PosArgs, I am worried about it, as it looks quite complicated. @Shantanu, do we really need to worry that Callable[P, R] could be ambiguous? If P is a ParamSpec, wouldn't Call

[issue42474] improve test coverage for TracebackException's __eq__

Guido van Rossum added the comment: New changeset 586bdd1add2ca7236e3096ab7167862cf17f0939 by Irit Katriel in branch '3.9': [3.9] bpo-42474: test TracebackException comparison to non-equal instances (GH-23557) https://github.com/python/cpython/commit/586bdd1add2ca7236e3096ab716786

[issue42474] improve test coverage for TracebackException's __eq__

Guido van Rossum added the comment: New changeset d82e08d185d52086f4d921c08b853c76c80bebbe by Irit Katriel in branch '3.8': [3.8] bpo-42474: test TracebackException comparison to non-equal instances (GH-23558) https://github.com/python/cpython/commit/d82e08d185d52086f4d921c08b853c

[issue42474] improve test coverage for TracebackException's __eq__

Guido van Rossum added the comment: Thanks! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue40939] Remove the old parser

Guido van Rossum added the comment: Hm, I wonder if there's a typo here in pythonrun.c: /* For use in Py_LIMITED_API */ #undef Py_CompileString PyObject * PyCompileString(const char *str, const char *filename, int start) { return Py_CompileStringFlags(str, filename, start,

[issue38352] In typing docs, note explicit import needed for IO and Pattern/Match

Guido van Rossum added the comment: Wait, is the OP maybe that there’s a difference between typeshed an the stdlib typing.py? -- ___ Python tracker <https://bugs.python.org/issue38

[issue42576] Passing keyword arguments to types.GenericAlias causes a hard crash

Guido van Rossum added the comment: Oh, this looks like I copied the wrong idiom. Good catch! -- ___ Python tracker <https://bugs.python.org/issue42576> ___ ___

[issue42576] Passing keyword arguments to types.GenericAlias causes a hard crash

Guido van Rossum added the comment: Thanks for the quick fix! -- ___ Python tracker <https://bugs.python.org/issue42576> ___ ___ Python-bugs-list mailin

[issue42059] TypedDict(...) as function does not respect "total" when setting __required_keys__ and __optional_keys__

Guido van Rossum added the comment: Looking for another reviewer. -- ___ Python tracker <https://bugs.python.org/issue42059> ___ ___ Python-bugs-list mailin

[issue41559] Add support for PEP 612 to typing.py

Guido van Rossum added the comment: Thanks for working on this -- let me know when you have a question for me. Once this is ready we should also add it to the typing_extensions module so people can use it on older Python versions. (https://github.com/python/typing/tree/master

[issue41559] Add support for PEP 612 to typing.py

Guido van Rossum added the comment: I wrote class C(Generic[T, P]): ... and was surprised that C.__parameters__ was (T,) instead of (T, P). -- ___ Python tracker <https://bugs.python.org/issue41

[issue39707] Abstract property setter/deleter implementation not enforced, but documented as such

Guido van Rossum added the comment: Josh, feel free to submit a PR (make sure it mentions this issue). -- ___ Python tracker <https://bugs.python.org/issue39

[issue41559] Add support for PEP 612 to typing.py

Guido van Rossum added the comment: > class X(Generic[T, P]): ... > > 1. X[int, [int, bool]] raises TypeError because second arg isn't a type (this > is easy to fix). How would you fix it? By just allowing it? But then X.__args__ would be unhashable (see the other issue

[issue41559] Add support for PEP 612 to typing.py

Guido van Rossum added the comment: For reference, here's what Pyre has (though it's an older version): https://github.com/facebook/pyre-check/tree/master/pyre_extensions -- ___ Python tracker <https://bugs.python.o

[issue41559] Add support for PEP 612 to typing.py

Guido van Rossum added the comment: I started doing this in the original code (long ago when PEP 484 was brand new) but have since realized that this makes the typing module both slow and hard to maintain. We should not follow this example. I do think we should try to keep `__args__` hashable

[issue42195] Inconsistent __args__ between typing.Callable and collections.abc.Callable

Guido van Rossum added the comment: New changeset 463c7d3d149283814d879a9bb8411af64e656c8e by kj in branch 'master': bpo-42195: Ensure consistency of Callable's __args__ in collections.abc and typing (GH-23060) https://github.com/python/cpython/commit/463c7d3d149283814d879a9bb

[issue41559] Add support for PEP 612 (Parameter Specification Variables) to typing.py

Guido van Rossum added the comment: This is now unblocked now that GH-23060 has landed. -- ___ Python tracker <https://bugs.python.org/issue41559> ___ ___ Pytho

[issue42195] Inconsistent __args__ between typing.Callable and collections.abc.Callable

Guido van Rossum added the comment: New changeset 33b3fedd43e10e5a227ec8b7d251496e7cad4717 by kj in branch '3.9': [3.9] bpo-42195: Ensure consistency of Callable's __args__ in collections.abc and typing (GH-23765) https://github.com/python

[issue42195] Inconsistent __args__ between typing.Callable and collections.abc.Callable

Guido van Rossum added the comment: Looks like we can close this. Thanks for the report Zac (hopefully you can live with the resolution), and thanks a bundle Ken Jin for all your work on this! I hope it was fun and educational for you. I know it was for me. -- resolution: -> fi

[issue42577] Unhelpful syntax error when expression spans multiple lines

Guido van Rossum added the comment: I think something should probably be done about this, but opening another tracker issue is not the way to make progress here. So I am closing the issue. It will happen in due time. No need to have more open issues. -- stage: -> resolved sta

[issue41960] Add globalns and localns to the inspect.signature and inspect.Signature.from_callable

Guido van Rossum added the comment: It's been a while, I've lost context for this idea. What problem are you trying to solve here? Are there issues where people have reported problems that this would allow them to solve? -- ___ Pyth

[issue42675] Document changes made in bpo-42195

Guido van Rossum added the comment: New changeset d75f6f78e6ca230d0dacc116dca9d8bf91509b68 by kj in branch 'master': bpo-42675: Document collections.abc.Callable changes (GH-23839) https://github.com/python/cpython/commit/d75f6f78e6ca230d0dacc116dca9d8

[issue42683] asyncio should handle keyboard interrupt while the event loop is running

Change by Guido van Rossum : -- nosy: +gvanrossum ___ Python tracker <https://bugs.python.org/issue42683> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42675] Document changes made in bpo-42195

Guido van Rossum added the comment: New changeset 597ebc8cf604de49eabbc7b83be2debd005d7819 by kj in branch '3.9': [3.9] bpo-42675: Document collections.abc.Callable changes (GH-23839) (#23852) https://github.com/python/cpython/commit/597ebc8cf604de49eabbc7b83be2de

[issue42675] Document changes made in bpo-42195

Guido van Rossum added the comment: Can this be closed now? -- ___ Python tracker <https://bugs.python.org/issue42675> ___ ___ Python-bugs-list mailin

[issue42725] PEP 563: Should the behavior change for yield/yield from's

Guido van Rossum added the comment: Ouch. I think we should generate a SyntaxError if yield [from] is used in an annotation. -- ___ Python tracker <https://bugs.python.org/issue42

[issue42725] PEP 563: Should the behavior change for yield/yield from's

Change by Guido van Rossum : -- nosy: +lys.nikolaou ___ Python tracker <https://bugs.python.org/issue42725> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42725] PEP 563: Should the behavior change for yield/yield from's

Guido van Rossum added the comment: The difference is that that just causes a slight inefficiency, while processing 'yield' makes the function a generator. So I don't feel as strongly about that. -- ___ Python tracker <https

[issue42725] PEP 563: Should the behavior change for yield/yield from's

Guido van Rossum added the comment: If we simply ignored yield in the annotation, wouldn't we have the problem that def f(a: (yield)): pass silently changes from being a generator (in 3.9) to not being a generator (in 3.10)? That would be bad. I'd rather make this an error still

[issue41559] Add support for PEP 612 (Parameter Specification Variables) to typing.py

Guido van Rossum added the comment: New changeset 73607be68668ab7f4bee53507c8dc7b5a46c9cb4 by kj in branch 'master': bpo-41559: Implement PEP 612 - Add ParamSpec and Concatenate to typing (#23702) https://github.com/python/cpython/commit/73607be68668ab7f4bee53507c8dc7

[issue41559] Add support for PEP 612 (Parameter Specification Variables) to typing.py

Guido van Rossum added the comment: Huge thanks! I think the next step is to port the essence to typing_extensions, which has to work for anything from 3.5 up (or maybe 3.6), *including* 3.10 and above. https://github.com/python/typing/tree/master/typing_extensions Honestly maybe we could

[issue42725] PEP 563: Should the behavior change for yield/yield from's

Guido van Rossum added the comment: Okay, let's do it. It should probably a post-parse check (before we invoke the bytecode compiler but after we have the AST in hand). -- ___ Python tracker <https://bugs.python.org/is

[issue40494] collections.abc.Callable and type variables

Guido van Rossum added the comment: Indeed. Thanks! -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue42737] PEP 563: drop annotations for complex assign targets

Guido van Rossum added the comment: So the distinction between simple and complex is to define what goes into `__annotations__`. As long as we don't disturb that I think it's fine not to evaluate anything. (There's also the effect on what's considered a local variab

[issue42737] PEP 563: drop annotations for complex assign targets

Guido van Rossum added the comment: Yeah, we're talking about a future here where `from __future__ import annotations` is always on. And that future is now. (3.10) -- ___ Python tracker <https://bugs.python.org/is

[issue42093] Add opcode cache for LOAD_ATTR

Guido van Rossum added the comment: Wow, this is amazing. I just found that this is now faster than slots. Should we mention that in What's New? (Of course there's an optimization possible for slots as well, but it would require complicating the cache struct. May

[issue42740] typing.py get_args and get_origin should support PEP 604 and 612

Guido van Rossum added the comment: New changeset efb1f0918fad2ba3346a986b0e958dc5753a7bbe by Ken Jin in branch 'master': bpo-42740: Support PEP 604, 612 for typing.py get_args and get_origin (GH-23942) https://github.com/python/cpython/commit/efb1f0918fad2ba3346a986b0e958d

[issue42740] typing.py get_args and get_origin should support PEP 604 and 612

Change by Guido van Rossum : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue42775] __init_subclass__ should be called in __init__

Guido van Rossum added the comment: Whoa, you start a discussion on python-dev and another on bpo? That sounds a bit hasty. -- nosy: +gvanrossum ___ Python tracker <https://bugs.python.org/issue42

[issue42775] __init_subclass__ should be called in __init__

Guido van Rossum added the comment: I see this as a backwards incompatible change and it's not worth doing for what seems to me a very minor benefit. -- ___ Python tracker <https://bugs.python.org/is

[issue40631] PEG Parser: Cannot used starred expression in parenthesised expr

Guido van Rossum added the comment: Honestly this seems like a bug in 3.8 to me (if it indeed behaves like this): >>> (*x), y (1, 2, 3) Every time I mistakenly tried (*x) I really meant (*x,), so it's surprising that (*x), y would be interpreted as (*x, y) rather than flagg

[issue40631] PEG Parser: Cannot used starred expression in parenthesised expr

Guido van Rossum added the comment: > It makes sense to me to be able to do `(*a), b` if I can do `*a, b`, but I > don't really have a strong opinion on it. I disagree. *a is not an expression, so the normal rules for parenthesizing those don't apply. I've always thoug

[issue42806] Incorrect offsets in new parser for f-string substitutions

Guido van Rossum added the comment: Did you check this with master? -- ___ Python tracker <https://bugs.python.org/issue42806> ___ ___ Python-bugs-list mailin

[issue41559] Add support for PEP 612 (Parameter Specification Variables) to typing.py

Guido van Rossum added the comment: New changeset 11276cd9c49faea66ce7760f26a238d1edbf6421 by Ken Jin in branch 'master': bpo-41559: Documentation for PEP 612 (GH-24000) https://github.com/python/cpython/commit/11276cd9c49faea66ce7760f26a238

[issue41559] Add support for PEP 612 (Parameter Specification Variables) to typing.py

Guido van Rossum added the comment: Looks like we can close this now, right? You can open a separate issue in the python/typing repo to update typing_extensions. -- ___ Python tracker <https://bugs.python.org/issue41

[issue40636] Provide a strict form of zip (PEP-618) requiring same length inputs

Guido van Rossum added the comment: That's fair. How do other builtins validate their pickling implementation? Since the pickling goes through __reduce__/__reduce_ex__ we could instead test that those methods return the expected results, that pickling roundtrips, and that unpickling

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Guido van Rossum added the comment: This issue probably needs a new champion. There is broad agreement but some bike shedding, so a PEP isn’t needed.-- --Guido (mobile) -- ___ Python tracker <https://bugs.python.org/issue28

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Guido van Rossum added the comment: Excellent! -- ___ Python tracker <https://bugs.python.org/issue28937> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40636] Provide a strict form of zip (PEP-618) requiring same length inputs

Guido van Rossum added the comment: Sounds good, go for it. I assume @brandtbucher won't mind. -- ___ Python tracker <https://bugs.python.org/is

[issue42824] get_type_hints throws for local class reference

Guido van Rossum added the comment: This is a known limitation. To get this to work you have to pass globals() and locals(): typing.get_type_hints(Test, globals(), locals()) -- nosy: +gvanrossum resolution: -> wont fix stage: -> resolved status: open -&g

[issue42093] Add opcode cache for LOAD_ATTR

Guido van Rossum added the comment: Thanks! Do you have any plans for further inline caches? I was wondering if we could reverse the situation for slots again by adding slots support to the LOAD_ATTR opcode inline cache... -- nosy: +gvanrossum

[issue40810] sqlite3 test CheckTraceCallbackContent fails for sqlite v3.7.3 through 3.7.14.1

Guido van Rossum added the comment: Please ping this issue if the backports don't auto-merge after the tests pass, or if the tests fail. -- nosy: +gvanrossum ___ Python tracker <https://bugs.python.org/is

[issue4714] print opcode stats at the end of pybench runs

Change by Guido van Rossum : -- resolution: -> out of date stage: patch review -> resolved status: languishing -> closed ___ Python tracker <https://bugs.python.o

[issue42115] Caching infrastructure for the evaluation loop: specialised opcodes

Change by Guido van Rossum : -- nosy: +Guido.van.Rossum ___ Python tracker <https://bugs.python.org/issue42115> ___ ___ Python-bugs-list mailing list Unsub

[issue42093] Add opcode cache for LOAD_ATTR

Guido van Rossum added the comment: Hm, I was thinking to recognize the specific type of descriptor used by slots and cache only that. Though we would still have to consider updates to C.__dict__ (that's handled by looking at the dict version

[issue42829] get_type_hints throws for nested class with __future__ annotations

Guido van Rossum added the comment: If you want this to work you have to pass the namespace where B is defined as locals to get_type_hint(). The recommended approach is to make B a global class; where that is not possible (as in your second example) you should chose a different name. We&#x

[issue42828] Python readline module

Guido van Rossum added the comment: This should be discussed on a user forum, not in our bug tracker. -- nosy: +gvanrossum resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue42835] Can't Built libxml2 When Using Python 3.9.x

Guido van Rossum added the comment: Have you approached the libxml2 developers with this problem? -- nosy: +gvanrossum ___ Python tracker <https://bugs.python.org/issue42

[issue42835] Can't Built libxml2 When Using Python 3.9.x

Guido van Rossum added the comment: Maybe libxml is using a deprecated API or an invalid combination of command line flags. I don't feel like debugging this until there's a clearer indication of who's at fault. -- ___ Python

[issue42115] Caching infrastructure for the evaluation loop: specialised opcodes

Guido van Rossum added the comment: I've skimmed several papers by Stefan Brunthaler about something called Quickening that I first found via the Pyston blog, which linked to an ancient bpo issue with a patch created by Stefan (https://bugs.python.org/issue14757). The gist seems to

[issue42115] Caching infrastructure for the evaluation loop: specialised opcodes

Guido van Rossum added the comment: Do we have good intuition or data about which operations need speeding up most? Everybody always assumes it's BINARY_ADD, but much Python code isn't actually numeric, and binary operations aren't all that common. (For example, IIRC at my pr

[issue42835] Can't Built libxml2 When Using Python 3.9.x

Guido van Rossum added the comment: Looks to me like this line is at fault: 607 | } else if PyLong_Check(obj) { That's not valid C. In the GitHub mirror this line has been corrected. -- resolution: -> third party stage: -> resolved status: ope

[issue42835] Can't Built libxml2 When Using Python 3.9.x

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <https://bugs.python.org/issue42835> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42725] PEP 563: Should the behavior change for yield/yield from's

Guido van Rossum added the comment: Yield in an annotation should be a syntax error. -- ___ Python tracker <https://bugs.python.org/issue42725> ___ ___ Pytho

[issue42837] Symbol table incorrectly identifies code as a generator, when 'yield' occurs in an annotation

Change by Guido van Rossum : -- nosy: +gvanrossum, lys.nikolaou, pablogsal ___ Python tracker <https://bugs.python.org/issue42837> ___ ___ Python-bugs-list mailin

[issue42845] Third Party Module Installation using pip fails in Python 3.10.0a3

Guido van Rossum added the comment: This is expected -- those modules contain C extensions for which no 3.10 wheels are available from PyPI yet, so pip tries to build them locally. If you want to help testing, please install the recommended free version of the MS C++ compiler. From CPython

[issue42841] Add bitwise or operator to collections.abc Mapping and MutableMapping

Guido van Rossum added the comment: This was discussed during the PEP review and rejected. The main reason is that this operator would need to create a new instance, and there is no standard API that's part of the Mapping protocol that can be used (the constructor of a Mapping ins

[issue42840] `type` takes **kwargs for __init_subclass__

Guido van Rossum added the comment: That sounds intentional to me (else the class statement would have a capability that cannot be dynamically emulated by calling type()). We should probably update the docs (if you could submit a small PR that would be appreciated) and also typeshed (ditto

[issue42839] SourceFileLoader does not (fully) accept path-like objects

Guido van Rossum added the comment: Maybe Brett can help? -- nosy: +brett.cannon, gvanrossum ___ Python tracker <https://bugs.python.org/issue42839> ___ ___

[issue42115] Caching infrastructure for the evaluation loop: specialised opcodes

Guido van Rossum added the comment: Undoubtedly -- but impact should be measured on what typical users would see, not on narrow benchmarks. -- ___ Python tracker <https://bugs.python.org/issue42

[issue42839] SourceFileLoader does not (fully) accept path-like objects

Guido van Rossum added the comment: If Brett's theory is right, compile() has a bug though -- it shouldn't plug a non-string into the code object. Or possibly the code object constructor should reject such objects (or extract

[issue42840] `type` takes **kwargs for __init_subclass__

Guido van Rossum added the comment: Excellent! -- ___ Python tracker <https://bugs.python.org/issue42840> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42847] Normalise file encodings in Lib/sqlite3/test/

Guido van Rossum added the comment: SGTM, the use of ISO-8859 is surely a legacy issue. -- nosy: +gvanrossum ___ Python tracker <https://bugs.python.org/issue42

[issue42848] asyncio produces an unexpected traceback with recursive __getattribute__

Guido van Rossum added the comment: Is there anything specific about __getattribute__ here? Wouldn't you have the same issue for *any* function that raises RecursionError called inside an async def? -- nosy: +gvanrossum ___ Python tracker &

[issue42848] asyncio produces an unexpected traceback with recursive __getattribute__

Guido van Rossum added the comment: The recursion error is actually inside the traceback module. The reason is that the code there calls itself recursively for each level of context. Since bar() builds up an endless chain of contexts as it calls itself recursively, that chain is very long

[issue42848] asyncio produces an unexpected traceback with recursive __getattribute__

Guido van Rossum added the comment: No problem. Riot, are you interested in this? -- nosy: +Guido.van.Rossum, iritkatriel ___ Python tracker <https://bugs.python.org/issue42

[issue42848] asyncio produces an unexpected traceback with recursive __getattribute__

Guido van Rossum added the comment: I meant Irit. Silly autocorrect. -- ___ Python tracker <https://bugs.python.org/issue42848> ___ ___ Python-bugs-list mailin

[issue42859] smtplib: recipe for certifying message delivery

Guido van Rossum added the comment: This looks more like a question than an issue. Have you tried stackoverflow or a user forum? -- nosy: +gvanrossum ___ Python tracker <https://bugs.python.org/issue42

[issue42725] PEP 563: Should the behavior change for yield/yield from's

Guido van Rossum added the comment: I wouldn’t have thought you’d need a PEP for this but if you want to write one that sounds like the right thing. Re: async and walrus: I think those are different, their presence doesn’t affect the meaning of the function like yield. We can’t hope to

[issue42858] Incorrect return value for os.system() in recognizing import error

Change by Guido van Rossum : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

<    22   23   24   25   26   27   28   29   30   31   >