[issue45812] SystemError when using code.interact

Andre Roberge added the comment: I am sorry, but I am not set up to work from the main branch and must rely on official releases. In the future, for alpha and beta releases, I will try to wait for the next release, see immediately if I can reproduce bugs that I had noted before, and submit

[issue45738] 3.11 exec raises SystemError instead of SyntaxError on char after line continuation

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue45738> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45781] Deleting __debug__ should be an SyntaxError

Andre Roberge added the comment: What version are you using? As far as I can test, it has become a syntax error since 3.10. Here is the result with the latest 3.11 alpha > python Python 3.11.0a2 (tags/v3.11.0a2:e2b4e4b, Nov 5 2021, 20:00:05) [MSC v.1929 64 bit (AMD64)] on win32 Type &q

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

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue45759> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45716] Confusing parsing error message when trying to use True as keyword argument

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue45716> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45721] Improve error message when python shell command is entered at the REPL prompt

Andre Roberge added the comment: I think that "trying to run a shell command" might not be easy to understand by a beginner. If the special case of r"python\s+" is added, perhaps r"pip\s+" should be considered as well since many sites on the Internet suggest t

[issue45607] Make it possible to enrich an exception's error message

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue45607> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44166] Make IndexError messages for list more informative

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue44166> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46042] Error range of "duplicate argument" SyntaxErrors is too big

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue46042> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46004] Incorrect bad token identified in 3.10.1

New submission from Andre Roberge : In Python 3.10.1, a change occurred compared with 3.10.0 so that an incorrect token is flagged for a SyntaxError. Also, in 3.11.0a2, the suggestion made about having forgotten a comma is incorrect. Python 3.10.1 for x range(4

[issue46004] Incorrect bad token identified in 3.10.1

Andre Roberge added the comment: >From >(https://friendly-traceback.github.io/docs/syntax_tracebacks_en_3.10.html#for-loop-missing-in-operator), > this is what was shown for Python 3.10.0 for x range(4): ^^ SyntaxError: invalid syntax. Perhaps you forgot a com

[issue44648] Inspect.getsource raises wrong error on classes in interactive session

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue44648> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46838] Parameters and arguments parser syntax error improvments

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue46838> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46902] Typo hint message for from-imports?

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue46902> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47156] IDLE: make use of extended SyntaxError info.

Andre Roberge added the comment: > (Anyone really want log of error?) If by this you mean having access to the error from a known place (like sys.last_traceback or something else specific to IDLE but available from a script), then the answer from me is definitely yes. -- n

[issue46637] Incorrect error message: "missing 1 required positional argument"

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue46637> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46652] Use code.co_qualname to provide richer information

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker <https://bugs.python.org/issue46652> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43476] Enabling access to showsyntaxerror for IDLE's shell

Andre Roberge added the comment: As far as I am concerned, this issue can be closed. I have found a workaround which allows me to reproduce and analyze the SyntaxError that are not captured by custom exception hook. -- ___ Python tracker <ht

[issue46291] [doc] First argument to raise can also be BaseException

Andre Roberge added the comment: Irit: In all the books and tutorials I have seen, the advice is to try to catch specific exceptions whenever possible or, *at most*, to catch Exception (and not BaseException). This is to allow, for example, a program to be interrupted

[issue46291] [doc] First argument to raise can also be BaseException

Andre Roberge added the comment: Irit: Gregor indicates that, while the tutorial refers to "a class that derives from Exception", the Python Reference Language states exceptions should be subclasses of BaseException (which Exception *is*). You then invited Gregor to subm

[issue46237] Incorrect line reported in syntax error

Andre Roberge added the comment: > This also affects 3.9 I imagine, no? Yes. And, from what I can tell, the same incorrect line is indicated at least all the way back to Python 3.6 (where it was "invalid token" instead of "invalid decimal literal).

[issue46291] [doc] First argument to raise can also be BaseException

Andre Roberge added the comment: In https://docs.python.org/3/library/exceptions.html#Exception, it is written: "All built-in, non-system-exiting exceptions are derived from this class. All user-defined exceptions should also be derived from this class." Yes, technically, the r

[issue46291] [doc] First argument to raise can also be BaseException

Andre Roberge added the comment: >> For this advice (catching Exception and not BaseException) to be correct, >> users should be advised (as they are in the tutorial) to raise exceptions >> derived from Exception (and not BaseException). > I disagree with that. You

<    1   2