[Python-ideas] Shouldn't this: ' myVar: "value" ' be a syntax error ?

>>> a: 3 >>> type(a: 3) File "", line 1 type(a: 3) ^ SyntaxError: invalid syntax >>> a: 3 >>> type(a) Traceback (most recent call last): File "", line 1, in NameError: name 'a' is not defined >>> a Traceback (most recent call last): File "", line 1, in NameError: name 'a' is n

[Python-ideas] Re: Shouldn't this: ' myVar: "value" ' be a syntax error ?

On Wed, Jul 10, 2019 at 6:11 AM Shay Cohen wrote: > > > >>> a: 3 > >>> type(a: 3) > File "", line 1 > type(a: 3) > ^ > SyntaxError: invalid syntax > >>> a: 3 > >>> type(a) > Traceback (most recent call last): > File "", line 1, in > NameError: name 'a' is not defined > >>> a > T

[Python-ideas] Re: Shouldn't this: ' myVar: "value" ' be a syntax error ?

On Jul 9, 2019, at 13:09, Shay Cohen wrote: > > >>> a: 3 The reason this isn’t a syntax error is that Python allows any valid expression as an annotation. And “3” is just as valid an expression as “int”. More generally, annotations don’t actually do anything at runtime, except get stored in a

[Python-ideas] Re: Suggestion: Windows launcher default to not using pre-releases by default

On Mon, Jul 8, 2019 at 10:39 PM Steve Barnes wrote: > Currently the py[w] command will launch the latest python by default > however I feel that this discourages the testing of pre-releases & release > candidates as once they are installed they will become the default. What I > would like is for

[Python-ideas] Re: Suggestion: Windows launcher default to not using pre-releases by default

On Wed, Jul 10, 2019 at 7:48 AM Brett Cannon wrote: > > > > On Mon, Jul 8, 2019 at 10:39 PM Steve Barnes wrote: >> >> Currently the py[w] command will launch the latest python by default however >> I feel that this discourages the testing of pre-releases & release >> candidates as once they are

[Python-ideas] Re: Python including packages

On 08Jul2019 11:40, Siddharth Prajosh wrote: Hey all, after this talk on how useful standard libraries are this has been in talks in multiple channels. I just wanted to present my idea on the same. Why not keep the es

[Python-ideas] Re: Suggestion: Windows launcher default to not using pre-releases by default

On Jul 9, 2019, at 16:30, Chris Angelico wrote: > > What about flipping that around - when you install, have an option to > say "make this the default" (active by default), and if you untick it, > it flags the installation as "not the default"? Available only if > there's an existing default. As

[Python-ideas] Re: Suggestion: Windows launcher default to not using pre-releases by default

On 2019-07-09 22:46, Brett Cannon wrote: On Mon, Jul 8, 2019 at 10:39 PM Steve Barnes > wrote: Currently the py[w] command will launch the latest python by default however I feel that this discourages the testing of pre-releases & release candidates

[Python-ideas] Re: Suggestion: Windows launcher default to not using pre-releases by default

On Tue, Jul 9, 2019 at 8:04 PM MRAB wrote: > When you start Python, it reports its version. How discoverable is that > version for the launcher, and for tools in general? `python -V` will print a simple version string and exit, like this example using an executable compiled from the 3.8 git branc

[Python-ideas] Re: Suggestion: Windows launcher default to not using pre-releases by default

I have made this suggestion in the past. The response then was that there is no metadata in the windows install that includes if the release is development or stable (that information is not stored in the registry). I was advised to adjust my configuration of the py.exe launcher to set a differen