[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 Concatenate.

[issue46066] Deprecate keyword args syntax for TypedDict definition

Jelle Zijlstra added the comment: Thanks, I'll send a PR. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[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 ___ __

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

Change by Meer Suri : -- pull_requests: +29564 pull_request: https://github.com/python/cpython/pull/31429 ___ Python tracker ___ ___

[issue46795] Why does 3rd/Python39/Lib/site-packages/psycopg2/_psycopg.cp39-win_amd64.pyd have the CVE-201-4160 vulnerability when I use Python 3.9.2

Change by zjmxq : -- components: Library (Lib) nosy: zjmxq priority: normal severity: normal status: open title: Why does 3rd/Python39/Lib/site-packages/psycopg2/_psycopg.cp39-win_amd64.pyd have the CVE-201-4160 vulnerability when I use Python 3.9.2 type: security versions: Python 3.9

[issue46795] Why Does 3rd/Python39/Lib/site-packages/psycopg2/_psycopg.cp39-win_amd64.pyd Have the CVE-20211-4160 Vulnerability? I Use Python 3.9.2? Where Is OpenSSL Used?

Change by zjmxq : -- title: Why does 3rd/Python39/Lib/site-packages/psycopg2/_psycopg.cp39-win_amd64.pyd have the CVE-201-4160 vulnerability when I use Python 3.9.2 -> Why Does 3rd/Python39/Lib/site-packages/psycopg2/_psycopg.cp39-win_amd64.pyd Have the CVE-20211-4160 Vulnerability?

[issue46757] dataclasses should define an empty __post_init__

Nikita Sobolev added the comment: I like this idea. `attrs` right now behave the same way (no default `__attrs_post_init__`: ``` >>> import attrs >>> @attrs.define ... class Some: ... x: int ... >>> @attrs.define ... class Other(Some): ...def __attrs_post_init__(self): ... super(

[issue46757] dataclasses should define an empty __post_init__

Change by Nikita Sobolev : -- keywords: +patch pull_requests: +29565 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31430 ___ Python tracker ___ _

[issue24053] Define EXIT_SUCCESS and EXIT_FAILURE constants in sys

Stefan Behnel added the comment: > Any reasons the PR still not merged? There was dissent about whether these constants should be added or not. It doesn't help to merge a PR that is not expected to provide a benefit. -- ___ Python tracker

[issue46757] dataclasses should define an empty __post_init__

Change by Nikita Sobolev : -- type: -> behavior versions: +Python 3.11 ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue46757] dataclasses should define an empty __post_init__

Vedran Čačić added the comment: That "except AttributeError" approach is a powerful bug magnet, since it can very easily mask real attribute errors stemming from misspelled attribute names in the __post_init__ call itself. What you should _really_ do is def __post_init__(self): wi

[issue46796] Simplify handling of removed parameter "loop" in asyncio

New submission from Serhiy Storchaka : Before 3.10 many asyncio classes did have an optional parameter "loop". It was deprecated in 3.8. To simplify the code, such classes inherited a constructor from _LoopBoundMixin which set the _loop attribute and (since 3.8) emitted a warning if the loop

[issue46796] Simplify handling of removed parameter "loop" in asyncio

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +29566 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31431 ___ Python tracker ___

<    1   2