[Python-Dev] Anyone else gotten bizarre personal replies to mailing list posts?

I just got the reply below sent directly to my personal account, and I'm confused about what's going on. If it's just a one off I'll chalk it up to random internet weirdness, but if other folks are getting these too it might be something the list admins should look into? Or... something?

Re: [Python-Dev] Anyone else seeing a lack of caching in local docs builds?

On Mon, 28 Jan 2019 18:02:16 +1000 Nick Coghlan wrote: > On Mon, 28 Jan 2019 at 05:44, Terry Reedy wrote: > > On 1/27/2019 9:01 AM, Nick Coghlan wrote: > > > For now, I'm assuming I've messed something up with my local docs > > > build setup, but figured I'd ask if anyone else was seeing this,

Re: [Python-Dev] Anyone else seeing a lack of caching in local docs builds?

On Mon, 28 Jan 2019 at 05:44, Terry Reedy wrote: > On 1/27/2019 9:01 AM, Nick Coghlan wrote: > > For now, I'm assuming I've messed something up with my local docs > > build setup, but figured I'd ask if anyone else was seeing this, in > > case it was actually broken at the build level (CI

Re: [Python-Dev] Anyone else seeing a lack of caching in local docs builds?

On 1/27/2019 9:01 AM, Nick Coghlan wrote: Hi folks, I'm currently seeing a behaviour where every time I run "make html", all 474 source files get rebuilt. I just rebuilt, ditto, all 474. Caching only works when I rebuild 'soon' (at least within same day) after a complete rebuild. I just

[Python-Dev] Anyone else seeing a lack of caching in local docs builds?

Hi folks, I'm currently seeing a behaviour where every time I run "make html", all 474 source files get rebuilt. For now, I'm assuming I've messed something up with my local docs build setup, but figured I'd ask if anyone else was seeing this, in case it was actually broken at the build level

Re: [Python-Dev] for...else

As previously requested: please take this discussion to python-ideas. If you reply, remove python-dev from the To: and Cc: lists, and add python-ideas instead. This speculative discussion was never appropriate for python-dev. //arry/ On 07/28/2017 03:11 PM, Rob Cliffe wrote: On

Re: [Python-Dev] for...else

On 28/07/2017 20:57, MRAB wrote: On 2017-07-28 10:17, Michel Desmoulin wrote: elif break and elif None: I'd like that very much. It's weird a break the semantic of break and None, but it's in such a dark corner of Python anyway I don't bother. Surely it would not be "elif break", but "elif

Re: [Python-Dev] for...else

On 2017-07-28 10:17, Michel Desmoulin wrote: elif break and elif None: I'd like that very much. It's weird a break the semantic of break and None, but it's in such a dark corner of Python anyway I don't bother. Surely it would not be "elif break", but "elif not break"? Le 27/07/2017 à 21:19,

Re: [Python-Dev] for...else

elif break and elif None: I'd like that very much. It's weird a break the semantic of break and None, but it's in such a dark corner of Python anyway I don't bother. Le 27/07/2017 à 21:19, MRAB a écrit : > On 2017-07-27 03:34, Mike Miller wrote: >> >> >> On 2017-07-26 16:36, MRAB wrote: >>>

Re: [Python-Dev] for...else

funny ; this made me think of this talk; https://youtu.be/OSGv2VnC0go?t=1013 Éric Lafontaine | Membre du Projet VUE, Groupe Contrôle Génie électrique, 54ème promotion UdeS | Étudiant en maitrise TI à l'ETS VAS OPS chez Bell Mobility « Nous voulons proposer une alternative de transport en

Re: [Python-Dev] for...else

On 2017-07-27 03:34, Mike Miller wrote: On 2017-07-26 16:36, MRAB wrote: "nobreak" would introduce a new keyword, but "not break" wouldn't. Whenever I've used the for-else, I've put a # no-break right next to it, to remind myself as much as anyone else. for...: not break: is the best

Re: [Python-Dev] for...else

On 2017-07-26 16:36, MRAB wrote: "nobreak" would introduce a new keyword, but "not break" wouldn't. Whenever I've used the for-else, I've put a # no-break right next to it, to remind myself as much as anyone else. for...: not break: is the best alternative I've yet seen, congrats.

Re: [Python-Dev] for...else

This discussion belongs on python-list (where is it mostly a repeat). -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:

Re: [Python-Dev] for...else

On 2017-07-27 01:07, Koos Zevenhoven wrote: On Jul 27, 2017 02:38, "MRAB" > wrote: On 2017-07-26 23:55, Koos Zevenhoven wrote: ​IMO, for item in sequence: # block nobreak: # or perhaps

Re: [Python-Dev] for...else

On Jul 27, 2017 02:38, "MRAB" wrote: On 2017-07-26 23:55, Koos Zevenhoven wrote: > > ​IMO, > > for item in sequence: > # block > nobreak: # or perhaps `if not break:` > # block > > would be clearer (if the syntax is necessary at all). > You couldn't have

Re: [Python-Dev] for...else

On 2017-07-26 23:55, Koos Zevenhoven wrote: On Mon, Jul 24, 2017 at 7:14 PM, Steven D'Aprano >wrote: Hello Kiuhnm, and welcome. On Mon, Jul 24, 2017 at 05:35:03PM +0200, Kiuhnm via Python-Dev wrote: > Hello, > > I think that

Re: [Python-Dev] for...else

On Mon, Jul 24, 2017 at 7:14 PM, Steven D'Aprano wrote: > Hello Kiuhnm, and welcome. > > On Mon, Jul 24, 2017 at 05:35:03PM +0200, Kiuhnm via Python-Dev wrote: > > Hello, > > > > I think that the expression "for...else" or "while...else" is completely > > counter-intuitive.

Re: [Python-Dev] for...else

On 25/07/2017 06:51, Nick Coghlan wrote: On 25 July 2017 at 02:23, Ben Hoyt wrote: This is more of a python-ideas discussion, and Steven's answer is good. I'll just add one thing. Maybe it's obvious to others, but I've liked for...else since I found a kind of mnemonic to

Re: [Python-Dev] for...else

On 25 July 2017 at 02:23, Ben Hoyt wrote: > This is more of a python-ideas discussion, and Steven's answer is good. > > I'll just add one thing. Maybe it's obvious to others, but I've liked > for...else since I found a kind of mnemonic to help me remember when the > "else" part

Re: [Python-Dev] for...else

The way I remember it is to observe that the following are *almost* exactly the same thing: if C: T else: E while C: T else: E The *only* differences are: 1) where execution jumps if it reaches the end of the T: in the "while", it jumps back to the while itself, resulting in

Re: [Python-Dev] for...else

On Mon, Jul 24, 2017 at 12:23 PM, Ben Hoyt wrote: > .. I found a kind of mnemonic to help me remember when the > "else" part happens: I think of it not as "for ... else" but as "break ... > else" -- saying it this way makes it clear to me that the break goes with > the else.

Re: [Python-Dev] for...else

This is more of a python-ideas discussion, and Steven's answer is good. I'll just add one thing. Maybe it's obvious to others, but I've liked for...else since I found a kind of mnemonic to help me remember when the "else" part happens: I think of it not as "for ... else" but as "break ... else"

Re: [Python-Dev] for...else

Hello Kiuhnm, and welcome. On Mon, Jul 24, 2017 at 05:35:03PM +0200, Kiuhnm via Python-Dev wrote: > Hello, > > I think that the expression "for...else" or "while...else" is completely > counter-intuitive. You may be right -- this has been discussed many, many times before. In my personal

[Python-Dev] for...else

Hello, I think that the expression "for...else" or "while...else" is completely counter-intuitive. Wouldn't it be possible to make it clearer? Maybe something like break in for i in range(n): ... if cond: break else: ... I'm not an English native speaker so