Re: [Python-Dev] chained assignment weirdity

On 06.11.12 21:00, Ned Batchelder wrote: If someone really needs to control whether the keys or values are evaluated first, they shouldn't use a dict literal. Not only a dict literal. >>> {print('foo'): print('bar') for x in [1]} bar foo {None: None} _

[Python-Dev] 回复： Python-Dev Digest, Vol 112, Issue 8

I hava some question about Object which "inital" need ,but return "object" in mongo shell. So   BSONElement initial = p["initial"]; if ( initial.type() != Object ) { errmsg = "initial has to be an object"; return false; }  "initial.type() !=

Re: [Python-Dev] chained assignment weirdity

On Tue, Nov 6, 2012 at 9:58 AM, Ned Batchelder wrote: > On 11/6/2012 11:26 AM, R. David Murray wrote: >> >> On Tue, 06 Nov 2012 18:14:38 +0200, Serhiy Storchaka >> wrote: >>> >>> Another counterintuitive (and possible wrong) example: >>> >>> >>> {print('foo'): print('bar')} >>> bar >>>

Re: [Python-Dev] chained assignment weirdity

MRAB wrote: That would make augmented assignment more difficult. For example, how would you write the equivalent of "x -= y"? SUBTRACT x FROM y. CLOSE POST WITH SMILEY. -- Greg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org

Re: [Python-Dev] chained assignment weirdity

On 11/6/2012 1:19 PM, Devin Jeanpierre wrote: On Nov 6, 2012 1:05 PM, "Ned Batchelder" > wrote: > > On 11/6/2012 11:26 AM, R. David Murray wrote: >> >> On Tue, 06 Nov 2012 18:14:38 +0200, Serhiy Storchaka mailto:storch...@gmail.com>> wrote: >>> >>> Another cou

Re: [Python-Dev] chained assignment weirdity

On Nov 6, 2012 1:05 PM, "Ned Batchelder" wrote: > > On 11/6/2012 11:26 AM, R. David Murray wrote: >> >> On Tue, 06 Nov 2012 18:14:38 +0200, Serhiy Storchaka wrote: >>> >>> Another counterintuitive (and possible wrong) example: >>> >>> >>> {print('foo'): print('bar')} >>> bar >>> foo >

Re: [Python-Dev] chained assignment weirdity

On 11/6/2012 11:26 AM, R. David Murray wrote: On Tue, 06 Nov 2012 18:14:38 +0200, Serhiy Storchaka wrote: Another counterintuitive (and possible wrong) example: >>> {print('foo'): print('bar')} bar foo {None: None} http://bugs.python.org/issue11205 This seems to me better l

Re: [Python-Dev] chained assignment weirdity

On Tue, 06 Nov 2012 18:14:38 +0200, Serhiy Storchaka wrote: > Another counterintuitive (and possible wrong) example: > >>>> {print('foo'): print('bar')} >bar >foo >{None: None} http://bugs.python.org/issue11205 --David ___ Python-Dev

Re: [Python-Dev] chained assignment weirdity

On 06.11.12 14:01, Nick Coghlan wrote: Python, on the other hand, is able to preserve primarily left to right evaluation in this case with only the far right hand expression needing to be evaluated out of order. I'm surprised, but it is really so. >>> {}[print('foo')] = print('bar') bar

Re: [Python-Dev] chained assignment weirdity

+1 to what Nick said. And I thought about this carefully when designing the language. It's not a bug. The note about assignment RHS being evaluated before LHS is normative -- you just have to interpret RHS as "after the *last* '=' symbol". Assignment itself is *not* an expression. On Tue, Nov 6, 2

Re: [Python-Dev] chained assignment weirdity

On 2012-11-06 15:02, Rob Cliffe wrote: On 06/11/2012 12:01, Nick Coghlan wrote: As noted, it's really only counterintuitive if your intuition is primed to expect C style right to left chained assignments. Python, on the other hand, is able to preserve primarily left to right evaluation in thi

Re: [Python-Dev] cpython (3.3): Add examples for opener argument of open (#13424).

Hi, Le 05/11/2012 13:04, Georg Brandl a écrit : > Please heed your Sphinx warnings: the :ref:`dir_fd` needs a link caption, > since > it can't autogenerate one (the dir_fd anchor does not point to a heading). Okay. I hadn’t noticed it because I was using my system sphinx-build instead of a loca

Re: [Python-Dev] chained assignment weirdity

On 06/11/2012 12:01, Nick Coghlan wrote: As noted, it's really only counterintuitive if your intuition is primed to expect C style right to left chained assignments. Python, on the other hand, is able to preserve primarily left to right evaluation in this case with only the far right hand e

Re: [Python-Dev] ctypes is not an acceptable implementation strategy for modules in the standard library?

On Mon, Nov 05, 2012 at 03:36:00AM -0800, Victor Stinner wrote: > I'm not sure that ctypes is always available (available on all platforms). Indeed. Every non-x86 Snakebite platform has pretty serious issues with ctypes. I spent a morning looking into one platform, Solaris 10 on SPAR

Re: [Python-Dev] chained assignment weirdity

As noted, it's really only counterintuitive if your intuition is primed to expect C style right to left chained assignments. Python, on the other hand, is able to preserve primarily left to right evaluation in this case with only the far right hand expression needing to be evaluated out of order.

Re: [Python-Dev] chained assignment weirdity

On 11/6/2012 1:18 AM, Chris Withers wrote: Hi All, I bumped into this using Michael Foord's Mock library. It feels like a bug to me, but thought I'd ask here before logging one in the tracker in case people know that we won't be able to fix it: On 05/11/2012 13:43, Michael Foord wrote: class

Re: [Python-Dev] chained assignment weirdity

On Tue, Nov 6, 2012 at 1:18 AM, Chris Withers wrote: > Hi All, > > I bumped into this using Michael Foord's Mock library. > It feels like a bug to me, but thought I'd ask here before logging one in > the tracker in case people know that we won't be able to fix it: > > On 05/11/2012 13:43, Michael

[Python-Dev] chained assignment weirdity

Hi All, I bumped into this using Michael Foord's Mock library. It feels like a bug to me, but thought I'd ask here before logging one in the tracker in case people know that we won't be able to fix it: On 05/11/2012 13:43, Michael Foord wrote: class Foo(object): ... def __setattr__(s, k,