Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

On Fri, Mar 2, 2018 at 5:39 PM, Ethan Furman wrote: > Seems like it would far easier and (IMHO) more useful to scale the proposal > back from a statement scope to simple expression assignment, and the > variable is whatever scope it would have been if assigned to outside the >

Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

On 03/01/2018 09:08 PM, Nick Coghlan wrote: On 1 March 2018 at 19:30, Paul Moore

Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

On 1 March 2018 at 19:30, Paul Moore wrote: > On 1 March 2018 at 06:40, Chris Angelico wrote: > > On Thu, Mar 1, 2018 at 3:31 PM, Nick Coghlan wrote: > >> Since ".NAME" is illegal for both variable and attribute names, this > makes >

Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

On Thu, Mar 1, 2018 at 2:47 PM, Greg Ewing wrote: > On 28 February 2018 at 21:48, Robert Vanden Eynde >> wrote: >> >> Isn't it easier to talk on a forum? >>> >> > For me, the fact that all the mailing lists I subscribe to > feed into one input

Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

On 28 February 2018 at 21:48, Robert Vanden Eynde wrote: Isn't it easier to talk on a forum? For me, the fact that all the mailing lists I subscribe to feed into one input queue is a feature, not a bug. It means I can easily keep abreast of developments in many areas at

Re: [Python-ideas] Medium for discussion potential changes to python (was: PEP 572: Statement-Local Name Bindings)

The best we can do here is move to MM3, as is being discussed in another thread. On Wed, Feb 28, 2018 at 2:39 PM, Oleg Broytman wrote: > On Wed, Feb 28, 2018 at 10:23:08PM +, Matt Arcidy > wrote: > > if Linux kernel can handle it, there is no argument

Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

On 01/03/2018 06:47, Chris Angelico wrote: This is the kind of ambiguity of intent that goes away if statement locals are made syntactically distinct in addition to being semantically distinct: .a = (2 as .a) # Syntax error (persistent bindings can't target statement locals) a = (2 as

Re: [Python-ideas] Upgrading python-ideas to MM3?

On 1 March 2018 at 20:11, Antoine Pitrou wrote: > On Thu, 1 Mar 2018 11:08:10 +0100 > Antoine Pitrou wrote: > > On Thu, 1 Mar 2018 15:28:57 +1000 > > Nick Coghlan wrote: > > > Hi folks, > > > > > > A number of smaller python.org

Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

Nick Coghlan writes: > for .i in range(10): > print(.i) # This is fine > print(.i) # This is an error (unless an outer statement also sets .i) That's one heck of a lot of grit on Tim's screen! ___ Python-ideas mailing list

Re: [Python-ideas] Upgrading python-ideas to MM3?

On Thu, 1 Mar 2018 11:08:10 +0100 Antoine Pitrou wrote: > On Thu, 1 Mar 2018 15:28:57 +1000 > Nick Coghlan wrote: > > Hi folks, > > > > A number of smaller python.org mailing lists have been successfully > > migrated to the PSF's Mailman 3

Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

Nick Coghlan writes: > for .i in range(10): > print(.i) # This is fine > print(.i) # This is an error (unless an outer statement also sets .i) That's one heck of a lot of grit on Tim's screen! ___ Python-ideas mailing list

Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

Chris Angelico writes: > Memoization can only be done for pure functions. True, but when for impure f you naively construct a list [f(x), f(x)], substituting [(f(x) as wrong), wrong] is just [wrong, wrong] ;-), because the side effect doesn't get reevaluated. Steve

Re: [Python-ideas] PEP 572: Statement-Local Name Bindings

On 28 February 2018 at 21:48, Robert Vanden Eynde wrote: > We are currently like a dozen of people talking about multiple sections of a > single subject. > > Isn't it easier to talk on a forum? Not for me, certainly. I could probably learn how to effectively work with a

Re: [Python-ideas] Upgrading python-ideas to MM3?

01.03.18 09:46, Nick Coghlan пише: Yeah, the existing archives will remain untouched (but will also stop getting updated). New and migrated messages get archived based on a content-addressable hash (e.g.