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

2017-07-26 Thread Mike Miller
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

2017-07-26 Thread Terry Reedy
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

2017-07-26 Thread MRAB
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

2017-07-26 Thread Koos Zevenhoven
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

2017-07-26 Thread MRAB
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

2017-07-26 Thread Koos Zevenhoven
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] Appending a link back to bugs.python.org in GitHub PRs

2017-07-26 Thread Nick Coghlan
On 26 July 2017 at 02:21, Brett Cannon wrote: > > > On Tue, 25 Jul 2017 at 07:30 Ben Hoyt wrote: >> >> With the linking back and forth, I'm curious why there wasn't a switch to >> use GitHub's issue tracker when we switched to GitHub. I'm sure there was >>