Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution

Ok, had received response on pyinstaller mailing list, but, also just related to trying clean uninstall/reinstall of modules, but, while checking that out, something else occurred to me, and, it now operates as it should. Anyway, what seemed to be causing issue was actually that, since,

Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution

Ok, last update for now - checked out the following page on pyinstaller.org, and, ended up posting to the mailing list, so, let's see: https://pyinstaller.org/en/latest/when-things-go-wrong.html Jacob Kruger +2782 413 4791 "Resistance is futile!...Acceptance is versatile..." On 2024/04/02

Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution

> On 1 Apr 2024, at 15:52, Jacob Kruger via Python-list > wrote: > > Found many, many mentions of errors, with some of the same keywords, but, no > resolutions that match my exact issue at all. Try asking the pyinstaller developers. I think there is a mailing list. Barry > > > As in,

Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution

Found many, many mentions of errors, with some of the same keywords, but, no resolutions that match my exact issue at all. As in, most of them are mentioning older versions of python, and, mainly different platforms - mac and linux, but, various google searches have not mentioned much of

Re: Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution

> On 31 Mar 2024, at 13:24, Jacob Kruger via Python-list > wrote: > > pkg_resources.DistributionNotFound: The 'altgraph' distribution was not found > and is required by the application I think I have seen this error being discussed before… A web search for pyinstaller and that error leads

Trying to use pyinstaller under python 3.11, and, recently started receiving error message about specific module/distribution

This started happening this past week, and, while it's worked fine in the past, the moment I try to launch the pyinstaller process at all, to generate compiled output, or even if just launch it with no command line options, I receive the following error message

Matplotlib warning [error?] message

now I get: File e:\getmodpot.py:40 fig,ax = initPlot() File E:\mystuff.py:272 in initPlot fig,ax = plt.subplots(figsize=(xs,ys)) File ~\anaconda3\Lib\site-packages\matplotlib\pyplot.py:1501 in subplots fig = figure(**fig_kw) File

Re: Matplotlib warning [error?] message

On Sunday, February 18, 2024 at 10:48:29 PM UTC+3, Leif Svalgaard wrote: > The latest[?] version of Matplotlib cannot show a figure. I get the > annoying error message: "Matplotlib is currently using agg, which is a > non-GUI backend, so cannot show the figure" > I'm us

Matplotlib warning [error?] message

The latest[?] version of Matplotlib cannot show a figure. I get the annoying error message: "Matplotlib is currently using agg, which is a non-GUI backend, so cannot show the figure" I'm using Spyder python 3.11 on Windows 11. What to do? -- Leif Svalgaard l...@leif.org

Re: f-string error message

t; However, to my mind it is not the format string that is invalid, but the > value supplied to it. > Would it be possible to have a different error message, something like > > ValueError: int expected in format string but decimal.Decimal found > > Or am I missing something? It's up to the type

f-string error message

. However the following error message confused me for a while when it happened in real code: import decimal x=42 f"{x:3d}" ' 42' x=decimal.Decimal('42') f"{x:3d}" Traceback (most recent call last):   File "", line 1, in ValueError: invalid format string I underst

[issue535324] "if foo=bar:" error-message

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

[issue486826] bogus error message on bad parameters

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

[issue476557] Wrong error message for file.write(a, b)

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

[issue224758] Bogus error message from os.getlogin()

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

[issue416034] Confusing error message for top global

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

[issue232313] error message confusing for assignment in lambda

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

[issue224758] Bogus error message from os.getlogin()

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

[issue217241] class.method(*([self]+args)) gave me a 'unbound method must be called with class instance 1st argument" error message.

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

[issue400842] better error message for unicode coercian failure

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

[issue400874] Better error message with UnboundLocalError

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

[issue217241] class.method(*([self]+args)) gave me a 'unbound method must be called with class instance 1st argument" error message.

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

[issue400874] Better error message with UnboundLocalError

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

[issue400842] better error message for unicode coercian failure

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

[issue46134] Confusing error message for AttributeError with dataclasses

Alex Waygood added the comment: Closing due to lack of response from OP. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue31140] Insufficient error message with incorrect formated string literal

Peter Lovett added the comment: Thanks Eric. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31140] Insufficient error message with incorrect formated string literal

Eric V. Smith added the comment: Yes, they should update Python. A lot of work went in to fixing these issues, and won't be backported. -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue31140] Insufficient error message with incorrect formated string literal

Peter Lovett added the comment: I'm not getting the problem on 3.9.7 on Windows. Did get it on 3.7 (3.7.11?) on a different Windows machine last week. Not getting the problem on 3.10.4 The wrong line number is a problem for IDLE's syntax highlighter, that marks the first line as a Syntax

[issue31140] Insufficient error message with incorrect formated string literal

Change by Peter Lovett : -- nosy: +PeterL777 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue27132] New assert method that checks an error message for a list of strings

Irit Katriel added the comment: > Personally I'd write multiple asserts rather than regex permutations. I would too, because then when one of them fails it's clear which of the strings is missing. -- nosy: +iritkatriel ___ Python tracker

[issue46170] Improving the error message when subclassing NewType

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

[issue46170] Improving the error message when subclassing NewType

Jelle Zijlstra added the comment: New changeset f391f9bf28f0bba7939d9f9e5a7a6396d2b0df62 by James Hilton-Balfe in branch 'main': bpo-46170: Improve the error message when subclassing NewType (GH-30268) https://github.com/python/cpython/commit/f391f9bf28f0bba7939d9f9e5a7a6396d2b0df62

[issue46927] Improve error message for subscripting non-generic types

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

[issue46927] Improve error message for subscripting non-generic types

Serhiy Storchaka added the comment: New changeset ab9301a28fa431d7a32163126fc96de3b2ce6107 by Serhiy Storchaka in branch 'main': bpo-46927: Include the type's name in the error message for subscripting non-generic types (GH-31694) https://github.com/python/cpython/commit

[issue46927] Improve error message for subscripting non-generic types

Change by Alex Waygood : -- nosy: +Jelle Zijlstra ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46927] Improve error message for subscripting non-generic types

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +29814 stage: -> patch review pull_request: https://github.com/python/cpython/pull/31694 ___ Python tracker

[issue46927] Improve error message for subscripting non-generic types

Change by Serhiy Storchaka : -- nosy: +gvanrossum, kj ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46927] Improve error message for subscripting non-generic types

criptable, but list[str] works, and it is not clear from the error message for what type it is failed. The following PR changes an error message: >>> int[str] Traceback (most recent call last): File "", line 1, in TypeError: type 'int' is not subscriptable -- compone

[issue34191] argparse: Missing subparser error message should be more clear

Change by Ned Deily : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> argparse fails with required subparsers, un-named dest, and empty argv ___ Python tracker

[issue34191] argparse: Missing subparser error message should be more clear

Jacob Walls added the comment: Duplicate of issue29298 (fixed) -- nosy: +jacobtylerwalls ___ Python tracker ___ ___

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

Change by Alex Waygood : -- nosy: +AlexWaygood ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

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

Terry J. Reedy added the comment: I think the incorrect qualification should be dropped, if sanely feasible. More misleading are hidden positional-only args. Doc: min(iterable, *[, key, default]) min(arg1, arg2, *args[, key]) >>> min(iterator=(1,3)) Traceback (most recent call last):

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

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

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

Anders Hovmöller added the comment: For `foo(a, /, b)`, it could be: "TypeError: foo() missing 1 required argument 'a', and one required positional argument 'b'. If we start on this road there are some more, like for `def foo(a, *, b)` you get the error "TypeError: foo() missing 1 required

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

Eric V. Smith added the comment: Given this current behavior: >>> def foo(a, /, b): pass ... >>> foo() Traceback (most recent call last): File "", line 1, in TypeError: foo() missing 2 required positional arguments: 'a' and 'b' What would you suggest? I agree the current messages aren't

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

Anders Hovmöller added the comment: Just dropping the word "positional" is very good. That word is a lie, and just removing it makes it true. -- ___ Python tracker ___

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

Eric V. Smith added the comment: I guess the technically correct term is positional-or-keyword, but that seems like too much: https://docs.python.org/3/glossary.html I think dropping "positional" doesn't increase the precision of the error message, but I'll admit I can't think o

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

, but it's just "argument". The proof is that if you call it with foo(a=3) it works fine. -- components: Interpreter Core messages: 412510 nosy: Anders.Hovmöller priority: normal severity: normal status: open title: Incorrect error message: "missing 1 required positi

[issue44264] Add descriptive error message when environment variable not detected

Irit Katriel added the comment: > os.environ defines the __delitem__ method to call C unsetenv(). Thus `del > os.environ[varname]` does unset the environment variable, at least at the > level of the C runtime. For the current process, yes. But it's not that what the user needs to do to

[issue44264] Add descriptive error message when environment variable not detected

Eryk Sun added the comment: This is just a point of clarification. > my del did not change the environment variable os.environ defines the __delitem__ method to call C unsetenv(). Thus `del os.environ[varname]` does unset the environment variable, at least at the level of the C runtime.

[issue44264] Add descriptive error message when environment variable not detected

Irit Katriel added the comment: I vote to reject this proposal. Unless another core dev disagrees, I will close this issue. -- status: pending -> open ___ Python tracker ___

[issue44264] Add descriptive error message when environment variable not detected

Irit Katriel added the comment: > if a user of a Python program were to come across it, it may not indicate > what they needed to do to avoid the crash. The user of a program should not see this exception. The program should translate it to an error that would make sense to the user.

[issue44264] Add descriptive error message when environment variable not detected

Irit Katriel added the comment: It's not necessarily true that the environment variable is not set just because the key is not in os.environ. In this example my del did not change the environment variable: >>> import os >>> os.environ['TMPDIR']

[issue43814] Fix the error message for disallowed __weakref__ slots

Change by Irit Katriel : -- versions: +Python 3.11 -Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___

[issue45686] ElementTree.Element.extend: bad error message when error occurs in generator

Change by Irit Katriel : -- versions: -Python 3.6, Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue46242] Improve error message when attempting to extend an enum with `__call__`

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

[issue46242] Improve error message when attempting to extend an enum with `__call__`

Ethan Furman added the comment: New changeset e674e48ddc2712f28cc7ecdc66a6c328066694b0 by Nikita Sobolev in branch 'main': bpo-46242: [Enum] better error message for extending `Enum` with members (GH-30357) https://github.com/python/cpython/commit/e674e48ddc2712f28cc7ecdc66a6c328066694b0

[issue46242] Improve error message when attempting to extend an enum with `__call__`

Change by Alex Waygood : -- assignee: -> ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46239] Incosistent error message in asyncio: windows_events / windows_utils

Andrew Svetlov added the comment: New changeset cf48a148190a6ccadc144cab2e2046e95c20fb57 by Miss Islington (bot) in branch '3.10': bpo-46239: improve error message when importing `asyncio.windows_events` (GH-30353) (#30388) https://github.com/python/cpython/commit

[issue46239] Incosistent error message in asyncio: windows_events / windows_utils

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

[issue46239] Incosistent error message in asyncio: windows_events / windows_utils

miss-islington added the comment: New changeset 86d1b8c13fcaf8a974cf2ae23b31fe87dfdb6267 by Miss Islington (bot) in branch '3.9': bpo-46239: improve error message when importing `asyncio.windows_events` (GH-30353) https://github.com/python/cpython/commit

[issue46239] Incosistent error message in asyncio: windows_events / windows_utils

Change by miss-islington : -- pull_requests: +28598 pull_request: https://github.com/python/cpython/pull/30389 ___ Python tracker ___

[issue46239] Incosistent error message in asyncio: windows_events / windows_utils

Change by miss-islington : -- nosy: +miss-islington nosy_count: 3.0 -> 4.0 pull_requests: +28597 pull_request: https://github.com/python/cpython/pull/30388 ___ Python tracker

[issue46239] Incosistent error message in asyncio: windows_events / windows_utils

Andrew Svetlov added the comment: New changeset 5a2a65096c3ec2d37f33615f2a420d2ffcabecf2 by Nikita Sobolev in branch 'main': bpo-46239: improve error message when importing `asyncio.windows_events` (GH-30353) https://github.com/python/cpython/commit/5a2a65096c3ec2d37f33615f2a420d2ffcabecf2

[issue46242] Improve error message when attempting to extend an enum with `__call__`

Change by Alex Waygood : -- title: Improve error message when creating an enum with `__call__` -> Improve error message when attempting to extend an enum with `__call__` ___ Python tracker <https://bugs.python.org/issu

[issue46242] Improve error message when creating an enum with `__call__`

Change by Nikita Sobolev : -- keywords: +patch pull_requests: +28571 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30357 ___ Python tracker ___

[issue46242] Improve error message when creating an enum with `__call__`

y", line 899, in _get_mixins_ raise TypeError('Cannot extend enumerations') ^ TypeError: Cannot extend enumerations ``` I propose to use the first error message in this case as well. Moreover, this behavior is not covered with tests: ``` » ag

[issue46239] Incosistent error message in asyncio: windows_events / windows_utils

Change by Nikita Sobolev : -- keywords: +patch pull_requests: +28566 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30353 ___ Python tracker ___

[issue46239] Incosistent error message in asyncio: windows_events / windows_utils

New submission from Nikita Sobolev : When trying to import both `windows_events` and `windows_utils` on non-Windows, they both fail. But, they fail differently. `windows_utils` produces a good error message, whil `windows_events` produces a strange one. Good: ``` Python 3.11.0a3+ (heads

[issue46170] Improving the error message when subclassing NewType

Nikita Sobolev added the comment: Turns out modern docs already have this problem fixed: https://docs.python.org/3/library/typing.html#newtype -- ___ Python tracker ___

[issue46170] Improving the error message when subclassing NewType

Nikita Sobolev added the comment: > So maybe those docs are incorrect? I can't find anything in PEP 484 about > this. Mypy even has an explicit test that NewType of NewType should work:

[issue46170] Improving the error message when subclassing NewType

Guido van Rossum added the comment: Weird, the docs you cite claims # Also does not typecheck ProUserId = NewType('ProUserId', UserId) but when I try it, it works at runtime and passes mypy (even with --strict) and also pyright. So maybe those docs are incorrect? I can't find

[issue46170] Improving the error message when subclassing NewType

Gobot1234 added the comment: > Do you have evidence that people make this particular mistake often? And that > the suggested solution is indeed what they should use? Why would you want to > subclass UserId? I was just trying to implement something that I thought had a non-obvi

[issue46170] Improving the error message when subclassing NewType

Guido van Rossum added the comment: Do you have evidence that people make this particular mistake often? And that the suggested solution is indeed what they should use? Why would you want to subclass UserId? Do we have examples of other error messages split across two lines like this?

[issue46170] Improving the error message when subclassing NewType

Change by Gobot1234 : -- keywords: +patch pull_requests: +28485 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30268 ___ Python tracker ___

[issue46170] Improving the error message when subclassing NewType

Change by Alex Waygood : -- nosy: +AlexWaygood ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46170] Improving the error message when subclassing NewType

Nikita Sobolev added the comment: > I'd be happy to patch this myself if this sounds like a good idea. Oh, please, go ahead! :) Would be happy to review. -- ___ Python tracker

[issue46170] Improving the error message when subclassing NewType

Nikita Sobolev added the comment: This seems like a good idea to me. I will send a PR for others to judge :) -- nosy: +sobolevn ___ Python tracker ___

[issue46170] Improving the error message when subclassing NewType

New submission from Gobot1234 : I'd like to propose making the error message when subclassing typing.NewType much more understandable. Currently it looks like: ``` TypeError: NewType.__init__() takes 3 positional arguments but 4 were given ``` But I think we could do much better by adding

[issue46134] Confusing error message for AttributeError with dataclasses

Eric V. Smith added the comment: Please show the error you're getting, including the traceback. -- status: pending -> open ___ Python tracker ___

[issue46134] Confusing error message for AttributeError with dataclasses

'Character' object has no attribute 'sort_index'. Did you mean: 'sortindex'? ``` This seems like the correct error message to me. The issue is that your "Character" class has a field named "sort_index", but that field is never assigned to. Instead, you assign an attri

[issue16977] argparse: mismatch between choices parsing and usage/error message

Irit Katriel added the comment: We could make the error message less wrong: >>> p.parse_args(['d']) usage: [-h] {a,b,c} : error: argument a: invalid choice: 'd' (choose a value in 'abc') % git diff diff --git a/Lib/argparse.py b/Lib/argparse.py index b44fa4f0f6..f03cc1f110 100644

[issue28559] Unclear error message when raising wrong type of exceptions

Change by Irit Katriel : -- resolution: -> rejected stage: patch review -> resolved status: pending -> closed ___ Python tracker ___

[issue44377] Truncated error message of original function while multiprocessing or multithreading

Change by Andrei Kulakov : -- type: -> behavior versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.7 ___ Python tracker ___

[issue44377] Truncated error message of original function while multiprocessing or multithreading

Andrei Kulakov added the comment: Prasanth: can you provide a bit more details, are you saying that this line: https://github.com/python/cpython/blob/2109f7880b65755329a877da3a7f8a362de07350/Lib/multiprocessing/pool.py#L86 .. truncates the exception msg? What is the exact exception type that

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

Change by Irit Katriel : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.11 ___ Python tracker ___

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

Irit Katriel added the comment: New changeset 5bb7ef2768be5979b306e4c7552862b1746c251d by Irit Katriel in branch 'main': bpo-45607: Make it possible to enrich exception displays via setting their __note__ field (GH-29880)

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

Change by Irit Katriel : -- keywords: +patch pull_requests: +28105 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29880 ___ Python tracker ___

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

Irit Katriel added the comment: Issue28953 is another use case for this feature. -- ___ Python tracker ___ ___ Python-bugs-list

[issue9682] socket.create_connection error message for domain subpart with invalid length is very confusing

Irit Katriel added the comment: Reproduced on 3.11: Traceback (most recent call last): File "/Users/iritkatriel/src/cpython-1/Lib/encodings/idna.py", line 165, in encode raise UnicodeError("label empty or too long") ^ UnicodeError: label

[issue44678] Seperate error message for discontinuous padding in binascii.a2b_base64 strict mode

Andrei Kulakov added the comment: Looks like it's fixed so closing it.. -- nosy: +andrei.avk, kj resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue45721] Improve error message for OS command entered at >>> prompt

Change by Terry J. Reedy : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Attempt to give better errors for pip commands typed into the REPL ___ Python tracker

[issue45811] Improve error message when source code contains invisible control characters

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

[issue45811] Improve error message when source code contains invisible control characters

Pablo Galindo Salgado added the comment: New changeset 81f4e116ef7d30ef6e2041c2d6cf29af511a3a02 by Pablo Galindo Salgado in branch 'main': bpo-45811: Improve error message when source code contains invisible control characters (GH-29654) https://github.com/python/cpython/commit

[issue45811] Improve error message when source code contains invisible control characters

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

[issue45811] Improve error message when source code contains invisible control characters

Terry J. Reedy added the comment: I agree. -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue45811] Improve error message when source code contains invisible control characters

Change by Terry J. Reedy : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

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

Pablo Galindo Salgado added the comment: New changeset 5618c81e139419b4665dc1f1e8a468738546f542 by Pablo Galindo Salgado in branch '3.10': [3.10] bpo-45716: Improve the error message when using True/False/None as keywords in a call (GH-29413). (GH-29428) https://github.com/python/cpython

[issue45811] Improve error message when source code contains invisible control characters

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

[issue45811] Improve error message when source code contains invisible control characters

and_C1_control_codes -- components: Interpreter Core messages: 406379 nosy: steven.daprano priority: normal severity: normal status: open title: Improve error message when source code contains invisible control characters type: enhancement versions: Python 3.11 _

  1   2   3   4   5   6   7   8   9   10   >