Re: Disable 'style PEP' messages

On 05/05/2023 04.28, Kevin M. Wilson via Python-list wrote: Hi... How do I set Pycharm to find only syntax errors?!! Please review response to previous message re:configuring PyCharm's helpful features towards to coders and quality-coding... -- Regards, =dn --

Re: Disable 'style PEP' messages

On 5/4/23 10:28, Kevin M. Wilson via Python-list wrote: Hi... How do I set Pycharm to find only syntax errors?!! By configuring PyCharm the way you want. See PyCharm's documentation for how to do that. Hint: Settings -> Editor -> Code Style -> Inspections --

Disable 'style PEP' messages

Hi... How do I set Pycharm to find only syntax errors?!! "When you pass through the waters, I will be with you: and when you pass through the rivers, they will not sweep over you. When you walk through the fire, you will not be burned: the flames will not set you ablaze."      Isaiah 43:2 | |

RE: XXX XXX should stop sending me rude email messages.

Michael, Although I appreciate much of what you say, I ask humbly and politely that we change the Subject line for messages like this one. HH is out of range for now, albeit I think he can still read what we say. But keeping the name Michael Torrie in the subject line, should be sort of XXX

Re: Rob Cliffe should stop sending me rude email messages.

On 2/27/23 09:17, Grant Edwards wrote: > On 2023-02-27, Michael Torrie wrote: > >> I've been putting off sending this message for days, but the list noise >> level is now to the point that it has to be said. > > Ah, I've finially realized why some of those threads have seemed so > disjointed to

Re: Rob Cliffe should stop sending me rude email messages.

On 2023-02-27, Michael Torrie wrote: > I've been putting off sending this message for days, but the list noise > level is now to the point that it has to be said. Ah, I've finially realized why some of those threads have seemed so disjointed to me. Years ago, I plonked all posts which are (like

Re: Rob Cliffe should stop sending me rude email messages.

understand why your posts have been causing frustration? This is an existing community that you've chosen to join. Many of the people you've insulted here, including dn have been participating and helpfully contributing to this list for many years. Please stop posting messages about how you think

Re: Rob Cliffe should stop sending me rude email messages.

On Sun, Feb 26, 2023 at 3:49 PM Hen Hanna wrote: > > Rob Cliffe should stop sending me rude email messages. You should stop spamming this lists with with meaningless posts. -- https://mail.python.org/mailman/listinfo/python-list

Re: Rob Cliffe should stop sending me rude email messages.

t through, apparently) were among the few that were relevant. On Sunday, February 26, 2023 at 10:10:09 AM UTC-8, Hen Hanna wrote: > Rob Cliffe should stop sending me rude email messages. > > > At the very least, Rob Cliffe should stop sending

Rob Cliffe should stop sending me rude email messages.

Rob Cliffe should stop sending me rude email messages. At the very least, Rob Cliffe should stop sending me ANY email messages, if he doesn't intend to an email i've sent him. -- https://mail.python.org/mailman/listinfo/python-list

Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

t; > Date: Friday, October 7, 2022 at 1:30 PM > To: MRAB mailto:pyt...@mrabarnett.plus.com>> > Cc: python-list@python.org <mailto:python-list@python.org> > mailto:python-list@python.org>> > Subject: Re: Ref-strings in logging messages (was: Performan

Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

hello" logging.basicConfig() logging.debug(Defer(some_expensive_function)) From: Python-list on behalf of Barry Date: Friday, October 7, 2022 at 1:30 PM To: MRAB Cc: python-list@python.org Subject: Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython) ***

Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

On Fri, 7 Oct 2022 18:28:06 +0100 Barry wrote: > > On 7 Oct 2022, at 18:16, MRAB wrote: > > > > On 2022-10-07 16:45, Skip Montanaro wrote: > >>> On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames > >>> > >>> wrote: > >>> 1. The culprit was me. As lazy as I am, I have used f-strings all over the

Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

ebug = logger_from(DEBUG) log_debug and log_debug(‘expensive %s’ % (complex(),)) Barry > > From: Python-list on > behalf of Barry > Date: Friday, October 7, 2022 at 1:30 PM > To: MRAB > Cc: python-list@python.org > Subject: Re: Ref-strings in logging messages (was: Pe

Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

To: MRAB Cc: python-list@python.org Subject: Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython) *** Attention: This is an external email. Use caution responding, opening attachments or clicking on links. *** > On 7 Oct 2022, at 18:16, MRAB wr

Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

> On 7 Oct 2022, at 18:16, MRAB wrote: > > On 2022-10-07 16:45, Skip Montanaro wrote: >>> On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames >>> wrote: >>> 1. The culprit was me. As lazy as I am, I have used f-strings all over the >>> place in calls to `logging.logger.debug()` and friends,

Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

On 2022-10-07 16:45, Skip Montanaro wrote: On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames wrote: 1. The culprit was me. As lazy as I am, I have used f-strings all over the place in calls to `logging.logger.debug()` and friends, evaluating all arguments regardless of whether the logger was

Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

> On 7 Oct 2022, at 16:48, Skip Montanaro wrote: > > On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames > wrote: > >> 1. The culprit was me. As lazy as I am, I have used f-strings all over the >> place in calls to `logging.logger.debug()` and friends, evaluating all >> arguments regardless of

Re: Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

Dang autocorrect. Subject first word was supposed to be "f-strings" not "ref-strings." Sorry about that. S On Fri, Oct 7, 2022, 10:45 AM Skip Montanaro wrote: > > > On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames > wrote: > >> 1. The culprit was me. As lazy as I am, I have used f-strings all over

Ref-strings in logging messages (was: Performance issue with CPython 3.10 + Cython)

On Fri, Oct 7, 2022 at 9:42 AM Andreas Ames wrote: > 1. The culprit was me. As lazy as I am, I have used f-strings all over the > place in calls to `logging.logger.debug()` and friends, evaluating all > arguments regardless of whether the logger was enabled or not. > I thought there was some

[issue402684] ceval/getargs: better messages for argument handling

Change by admin : -- github: None -> 33555 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue229740] mkhowto needs better diagnostic messages

Change by admin : -- github: None -> 33778 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue401839] better error messages

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue402684] ceval/getargs: better messages for argument handling

Change by admin : -- github: None -> 33555 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue401350] Fix SMTPlib for large messages

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400734] more helpful SyntaxError messages

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue402679] linuxaudiodev: better format names (and error messages)

Change by admin : -- github: None -> 33553 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue472202] dlerror()-messages bogus on netbsd

Change by admin : -- github: None -> 35346 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue466352] let mailbox.Maildir tag messages as read

Change by admin : -- github: None -> 35249 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue434992] Cleanup of warning messages

Change by admin : -- github: None -> 34655 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue403235] getargs: better error messages for wrong # of args

Change by admin : -- github: None -> 33716 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue402679] linuxaudiodev: better format names (and error messages)

Change by admin : -- github: None -> 33553 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue402681] issubclass() and isinstance() error messages

Change by admin : -- github: None -> 33554 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue216453] [Windows] TclError does not always produce error messages

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400926] StaError messages for Winsock errors.

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue402681] issubclass() and isinstance() error messages

Change by admin : -- github: None -> 33554 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue216453] [Windows] TclError does not always produce error messages

Change by admin : -- github: None -> 33323 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue401839] better error messages

Change by admin : -- github: None -> 33314 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue401350] Fix SMTPlib for large messages

Change by admin : -- github: None -> 33010 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400926] StaError messages for Winsock errors.

Change by admin : -- github: None -> 32632 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400734] more helpful SyntaxError messages

Change by admin : -- github: None -> 32518 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45410] python -m test -jN: write stderr in stdout to get messages in order

Change by STINNER Victor : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue47129] Improve errors messages in f-string syntax errors

Maciej Górski added the comment: Thanks for helping me with my very first python contribution! @eric.smith @lys.nikolaou -- ___ Python tracker ___

[issue47129] Improve errors messages in f-string syntax errors

Eric V. Smith added the comment: Thanks, @macgors! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> behavior ___ Python tracker ___

[issue47129] Improve errors messages in f-string syntax errors

Eric V. Smith added the comment: New changeset 7b44ade018cfe6f54002a3cee43e8aa415d4d635 by Maciej Górski in branch 'main': bpo-47129: Add more informative messages to f-string syntax errors (32127) https://github.com/python/cpython/commit/7b44ade018cfe6f54002a3cee43e8aa415d4d635

[issue43818] Email does not apply policy to multipart messages with defects

Martin Dengler added the comment: Possible related to https://github.com/python/cpython/pull/32137 and https://bugs.python.org/issue43323 -- ___ Python tracker ___

[issue47129] Improve errors messages in f-string syntax errors

Maciej Górski added the comment: I agree as well. I will change it to the new version :) Thanks for your input in this. -- ___ Python tracker ___

[issue47129] Improve errors messages in f-string syntax errors

Lysandros Nikolaou added the comment: I like the newest suggestion by @Jelle better as well. -- ___ Python tracker ___ ___

[issue47129] Improve errors messages in f-string syntax errors

Eric V. Smith added the comment: >From a suggestion by @Jelle on the python discord server: how about just >"f-string: expression required before '!'"? -- ___ Python tracker

[issue43818] Email does not apply policy to multipart messages with defects

Change by Martin Dengler : -- nosy: +mdengler ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47129] Improve errors messages in f-string syntax errors

Maciej Górski added the comment: Understandable. In this case I can maybe propose something along the lines of "f-string: empty expression not allowed (Conversion specifier '!' can only follow non-empty expressions)", and so on for each of the specifiers. This way the original message is

[issue47129] Improve errors messages in f-string syntax errors

Eric V. Smith added the comment: I'm not convinced this is an improvement. I don't think someone trying '!' in an f-string expression happens often enough to worry about that specific error message. And a generic "optional specifier" isn't great. If we're going to do this, it should

[issue47129] Improve errors messages in f-string syntax errors

Change by Pablo Galindo Salgado : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47129] Improve errors messages in f-string syntax errors

Change by Maciej Górski : -- keywords: +patch pull_requests: +30206 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32127 ___ Python tracker ___

[issue47129] Improve errors messages in f-string syntax errors

n error with the message: "f-string: optional specifier '%c' must follow a non-empty expression. -- components: Parser messages: 416069 nosy: lys.nikolaou, macgors, pablogsal priority: normal severity: normal status: open title: Improve errors messages in f-string syntax error

[issue23578] struct.pack error messages do not indicate which argument was invalid

Change by Irit Katriel : -- versions: +Python 3.11 -Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue46940] Suggestion messages don't properly work in nested getattr calls

Change by Zara Youmi : -- components: +2to3 (2.x to 3.x conversion tool), C API, Extension Modules, IO, Installation, SSL, Unicode, Windows nosy: +ezio.melotti, paul.moore, steve.dower, tim.golden, vstinner, zach.ware, zarayoumi3 type: -> resource usage Added file:

[issue46940] Suggestion messages don't properly work in nested getattr calls

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue46940] Suggestion messages don't properly work in nested getattr calls

Pablo Galindo Salgado added the comment: New changeset 3594ebca2cacf5d9b5212d2c487fd017cd00e283 by Pablo Galindo Salgado in branch '3.10': [3.10] bpo-46940: Don't override existing AttributeError suggestion information (GH-31710) (GH-31724)

[issue46940] Suggestion messages don't properly work in nested getattr calls

Change by Pablo Galindo Salgado : -- pull_requests: +29840 pull_request: https://github.com/python/cpython/pull/31724 ___ Python tracker ___

[issue46940] Suggestion messages don't properly work in nested getattr calls

Pablo Galindo Salgado added the comment: New changeset 3b3be05a164da43f201e35b6dafbc840993a4d18 by Pablo Galindo Salgado in branch 'main': bpo-46940: Don't override existing AttributeError suggestion information (GH-31710)

[issue46940] Suggestion messages don't properly work in nested getattr calls

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +29829 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31710 ___ Python tracker

[issue46940] Suggestion messages don't properly work in nested getattr calls

e metadata information in the exception object and it tries to produce an error message for the attribute "color" instead of "_color". -- assignee: pablogsal messages: 414623 nosy: pablogsal priority: normal severity: normal status: open title: Suggestion messages don't

[issue31084] QueueHandler not formatting messages

Change by Erik Montnemery : -- nosy: +emontnemery nosy_count: 2.0 -> 3.0 pull_requests: +29505 pull_request: https://github.com/python/cpython/pull/31355 ___ Python tracker

[issue46575] One-off errors in hashlib.scrypt error messages

New submission from Ron Kaminsky : There are one-off errors in upper bounds given in the error messages for hashlib.scrypt(...). MAX_INT *is* accepted (and at least for maxmem, works). See https://github.com/python/cpython/blob/8fb36494501aad5b0c1d34311c9743c60bb9926c/Modules/_hashopenssl.c

[issue39486] Confusing error messages for %-formatting, related to escaped %-characters

uot;, line 1, in ValueError: unsupported format character '%' (0x25) at index 2 -- nosy: +iritkatriel title: bug in %-formatting in Python, related to escaped %-characters -> Confusing error messages for %-formatting, related to escaped %-characters versions: +Python 3.11 -Python 3.7 _

[issue39464] Allow translating argparse error messages

Irit Katriel added the comment: Closed issue26726 as duplicate of this. -- nosy: +iritkatriel versions: +Python 3.10, Python 3.11 ___ Python tracker ___

[issue1599254] mailbox: other programs' messages can vanish without trace

Irit Katriel added the comment: Reproduced on 3.11 - the test in mailbox-test.patch fails. -- nosy: +iritkatriel versions: +Python 3.10, Python 3.11, Python 3.9 -Python 2.7, Python 3.4, Python 3.5 ___ Python tracker

[issue44166] Make IndexError messages for list more informative

Raymond Hettinger added the comment: Thank for the suggestion. While we're going to a pass on this one, no doubt there are other places that language can improve its communication with the user. Please continue to submit ideas and patches. --

[issue44166] Make IndexError messages for list more informative

Change by Raymond Hettinger : -- assignee: -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44166] Make IndexError messages for list more informative

Change by Raymond Hettinger : -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue44166] Make IndexError messages for list more informative

Pablo Galindo Salgado added the comment: I concur with Serhiy and Raymond and I would prefer to leave as is. -- ___ Python tracker ___

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

Pablo Galindo Salgado added the comment: Check my multiple comments in PR29916 -- ___ Python tracker ___ ___ Python-bugs-list

[issue44166] Make IndexError messages for list more informative

Vedran Čačić added the comment: > fix typically isn't replacing s[i] with s[i - 5] ... especially since that will still raise IndexError (in case when i==15 and len(s)==10). ;-P -- nosy: +veky ___ Python tracker

[issue44166] Make IndexError messages for list more informative

Raymond Hettinger added the comment: Here's another way to think of it: The call s[i] raising an IndexError isn't a numerical error, it is a conceptual error. Knowing that i==15 and len(s)==10 doesn't usually help resolve the problem. The fix typically isn't replacing s[i] with s[i -

[issue44166] Make IndexError messages for list more informative

Raymond Hettinger added the comment: I also share Serhiy's concerns and prefer that it be left as-is. Conceptually, adding more information in the error message would make it more useful for debugging, but in practice, it would rarely be helpful. In teaching and coaching Python, I've

[issue44166] Make IndexError messages for list more informative

Spencer Brown added the comment: One potential solution would be to add two Py_ssize_t to IndexError, storing the index and length along with the existing exception value. Then __str__() can append that to the message if set, perhaps having len be negative to signal they're not passed. An

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

theeshallnotknowethme added the comment: Can I know the reason for rejection? -- ___ Python tracker ___ ___ Python-bugs-list

[issue44166] Make IndexError messages for list more informative

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44166] Make IndexError messages for list more informative

Akash Mishra added the comment: While browsing some traceback error reporting i land on this solution threads. Specially beginner face traceback error for - KeyError - IndexError (As mentioned in current message thread) - ValueError .. It is sometime self explanatory from error reports

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

Change by theeshallnotknowethme : -- resolution: -> rejected ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

Change by theeshallnotknowethme : -- resolution: rejected -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

theeshallnotknowethme added the comment: I actually didn't know bpo-45982 existed. -- ___ Python tracker ___ ___ Python-bugs-list

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

Eric V. Smith added the comment: Since the two reported problems are unrelated, this should be two bug reports. The first one does seem like a duplicate, as Pablo mentions. I haven’t checked to see if the second one already has an issue. -- nosy: +eric.smith

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

Pablo Galindo Salgado added the comment: Actually, is not technically a duplicate of https://bugs.python.org/issue45982 but is related. -- resolution: duplicate -> rejected ___ Python tracker

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

Pablo Galindo Salgado added the comment: Duplicate of https://bugs.python.org/issue45982 -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

Change by theeshallnotknowethme : -- keywords: +patch pull_requests: +28142 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29916 ___ Python tracker

[issue45984] Error messages for invalid string prefixes and potential attribute accesses

kf'dsdsfddsf' ^^ SyntaxError: invalid string prefix 'kf' -- components: Parser messages: 407687 nosy: February291948, lys.nikolaou, pablogsal priority: normal severity: normal status: open title: Error messages for invalid string prefixes and potential attribute access

[issue45982] Bug in Error messages

Change by Pablo Galindo Salgado : -- Removed message: https://bugs.python.org/msg407685 ___ Python tracker ___ ___ Python-bugs-list

[issue45982] Bug in Error messages

Pablo Galindo Salgado added the comment: It doesn't happen anymore with the latest 3.10: >>> if datetime.now()strftime(...) != "19:50:00": pass File "", line 1 if datetime.now()strftime(...) != "19:50:00": pass SyntaxError: invalid syntax --

[issue45982] Bug in Error messages

Pablo Galindo Salgado added the comment: It doesn't happen anymore with the latest 3.10: >>> if datetime.now(),strftime(...) != "19:50:00": pass File "", line 1 if datetime.now(),strftime(...) != "19:50:00": pass ^ SyntaxError: invalid syntax --

[issue45982] Bug in Error messages

Matt Wozniski added the comment: > Syntactically, this could be many possible errors: missing comma, missing > period, missing parens, missing brackets, etc. Syntactically, it cannot be a missing comma. Adding the comma is a syntax error. $ python3 -c 'if datetime.now(),strftime(...) !=

[issue45982] Bug in Error messages

Pablo Galindo Salgado added the comment: I concur with Eric: the purpose of the error message is a suggestion based in the most likely cause. Also we have recently refined this so I will trigger in less uncommon situations. -- resolution: -> not a bug stage: -> resolved status:

[issue45982] Bug in Error messages

Eric V. Smith added the comment: Syntactically, this could be many possible errors: missing comma, missing period, missing parens, missing brackets, etc. A human can figure it out based on semantics, but based purely on syntax, I think this error message is good enough. --

[issue45982] Bug in Error messages

Change by Dong-hee Na : -- nosy: +corona10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45982] Bug in Error messages

New submission from UnknownLITE : A dot is missing between `now()` and `strftime` but it is suggesting that most probably a comma is missing. -- components: Interpreter Core files: Screenshot 2021-12-04 202054.png messages: 407670 nosy: UnknownLITE priority: normal severity: normal

[issue45759] Improve error messages for non-matching `elif`/`else` statements

Change by theeshallnotknowethme : -- pull_requests: +28012 pull_request: https://github.com/python/cpython/pull/29775 ___ Python tracker ___

[issue45759] Improve error messages for non-matching `elif`/`else` statements

Change by theeshallnotknowethme : -- pull_requests: +27765 pull_request: https://github.com/python/cpython/pull/29513 ___ Python tracker ___

[issue45759] Improve error messages for non-matching `elif`/`else` statements

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45759] Improve error messages for non-matching `elif`/`else` statements

Change by Alex Waygood : -- title: non-matching `elif`/`else` statements with uninformative errors -> Improve error messages for non-matching `elif`/`else` statements ___ Python tracker <https://bugs.python.org/issu

  1   2   3   4   5   6   7   8   9   10   >