[issue5866] cPickle defect with tuples and different from pickle output

New submission from Jelle : Python 2.5.2 (r252:60911, Oct 5 2008, 19:24:49) [GCC 4.3.2] on linux2 >>> print cPickle.dumps(('a','b')) == cPickle.dumps(('a', str('b'))) False >>> print pickle.dumps(('a','

[issue5866] cPickle defect with tuples and different from pickle output

Changes by Jelle : -- type: -> behavior ___ Python tracker <http://bugs.python.org/issue5866> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue46330] Simplify the signature of __exit__

New submission from Jelle Zijlstra : With Irit's recent changes (bpo-45711), the (typ, exc, tb) tuple is now always redundant with just exc. As a result, `__exit__` methods now should only need to accept a single argument. If we were designing the context manager protocol from scratc

[issue46330] Simplify the signature of __exit__

Jelle Zijlstra added the comment: Thanks, that would work in normal cases but can cause issues if __exit__ takes *args. Still, that may be enough of an edge case that we can get it to work. -- ___ Python tracker <https://bugs.python.

[issue46342] Make @final introspectable at runtime

New submission from Jelle Zijlstra : Currently, @typing.final is implemented as an identity function, which makes it impossible for type checkers that look at runtime objects to support it. I propose that we implement it as something like: def final(f): try: f

[issue46342] Make @final introspectable at runtime

Change by Jelle Zijlstra : -- keywords: +patch pull_requests: +28732 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/30530 ___ Python tracker <https://bugs.python.org/issu

[issue46371] A better way to resolve ForwardRefs in type aliases across modules

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue46371> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46386] Improve `test_typing::test_immutability_by_copy_and_pickle`

Jelle Zijlstra added the comment: The additional tests would also be useful to have in https://github.com/python/typing/tree/master/typing_extensions if you're interested. -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.py

[issue46414] Add typing.reveal_type

New submission from Jelle Zijlstra : The `reveal_type()` primitive is injected by type checkers into the builtins. When the type checker sees a call, it prints the inferred type of the argument. This has been implemented across all type checkers, but adding an implementation to `typing

[issue46414] Add typing.reveal_type

Change by Jelle Zijlstra : -- keywords: +patch pull_requests: +28848 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30646 ___ Python tracker <https://bugs.python.org/issu

[issue46399] Addition of `mapping` attribute to dict views classes has inadvertently broken type-checkers

Jelle Zijlstra added the comment: The types of `.keys()`, `.items()`, and `.values()` on `collections.OrderedDict` are distinct from those for dict, and they are also not exposed anywhere. Should we put them in a public, documented place too for consistency? >>> import collectio

[issue46399] Addition of `mapping` attribute to dict views classes has inadvertently broken type-checkers

Jelle Zijlstra added the comment: I see the concerns about exposing too many implementation details. But I'm also not sure how much this will really help static typing use cases. Alex's examples just call super().keys(), but if you do that, there's not much point in overridin

[issue1284670] Allow to restrict ModuleFinder to get "direct" dependencies

Jelle Zijlstra added the comment: Mike's fix unfortunately didn't work out. What are the rules about closing old enhancement requests? modulefinder is an old and rarely used package, and I feel like the use case is better served by a PyPI package. -- nosy: +Jell

[issue46442] testExceptionCleanupNames doesn't test anything?

Jelle Zijlstra added the comment: Perhaps it's testing that the implicit `del` doesn't blow up if the variable is already deleted. -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.o

[issue22833] The decode_header() function decodes raw part to bytes or str, depending on encoded part

Jelle Zijlstra added the comment: This behavior is definitely unfortunate, but by now it's also been baked into more than a decade of Python 3 releases, so backward compatibility constraints make it difficult to fix. How can we be sure this change won't break users' code?

[issue46415] ipaddress.ip_{address, network, interface} raises TypeError instead of ValueError if given a tuple as address

Jelle Zijlstra added the comment: Duplicate of issue46141. -- nosy: +Jelle Zijlstra resolution: -> duplicate stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue46448] TypedDict inspect.signature error

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue46448> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46454] '0 -> /dev/null' is lost

Jelle Zijlstra added the comment: This sounds like a consequence of PEP 446. -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue46

[issue36643] Forward reference is not resolved by dataclasses.fields()

Jelle Zijlstra added the comment: I don't think we should merge this change. get_type_hints() is fragile and full of corner cases around using the right globals and locals dictionaries. dataclasses shouldn't execute it implicitly for you. -- nosy: +Jelle Zijlstra version

[issue44799] typing.get_type_hints() raises TypeError for a variable annotated by dataclasses.InitVar

Jelle Zijlstra added the comment: I think this should be fixed in typing.py instead. get_type_hints() should be less strict about what it accepts as a type, so users are free to use annotations in innovative ways. Static type checkers should have the job of enforcing that type annotations

[issue46468] http.server documentation missing default value for port

New submission from Jelle Zijlstra : "python -m http.server" works and listens on port 8000, but the docs suggest you always have to pass the port. PR incoming. -- assignee: Jelle Zijlstra components: Documentation messages: 411230 nosy: Jelle Zijlstra priority: norma

[issue46468] http.server documentation missing default value for port

Change by Jelle Zijlstra : -- keywords: +patch pull_requests: +28961 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30776 ___ Python tracker <https://bugs.python.org/issu

[issue46396] Typing: test invalid usages of `Concatenate`

Jelle Zijlstra added the comment: Let's change typing_extensions.py too in the same way. Speaking of typing-extensions, it'd be great if someone could review https://github.com/python/typing/pull/963 :) -- ___ Python track

[issue46475] Document use of NoReturn as a bottom type

New submission from Jelle Zijlstra : At the moment, https://docs.python.org/3.10/library/typing.html#typing.NoReturn simply says: Special type indicating that a function never returns. In practice, type checkers accept NoReturn as a bottom type in other positions too. We should document

[issue46475] Document use of NoReturn as a bottom type

Change by Jelle Zijlstra : -- components: +Library (Lib) versions: +Python 3.10, Python 3.11, Python 3.9 ___ Python tracker <https://bugs.python.org/issue46

[issue32007] deprecate the nis module

Jelle Zijlstra added the comment: PEP 549 lists nis among modules to be removed: https://www.python.org/dev/peps/pep-0594/#nis For what it's worth, when I built 3.11 from source on Ubuntu 16.04 I managed to build the nis extension, without installing any special libraries

[issue46479] Implement typing.reveal_locals

New submission from Jelle Zijlstra : Implement typing.reveal_locals() as proposed in https://mail.python.org/archives/list/typing-...@python.org/thread/5MGN6HZWTJELNLIUOXTHLIXVLKZCEWY2/. This is a marker for type checkers that causes them to emit the types of all local variables

[issue46480] Implement typing.assert_type

New submission from Jelle Zijlstra : Implement typing.assert_type as proposed in https://mail.python.org/archives/list/typing-...@python.org/thread/MITFQ6Z45RRMXY3HNM66IC3XXS3TA3JN/. This is a special primitive that asserts to the type checker what the type of an expression is. Tentatively

[issue31698] Add REQ_NAME to the node.h API

Jelle Zijlstra added the comment: The PR was closed for lack of interest. -- resolution: -> wont fix stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue27219] turtle.fillcolor doesn't accept a tuple of floats

Change by Jelle Zijlstra : -- assignee: Jelle Zijlstra -> ___ Python tracker <https://bugs.python.org/issue27219> ___ ___ Python-bugs-list mailing list Un

[issue46475] typing.Never and typing.assert_never

Jelle Zijlstra added the comment: Based on feedback here and on typing-sig I'm now leaning towards adding typing.Never along with typing.assert_never. I'll submit a single patch for these as the documentation will be closely linked. -- title: Document use of NoReturn a

[issue46491] typing: allow Annotated in outermost scope

Jelle Zijlstra added the comment: I support making this change. It looks like the simplest implementation is simply to remove the mention of ClassVar and Final in typing._type_check. -- components: +Library (Lib) nosy: +Jelle Zijlstra, gvanrossum, kj

[issue46479] Implement typing.reveal_locals

Change by Jelle Zijlstra : -- keywords: +patch pull_requests: +29022 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30839 ___ Python tracker <https://bugs.python.org/issu

[issue46475] typing.Never and typing.assert_never

Change by Jelle Zijlstra : -- keywords: +patch pull_requests: +29023 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30842 ___ Python tracker <https://bugs.python.org/issu

[issue46480] Implement typing.assert_type

Change by Jelle Zijlstra : -- keywords: +patch pull_requests: +29024 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30843 ___ Python tracker <https://bugs.python.org/issu

[issue46494] Mention typing_extensions in the typing documentation

New submission from Jelle Zijlstra : I've often seen people say things like "I can't use TypeGuard yet, I'm stuck on 3.9". That's not true, because the typing_extensions package backports all typing features to all supported Python versions. To help make p

[issue33983] unify types for lib2to3.pytree.Base.children

Jelle Zijlstra added the comment: lib2to3 is deprecated as of Python 3.11, and there's an available workaround. I don't think it still makes sense to change anything here. -- nosy: +Jelle Zijlstra resolution: -> wont fix stage: patch review -> resolved status

[issue22859] unittest.TestProgram.usageExit no longer invoked

Jelle Zijlstra added the comment: I suggest we mark the method as deprecated and remove it in 3.13. Making the argparse objects public can be done in a separate enhancement request if there is demand for it. -- nosy: +Jelle Zijlstra ___ Python

[issue46186] replace `io.IncrementalNewlineDecoder` with non incremental newline decoders

Jelle Zijlstra added the comment: If the old code is incorrect, can you give an example where it fails? Is it possible to write a unit test demonstrating that the current behavior is wrong? -- nosy: +Jelle Zijlstra ___ Python tracker <ht

[issue46483] `pathlib.PurePath.__class_getitem__` does not return `GenericAlias`

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue46483> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44796] Add __parameters__ and __getitem__ in TypeVar and ParamSpec

Jelle Zijlstra added the comment: The linked PR makes `T = TypeVar("T"); T[int]` work. That's not currently meaningful syntax to the type checker, but we may want it in the future for higher-kinded types. I would rather not make this change without a clear static typing u

[issue46511] dataclasses: Allow typing.Annotated to wrap dataclasses-specific annotations

Jelle Zijlstra added the comment: Related: issue44799 about InitVar. -- ___ Python tracker <https://bugs.python.org/issue46511> ___ ___ Python-bugs-list mailin

[issue46520] `ast.unparse` produces syntactically illegal code for identifiers that look like reserved words

Change by Jelle Zijlstra : -- nosy: +BTaskaya, Jelle Zijlstra, benjamin.peterson, pablogsal ___ Python tracker <https://bugs.python.org/issue46520> ___ ___ Pytho

[issue41370] PEP 585 and ForwardRef

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue41370> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46527] enumerate no longer accepts iterable keyword argument

Jelle Zijlstra added the comment: I can confirm that the behavior changed between 3.10 and current main: enumerate(iterable=[]) works on 3.10 but not on main. It's likely a consequence of bpo-43706. I'll submit a patch to restore the previous behavior. -- nosy: +Jell

[issue43706] enumerate() instantiation time reducing by using PEP 590 vectorcall

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra nosy_count: 4.0 -> 5.0 pull_requests: +29083 pull_request: https://github.com/python/cpython/pull/30904 ___ Python tracker <https://bugs.python.org/issu

[issue46527] enumerate no longer accepts iterable keyword argument

Change by Jelle Zijlstra : -- keywords: +patch pull_requests: +29082 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30904 ___ Python tracker <https://bugs.python.org/issu

[issue46543] Add sys._getfunc

New submission from Jelle Zijlstra : sys._getframe() has to create frame objects, which is relatively expensive. Usually the calling function object should be enough. See https://github.com/faster-cpython/ideas/discussions/238 -- assignee: Jelle Zijlstra components: Interpreter Core

[issue46543] Add sys._getfunc

Change by Jelle Zijlstra : -- keywords: +patch pull_requests: +29129 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30950 ___ Python tracker <https://bugs.python.org/issu

[issue44791] Substitution of ParamSpec in Concatenate

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue44791> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46552] typing: get_type_hints can't handle stringified annotations with leading spaces

Jelle Zijlstra added the comment: I vote we don't change this. PEP 484 says: > The string literal should contain a valid Python expression (i.e., > compile(lit, '', 'eval') should be a valid code object) and it should > evaluate without errors once the m

[issue46552] typing: get_type_hints can't handle stringified annotations with leading spaces

Change by Jelle Zijlstra : -- nosy: +AlexWaygood, gvanrossum, kj, sobolevn ___ Python tracker <https://bugs.python.org/issue46552> ___ ___ Python-bugs-list mailin

[issue46560] ParamSpec: Typo in doc string

Jelle Zijlstra added the comment: Thanks for noticing! Would you like to submit a PR to fix it? -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue46

[issue46562] Add typeof or enum behavior in the typing module

Jelle Zijlstra added the comment: Thanks for your report! I think you're looking for the Literal type. Also, new typing behaviors are better discussed first on https://github.com/python/typing or the typing-sig mailing list. -- nosy: +Jelle Zijlstra resolution: -> lat

[issue46571] Strange `@typing.no_type_check` behavior for class variables

Jelle Zijlstra added the comment: Let's not jump into deprecating it. I think (2) makes the most sense. If we can get that working reliably (using __qualname__ I assume), it would be my preference; otherwise we should do (1). This problem can also affect function objects, right? `cl

[issue46571] Strange `@typing.no_type_check` behavior for class variables

Jelle Zijlstra added the comment: 1. Less change in behavior 2. From the purpose of the decorator, it makes sense for it to apply to nested classes as well as methods, even if the docs don't say so explicitly. -- ___ Python tracker &

[issue46571] Strange `@typing.no_type_check` behavior for class variables

Jelle Zijlstra added the comment: I think we could do it by looking at __qualname__. -- ___ Python tracker <https://bugs.python.org/issue46571> ___ ___ Pytho

[issue43224] Add support for PEP 646

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue43224> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45325] Allow "p" in Py_BuildValue

Jelle Zijlstra added the comment: I stumbled upon the PR and tend to agree with Serhiy that this could be a source of nasty bugs. Passing the wrong type to a va_arg() argument is undefined behavior (e.g. https://wiki.sei.cmu.edu/confluence/display/c/EXP47-C.+Do+not+call+va_arg+with+an

[issue44796] Add __parameters__ and __getitem__ in TypeVar and ParamSpec

Jelle Zijlstra added the comment: I'd also be wary about making changes that introduce additional runtime checks. As we've seen with the PEP 612 and 646 implementations, those can impede future iteration on typing. -- ___ Python track

[issue46479] Implement typing.reveal_locals

Jelle Zijlstra added the comment: Withdrawn as there's insufficient demand for this function. -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.pyth

[issue46644] typing: remove callable() check from typing._type_check

Jelle Zijlstra added the comment: I agree with removing this check. I suspect it's a holdover from very early typing when static types were supposed to be runtime types. Now the check is a bug magnet and doesn't serve a useful purpose. I think we can just remove the tests that

[issue46669] Add types.Self

Jelle Zijlstra added the comment: PEP 673 (which was accepted) adds typing.Self already. bpo-46534 tracks implementing it. -- ___ Python tracker <https://bugs.python.org/issue46

[issue46677] TypedDict docs are incomplete

New submission from Jelle Zijlstra : https://docs.python.org/3.10/library/typing.html#typing.TypedDict It says: > To allow using this feature with older versions of Python that do not support > PEP 526, TypedDict supports two additional equivalent syntactic forms But there is another

[issue46669] Add types.Self

Jelle Zijlstra added the comment: The conventional way is to write def __exit__( self, __typ: type[BaseException] | None, __exc: BaseException | None, __tb: types.TracebackType | None, ) -> None: ... But there are two invariants about how __exit__ works in practice that t

[issue46475] typing.Never and typing.assert_never

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

[issue46685] Add additional tests for new features in `typing.py`

Jelle Zijlstra added the comment: Thanks for catching these details! Please send a PR. -- ___ Python tracker <https://bugs.python.org/issue46685> ___ ___ Pytho

[issue46494] Mention typing_extensions in the typing documentation

Jelle Zijlstra added the comment: Welcome to this project, Meer! That looks pretty good, feel free to submit a PR. We can then perhaps get feedback from more people to improve the wording. -- ___ Python tracker <https://bugs.python.

[issue46586] In documentation contents enum.property erroneously links to built-in property

Jelle Zijlstra added the comment: > How do I find other instances of this problem? Is there a systematic way to > look for such references? You could write a script that goes something like this, iterating over all the docs RST files: - Find all definitions in the file (e.g. `.. dec

[issue46677] TypedDict docs are incomplete

Jelle Zijlstra added the comment: Please do submit a PR! Agree that more examples of inheritance and attributes would be useful. Note that we're about to deprecate the keyword argument syntax (issue46066). -- ___ Python tracker &

[issue46725] Unpacking without parentheses is allowed since 3.9

Jelle Zijlstra added the comment: I'd lean towards keeping this syntax: - It's already been out for two releases, so there's user code out there relying on it. (In fact we found out about this because somebody complained that Black's parser couldn't handle this

[issue46724] Odd Bytecode Generation in 3.10

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue46724> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46727] Should shutil functions support bytes paths?

New submission from Jelle Zijlstra : The shutil documentation doesn't say anything about bytes paths, and the CPython unit tests don't test them. But some functions do work with bytes paths in practice, and on typeshed we've received some requests to add support for them in

[issue46732] object.__bool__ docstring is wrong

New submission from Jelle Zijlstra : >>> None.__bool__.__doc__ 'self != 0' This isn't true, since None does not equal 0. I suggest rewording it to "True if self else False". -- assignee: Jelle Zijlstra components: Interpreter Core messages: 41

[issue46732] object.__bool__ docstring is wrong

Change by Jelle Zijlstra : -- keywords: +patch pull_requests: +29460 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31301 ___ Python tracker <https://bugs.python.org/issu

[issue46743] Enable usage of object.__orig_class__ in __init__

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue46743> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46740] Improve Telnetlib's throughput

Jelle Zijlstra added the comment: Note that telnetlib is being proposed for deprecation in PEP 594. You may be better off using a third-party telnet implementation; the PEP lists https://pypi.org/project/telnetlib3/ and https://pypi.org/project/Exscript/. -- nosy: +Jelle Zijlstra

[issue46760] test_dis should test the dis module, not everything else

Change by Jelle Zijlstra : -- nosy: +Jelle Zijlstra ___ Python tracker <https://bugs.python.org/issue46760> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46738] Allow http.server to emit HTML 5

Jelle Zijlstra added the comment: Looks like this is a duplicate of issue46736. Seems like a good idea though! -- nosy: +Jelle Zijlstra resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracke

[issue46066] Deprecate keyword args syntax for TypedDict definition

Jelle Zijlstra added the comment: New changeset de6043e596492201cc1a1eb28038970bb69f3107 by 97littleleaf11 in branch 'main': bpo-46066: Deprecate kwargs syntax for TypedDict definitions (GH-31126) https://github.com/python/cpython/commit/de6043e596492201cc1a1eb2803897

[issue46066] Deprecate keyword args syntax for TypedDict definition

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

[issue46333] ForwardRef.__eq__ does not respect module parameter

Jelle Zijlstra added the comment: New changeset 6e7b813195f9bd6a2a15c1f00ef2c0180f6c751a by aha79 in branch 'main': bpo-46333: Honor `module` parameter in ForwardRef (GH-30536) https://github.com/python/cpython/commit/6e7b813195f9bd6a2a15c1f00ef2c0

[issue46333] ForwardRef.__eq__ does not respect module parameter

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

[issue46745] Typo in new PositionsIterator

Jelle Zijlstra added the comment: New changeset 482a4b6c3f8ef60056e85647a1d84af2e6dfd3ef by Robert-André Mauchin in branch 'main': bpo-46745: Fix typo in PositionsIterator (#31322) https://github.com/python/cpython/commit/482a4b6c3f8ef60056e85647a1d84af2e6dfd3ef -- no

[issue46571] Strange `@typing.no_type_check` behavior for class variables

Jelle Zijlstra added the comment: New changeset 395029b0bd343648b4da8044c7509672ea768775 by Nikita Sobolev in branch 'main': bpo-46571: improve `typing.no_type_check` to skip foreign objects (GH-31042) https://github.com/python/cpython/commit/395029b0bd343648b4da8044c75096

[issue46603] `typing._strip_annotations` is not fully covered

Jelle Zijlstra added the comment: New changeset 25c0b9d243b64ccd2eeab483089eaf7e4b4d5834 by Nikita Sobolev in branch 'main': bpo-46603: improve coverage of `typing._strip_annotations` (GH-31063) https://github.com/python/cpython/commit/25c0b9d243b64ccd2eeab483089eaf

[issue46603] `typing._strip_annotations` is not fully covered

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

[issue46571] Strange `@typing.no_type_check` behavior for class variables

Jelle Zijlstra added the comment: Thanks for the fix Nikita! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue46685] Add additional tests for new features in `typing.py`

Jelle Zijlstra added the comment: New changeset 32e3e0bea613711a8f19003445eebcb05fb75acc by Nikita Sobolev in branch 'main': bpo-46685: improve test coverage of `Self` and `Never` in `typing` (GH-31222) https://github.com/python/cpython/commit/32e3e0bea613711a8f19003445eebc

[issue46685] Add additional tests for new features in `typing.py`

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

[issue44791] Substitution of ParamSpec in Concatenate

Jelle Zijlstra added the comment: I'm looking at https://github.com/python/cpython/pull/30969 and I'm not sure what the motivation for the change is. PEP 612 is quite precise here (https://www.python.org/dev/peps/pep-0612/#id1) and allows only a ParamSpec as the last argument to C

[issue46066] Deprecate keyword args syntax for TypedDict definition

Jelle Zijlstra added the comment: Thanks, I'll send a PR. -- ___ Python tracker <https://bugs.python.org/issue46066> ___ ___ Python-bugs-list mailing list

[issue46066] Deprecate keyword args syntax for TypedDict definition

Change by Jelle Zijlstra : -- pull_requests: +29563 pull_request: https://github.com/python/cpython/pull/31428 ___ Python tracker <https://bugs.python.org/issue46

[issue46066] Deprecate keyword args syntax for TypedDict definition

Jelle Zijlstra added the comment: New changeset 0a8a8e7454c6565cf1554d5f23314e4c70960bcd by Jelle Zijlstra in branch 'main': bpo-46066: Check DeprecationWarning in test_typing (GH-31428) https://github.com/python/cpython/commit/0a8a8e7454c6565cf1554d5f23314e

[issue43853] [sqlite3] Improve sqlite3_value_text() error handling

Jelle Zijlstra added the comment: New changeset ba457fe6f8e50ad3ef3ceffb75dee96629a42ad7 by Erlend Egeberg Aasland in branch '3.10': [3.10] bpo-43853: Expand test suite for SQLite UDF's (GH-27642) (GH-31030) https://github.com/python/cpython/commit/ba457fe6f8e50ad3ef3ceffb7

[issue46732] Builtin __bool__ docstrings are wrong

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

[issue46821] Introspection support for typing.overload

New submission from Jelle Zijlstra : Currently, the implementation of @overload (https://github.com/python/cpython/blob/59585d6b2ea50d7bc3a9b336da5bde61367f527c/Lib/typing.py#L2211) simply returns a dummy function and throws away the decorated function. This makes it virtually impossible for

[issue46821] Introspection support for typing.overload

Jelle Zijlstra added the comment: Thanks! Closing this as a duplicate. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Improve help() by making typing.overload() information accessible at runtime __

[issue45100] Improve help() by making typing.overload() information accessible at runtime

Jelle Zijlstra added the comment: I made a similar suggestion in issue46821 (thanks Alex for pointing me to this older issue): Currently, the implementation of @overload (https://github.com/python/cpython/blob/59585d6b2ea50d7bc3a9b336da5bde61367f527c/Lib/typing.py#L2211) simply returns a

[issue45100] Improve help() by making typing.overload() information accessible at runtime

Jelle Zijlstra added the comment: I'm OK with not fully supporting overloads created in nested functions; that's a pretty marginal use case. But it's true that my proposed implementation would create a memory leak if someone does do that. I don't immediately see a w

  1   2   3   4   5   6   >