Mailman 3 - Python-Dev

Retiring this mailing list ?
by Marc-Andre Lemburg Nov. 25, 2023

Nov. 25, 2023

Hello everyone, for quite a while now, core discussions have moved to Discourse and people are obviously enjoying things there: https://discuss.python.org/c/core-dev/23 The Discourse mailing list mode works reasonably well, so is a suitable replacement for this mailing list. Posts to this list are now mostly spam, mailer error reports and the occasional release postings: https://mail.python.org/archives/list/python-dev@python.org/latest (you can't see much of the spam, since we filter … [View More]

7 9

Delivery reports about your e-mail
by ethan＠stoneleaf.us Nov. 15, 2023

Nov. 15, 2023

Your message was not delivered due to the following reason: Your message was not delivered because the destination server was unreachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within 5 … [View More]

1 0

HELLO
by mhammond＠skippinet.com.au Nov. 14, 2023

Nov. 14, 2023

The original message was received at Thu, 5 Oct 2023 09:08:00 +0300 from [87.212.114.230] ----- The following addresses had permanent fatal errors ----- <python-dev(a)python.org> ----- Transcript of session follows ----- ... while talking to python.org.: >>> DATA <<< 400-aturner; %MAIL-E-OPENOUT, error opening !AS as output <<< 400-aturner; -RMS-E-CRE, ACP file create failed <<< 400-aturner; -SYSTEM-F-EXDISKQUOTA, disk quota exceeded <<< 400

1 0

lkmxowjkmf
by theller＠python.net Nov. 6, 2023

Nov. 6, 2023

The message was undeliverable due to the following reason: Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 8 days: … [View More]

1 0

Proposal: Allow non-default after default arguments
by Sebastian Rittau Oct. 16, 2023

Oct. 16, 2023

Currently, Python doesn't allow non-default arguments after default arguments: >>> def foo(x=None, y): pass File "<stdin>", line 1 def foo(x=None, y): pass ^ SyntaxError: non-default argument follows default argument I believe that at the time this was introduced, no use cases for this were known and this is is supposed to … [View More]prevent a source of bugs. I have two use cases for this, one fringe, but valid, the other more important: The fringe use case: Suppose you have a function that takes a 2D coordinate value as separate "x" and "y" arguments. The "x" argument is optional, the "y" argument isn't. Currently there are two ways to do this, none of them particularly great: def foo(y, x): # reverse x and y arguments, confusing ... def foo(x, y=None): # Treat the x argument as y if only one argument is provided if y is None: x, y = y, x ... To me, the "natural" solution looks like this: def foo(x=None, y): ... # Called like this: foo(1, 2) foo(y=2) This could also be useful when evolving APIs. For example there is a function "bar" that takes two required arguments. In a later version, the first argument gains a useful default, the second doesn't. There is no sensible way to evolve the API at the moment. The more important use case involves @overloads. A condensed example of a function where the return type depends on an "encoding" parameter, followed by further parameters that could be called like this: foo(123, "utf-8") # would return bytes foo(encoding="utf-8") foo(123, None) # would return str foo(encoding=None) foo(x=123) # would return str foo() This could ideally be written as: @overload def foo(x: int = ..., encoding: None = ...) -> str: ... @overload def foo(x: int = ..., encoding: str) -> bytes: ... # plus the actual implementation But due to the syntax constraint, this needs to be hacked around with a third overload: @overload def foo(x: int = ... encoding: None = ...) -> str: ... @overload def foo(x: int, encoding: str) -> bytes: ... # for foo(123, "utf-8") @overload def foo(*, encoding: str) -> bytes: ... # for foo(encoding="utf-8") Not only is this hard to read, real examples in typeshed are usually more complex, with many arguments before or after the affected argument or even multiple affected arguments. This often becomes too complex to write or maintain. Here is one example from the wild: https://github.com/python/typeshed/blob/b95b729b9e07ab21d252701af0f5b740467… Allowing non-default arguments after default arguments would solve both use cases above and eliminates a special case. I'm also not sure what exactly the current SyntaxError really protects us from. Adding a non-default after a default argument can't really lead bugs. - Sebastian [View Less]

11 14

detecting statements which result is not stored
by Guenther Sohler Oct. 5, 2023

Oct. 5, 2023

Hi Python Developers, after some investigation i consider dev the correct mailing list. I got python embedded into OpenSCAD and i'd like to make more use out of it. statements like these do exactly what they should: width= 3*5 solid = make_nice_solid(width) other_solid = solid.size(1) print(" Everything fine") But i'd like to be able to write lines like these: These are expressions which create a value, which is apparently NOT stored in a variable solid *3 other_solid - solid instead of … [View More]

2 1

python-dev@python.org
by mhammond＠skippinet.com.au Sept. 19, 2023

Sept. 19, 2023

The message was undeliverable due to the following reason(s): Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within … [View More]

1 0

Message could not be delivered
by fdrake＠acm.org Sept. 10, 2023

Sept. 10, 2023

The original message was received at Wed, 20 Oct 2021 15:12:36 +0300 from acm.org [25.147.223.204] ----- The following addresses had permanent fatal errors ----- python-dev(a)python.org ----- Transcript of the session follows ----- ... while talking to 146.160.159.171: >>> RCPT To:<python-dev(a)python.org> <<< 550 5.1.1 <python-dev(a)python.org>... Not known here

1 0

[RELEASE] Python 3.11.5, 3.10.13, 3.9.18, and 3.8.18 is now available
by Łukasz Langa Aug. 24, 2023

Aug. 24, 2023

There’s security content in the releases, let’s dive right in. gh-108310 <https://github.com/python/cpython/issues/108310>: Fixed an issue where instances of ssl.SSLSocket <https://docs.python.org/release/3.10.13/library/ssl.html#ssl.SSLSocket> were vulnerable to a bypass of the TLS handshake and included protections (like certificate verification) and treating sent unencrypted data as if it were post-handshake TLS encrypted data. Security issue reported as CVE-2023-40217 1 &… [View More]

1 0

[RELEASE] Python 3.12.0 release candidate 1 released
by Thomas Wouters Aug. 6, 2023

Aug. 6, 2023

I'm pleased to announce the release of Python 3.12.0rc1: https://www.python.org/downloads/release/python-3120rc1/ This is the first release candidate of Python 3.12.0 This release, *3.12.0rc1*, is the penultimate release preview. Entering the release candidate phase, only reviewed code changes which are clear bug fixes are allowed between this release candidate and the final release. The second candidate (and the last planned release preview) is scheduled for Monday, 2023-09-04, while the … [View More]

1 0