[issue24650] Error in yield expression documentation

miss-islington added the comment: New changeset 75a1865d1ce352909ad9a30d001486bbd7d3ed75 by Miss Islington (bot) in branch '3.10': [3.10] bpo-24650: Use full term "generator function" in yield expressions docs (GH-24663) (GH-30461)

[issue24650] Error in yield expression documentation

miss-islington added the comment: New changeset 8bc68140cbe8230cf048bc04faf927c1413066d1 by Miss Islington (bot) in branch '3.9': bpo-24650: Use full term "generator function" in yield expressions docs (GH-24663)

[issue24650] Error in yield expression documentation

Irit Katriel added the comment: New changeset 273cb8e7577d143830404f6779946a0bedb58758 by Jacob Walls in branch 'main': bpo-24650: Use full term "generator function" in yield expressions docs (GH-24663) https://github.com/python/cpython/commit/273cb8e7577d143830404f6779946a0bedb58758

[issue24650] Error in yield expression documentation

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

[issue24650] Error in yield expression documentation

Change by miss-islington : -- nosy: +miss-islington nosy_count: 5.0 -> 6.0 pull_requests: +28664 pull_request: https://github.com/python/cpython/pull/30461 ___ Python tracker

[issue24650] Error in yield expression documentation

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

[issue46277] '''...''' error

Mark Dickinson added the comment: https://github.com/ipython/ipython/issues/12843 looks very closely related, and may be the exact same bug. -- nosy: +mark.dickinson ___ Python tracker

[issue46275] caret location for syntax error pointing with f-strings

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

[issue22739] "There is no disk in the drive" error

Pop Expangea added the comment: Forgot to comment versions: pdoc: 8.1.0 Python: 3.8.7 Platform: Windows-7-6.1.7601-SP1 -- ___ Python tracker ___

[issue22739] "There is no disk in the drive" error

Pop Expangea added the comment: Probably not a Python bug, but I have detected this problem a couple of times, and it always happened the same way, while using pdoc package in a Python script. Steps to reproduce the behavior: 1. Connect mobile telephone (Avenzo Xirius 5.5 AV112) to my

[issue46277] '''...''' error

STINNER Victor added the comment: vstinner@apu$ python3 Python 3.10.1 (main, Dec 9 2021, 00:00:00) [GCC 11.2.1 20211203 (Red Hat 11.2.1-7)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> str_='''... ... ... ... .. ... .. ... . ... ... ... ''' >>> str_

[issue46277] '''...''' error

Yongfan Ming added the comment: just happend in jupyter notebook . -- Added file: https://bugs.python.org/file50543/20220106143913.png ___ Python tracker ___

[issue46277] '''...''' error

: open title: '''...''' error type: behavior versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue46277> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46275] caret location for syntax error pointing with f-strings

William Navaraj added the comment: A potential solution or in that direction https://github.com/williamnavaraj/cpython/tree/fix-issue-46275 Example 1: ``` temp=f"blank {foo)" ``` temp=f"blank {foo)" ^ SyntaxError: f-string: unmatched ')' Example 2: ```

[issue46275] caret location for syntax error pointing with f-strings

two locations after the f-string (almost correct location of the f-strings as a whole but will be more helpful as much as possible to point where exactly the syntax error is) Example 2: ``` temp=f"blank ({foo(}" ``` temp=f"blank ({foo(}" ^ S

[issue46265] Error when cross compiling for hardfloat MIPS

/sdk/build_dir/target-mipsel_24kc+24kf_musl/Python-3.10.0/libpython3.10.so: undefined reference to `__fn_local_PyFloat_FromDouble.localalias' collect2: error: ld returned 1 exit status make[7]: *** [Makefile:602: python] Error 1 This error is only occurring for mipsel_24kc+24kf and not our other

[issue46262] Enum tests: Error path in `_missing_()` is not covered for `Flag` and `IntFlag`

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

[issue46262] Enum tests: Error path in `_missing_()` is not covered for `Flag` and `IntFlag`

Ethan Furman added the comment: New changeset 91bc6f9615eabb10090e2e4f0fe5913885a29c8c by Nikita Sobolev in branch 'main': bpo-46262: [Enum] test error path in `Flag._missing_` (GH-30408) https://github.com/python/cpython/commit/91bc6f9615eabb10090e2e4f0fe5913885a29c8c

[issue46262] Enum tests: Error path in `_missing_()` is not covered for `Flag` and `IntFlag`

Change by Ethan Furman : -- assignee: -> ethan.furman nosy: +ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue46262] Enum tests: Error path in `_missing_()` is not covered for `Flag` and `IntFlag`

Change by Alex Waygood : -- title: Error path in `_missing_()` is not covered for `enum.Flag` and `enum.IntFlag` -> Enum tests: Error path in `_missing_()` is not covered for `Flag` and `IntFlag` ___ Python tracker <https://bugs.pyth

[issue46262] Error path in `_missing_()` is not covered for `enum.Flag` and `enum.IntFlag`

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

[issue46262] Error path in `_missing_()` is not covered for `enum.Flag` and `enum.IntFlag`

New submission from Nikita Sobolev : I've noticed that `enum.Flag._missing_` has some uncovered paths. For example, this error is never checked: https://github.com/python/cpython/blob/31e43cbe5f01cdd5b5ab330ec3040920e8b61a91/Lib/enum.py#L1222-L1225 The same method for `Enum` has good

[issue46259] float formatting error?

John Holman added the comment: Thanks - sorry to waste your time. On Tue, 4 Jan 2022 at 18:17, Raymond Hettinger wrote: > > Raymond Hettinger added the comment: > > The two numbers you gave become the same when rounded to the limited > internal precision used by floats. > > >>>

[issue46259] float formatting error?

Raymond Hettinger added the comment: The two numbers you gave become the same when rounded to the limited internal precision used by floats. >>> 1.12345678901234 == 1.123456789011 True When it comes to displaying the number, Python tries to show the shortest possible member of the

[issue46259] float formatting error?

New submission from John Holman : Example: str(1.12345678901234) Out[24]: '1.123456789011' shouldn't the last digit should be 2? -- messages: 409696 nosy: johngholman priority: normal severity: normal status: open title: float formatting error? type: behavior versions: Python

[issue41945] http.cookies.SimpleCookie.parse error after [keys] or some JSON data values

="loaded" This not works: >>> ck.load('id=12345; complex_data={1:[1, 2]}; something="not loaded"') >>> print(ck) Set-Cookie: complex_data={1:[1, Set-Cookie: id=12345 Conclusion: Parsing JSON like cookie objects works, except quotes and without spaces. Exist

[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

[issue41987] singledispatchmethod raises an error when relying on a forward declaration

Jörn Heissler added the comment: Hello! git-bisect points at https://bugs.python.org/issue41341 https://github.com/python/cpython/pull/21553 It breaks both the examples from https://bugs.python.org/issue41987#msg379896 and https://bugs.python.org/issue41987#msg380803 -- nosy:

[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

[issue46237] Incorrect line reported in syntax error

New submission from arian-f : parsing this code results in a syntax error with an incorrect line number - it's always 1 f''' { 1_a }''' resulting in: File "", line 1 ( 1_a ) ^ SyntaxError: invalid decimal literal an analogue error occurs when parsing a fi

[issue45615] Missing test for type of error when printing traceback for non-exception

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

[issue45615] Missing test for type of error when printing traceback for non-exception

Irit Katriel added the comment: New changeset a82baed0e9e61c0d8dc5c12fc08de7fc172c1a38 by Irit Katriel in branch 'main': bpo-45615: Add missing test for printing traceback for non-exception. Fix traceback.py (GH-30091)

[issue40236] datetime.datetime.strptime get day error

Andrei Kulakov added the comment: I didn't realize that time.strptime is just using python module _strptime. -- ___ Python tracker ___

[issue46215] Wrong error line after using pdb

beda pišl added the comment: I tried this on current main branch, and I cannot reproduce the problem there. -- stage: -> resolved status: open -> closed ___ Python tracker

[issue40236] datetime.datetime.strptime get day error

Change by Andrei Kulakov : -- keywords: +patch pull_requests: +28534 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/30318 ___ Python tracker

[issue40236] datetime.datetime.strptime get day error

Andrei Kulakov added the comment: > I am open to discussion about trying to rationalize this behavior - it would > be a bit tricky but if we moved to our own implementation of the algorithm to > calculate %W we could detect this situation and throw an exception. Paul: I'm guessing here

[issue46215] Wrong error line after using pdb

New submission from beda pišl : Consider simple script: ``` for i in range(1): import pdb pdb.set_trace() x = y + z ``` After running it and pressing 'c' to continue: ``` test$ python test.py > /Users/bedrich.pisl/test/test.py(1)() -> for i in range(1): (Pdb) c ``` I get

[issue45321] Module xml.parsers.expat.errors misses error code constants of libexpat >=2.0

Change by Stefan Behnel : -- components: +XML resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> enhancement versions: -Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker

[issue45321] Module xml.parsers.expat.errors misses error code constants of libexpat >=2.0

Stefan Behnel added the comment: New changeset e18d81569fa0564f3bc7bcfd2fce26ec91ba0a6e by Sebastian Pipping in branch 'main': bpo-45321: Add missing error codes to module `xml.parsers.expat.errors` (GH-30188) https://github.com/python/cpython/commit/e18d81569fa0564f3bc7bcfd2fce26ec91ba0a6e

[issue46188] dictionary creation error

ons. The behaviour you see is correct. Except for the last line, which is a copy-and-paste error on your part: the actual last line is >>> dictionary {0: None, None: None, 2: 2, 4: 4, 6: 6, 8: 8} So there is no error here, everything is working as expected. If you need help understanding

[issue46188] dictionary creation error

% 2) == 0: ... return n ... return None >>> dictionary = {} >>> for i in range(10): ... dictionary[key_maker(i)] = i if key_maker(i) else "error" >>> dictionary {0: 'error', None: 'error', 2: 2, 4: 4, 6: 6, 8: 8} when I tried to print out the rest

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

tongxiaoge added the comment: We make SSL3 disappear to newly built dependencies, the test_ssl success. Refer to the modification of OpenSSL on fedoras (address: https://src.fedoraproject.org/rpms/openssl/tree/f34 ） ``` rm -f $RPM_BUILD_ROOT%{_sysconfdir}/pki/tls/*.dist +# Next step of

[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

[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:

[issue45321] Module xml.parsers.expat.errors misses error code constants of libexpat >=2.0

Change by Serhiy Storchaka : -- nosy: +eli.bendersky, scoder ___ 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

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

Christian Heimes added the comment: You are using a OpenSSL build with custom, additional patches and your code is crashing somewhere in OpenSSL. It is likely that your patches are causing issue. I'm not going to provide free service for custom builds. -- assignee: christian.heimes

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

Change by tongxiaoge : -- nosy: -christian.heimes, sxt1001, thatiparthy, vstinner Added file: https://bugs.python.org/file50512/python3.spec ___ Python tracker ___

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

tongxiaoge added the comment: I want to know whether this is an OpenSSL problem or a python 3 problem, and how to fix it? Thanks. (The OpenSSL source package is large and has not been uploaded successfully. We can download it from the OpenSSL official website) -- status: closed ->

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

Change by tongxiaoge : Added file: https://bugs.python.org/file50511/openssl-1.1.1-build.patch ___ Python tracker ___ ___ Python-bugs-list

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

Change by tongxiaoge : -- keywords: +patch Added file: https://bugs.python.org/file50510/openssl-1.1.1-fips.patch ___ Python tracker ___

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

Change by tongxiaoge : Added file: https://bugs.python.org/file50509/openssl.spec ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

Change by tongxiaoge : Added file: https://bugs.python.org/file50508/Makefile.certificate ___ Python tracker ___ ___ Python-bugs-list

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

tongxiaoge added the comment: Other information: ``` (gdb) f 2 #2 SSL_CTX_new (meth=0xe222cc30) at ssl/ssl_lib.c:3046 warning: Source file is more recent than executable. 3046ret->session_timeout = meth->get_timeout(); (gdb) l 3041ret->max_proto_version = 0; 3042

[issue44598] test_constructor (test.test_ssl.ContextTests) ... Fatal Python error: Segmentation fault

tongxiaoge added the comment: Today, I upgraded my version of Python3 to 3.9.9. When running test_ ssl,It has a segment error again. The version of OpenSSL I use is 1.1.1l, here is part of the stack information (the complete one is too long): ``` (gdb) bt #0 0x9e563830 in raise

[issue44413] Improvement mktime error reporting

Daniel McDonald added the comment: Sounds good, thank you, Terry -- type: enhancement -> behavior ___ Python tracker ___ ___

[issue44413] Improvement mktime error reporting

argument out of range after 2019 -> Improvement mktime error reporting type: behavior -> enhancement ___ Python tracker <https://bugs.python.org/issue44413> ___ ___ Pyth

[issue45996] Worse error from asynccontextmanager in Python 3.10

Andrew Svetlov added the comment: Sorry, I closed it because async behavior reflects sync version now. If you want to improve both -- you are welcome! Perhaps it is worth another issue with another problem description. -- resolution: fixed -> wont fix

[issue45996] Worse error from asynccontextmanager in Python 3.10

Dima Tisnek added the comment: I'm fine with guarding both. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue45996] Worse error from asynccontextmanager in Python 3.10

Thomas Grainger added the comment: > Actually I don't agree with Thomas's logic... his argument feels like > consistency for its own sake. Do you expect sync and async contextmanagers to act differently? Why would sync contextmanagers raise AttributeError and async contextmanagers raise a

[issue45996] Worse error from asynccontextmanager in Python 3.10

homas's logic... his argument feels like consistency for its own sake. I agree with the intention of the change for the arguments to be released (https://bugs.python.org/issue30306) but I disagree with the cryptic error. I'm sure we could have both argument release and readable exception,

[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 <https://bugs.python.org/issu

[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

[issue45996] Worse error from asynccontextmanager in Python 3.10

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

[issue45321] Module xml.parsers.expat.errors misses error code constants of libexpat >=2.0

Change by Roundup Robot : -- keywords: +patch nosy: +python-dev nosy_count: 2.0 -> 3.0 pull_requests: +28408 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30188 ___ Python tracker

[issue46115] Interrupting subprocess.popen in recursive calls by KeyboardInterrupt causes Fatal Python error.

New submission from Xinmeng Xia : Popen works when stdio fds are available. However, when interrupting popen in a recursive function call. The Python interpreter reports a Fatal Python error. test.py import subprocess import os import sys def

[issue45635] Tidy up error handling in traceback.c / python run.c

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

[issue45635] Tidy up error handling in traceback.c / python run.c

Irit Katriel added the comment: New changeset 8d6155ee9d1b05946f951d0ba602b9f63810fe0f by Irit Katriel in branch 'main': bpo-45635: Do not suppress errors in functions called from _PyErr_Display (GH-30073) https://github.com/python/cpython/commit/8d6155ee9d1b05946f951d0ba602b9f63810fe0f

[issue46087] format library documentation error

Change by Serhiy Storchaka : -- nosy: +eric.smith resolution: -> not a bug stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue46087] format library documentation error

Arthur Milchior added the comment: ipypthon3 does not print the loop content. python3 does. I only tested with ipython. I beg your pardon. I didn't know about this difference in behavior -- nosy: -eric.smith title: Zip library documentation error -> format library documentat

[issue46087] Zip library documentation error

Eric V. Smith added the comment: Good point, Serhiy. I also don't see how the proposed change is related to any zip documentation (which is in the title of this issue). I suggest closing this. -- nosy: +eric.smith ___ Python tracker

[issue46087] Zip library documentation error

Change by Eric V. Smith : -- versions: -Python 3.6, Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue46087] Zip library documentation error

Serhiy Storchaka added the comment: Since it is a REPL example, no print() is needed. In REPL any expression statement prints the repr of its result. For example: >>> for x in range(1, 5): ... f'{x}**2 = {x**2}' ... '1**2 = 1' '2**2 = 4' '3**2 = 9' '4**2 = 16' There are many such

[issue46087] Zip library documentation error

Change by Arthur Milchior : -- keywords: +patch pull_requests: +28345 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30126 ___ Python tracker ___

[issue46087] Zip library documentation error

onents: Documentation messages: 408624 nosy: Arthur-Milchior, docs@python priority: normal severity: normal status: open title: Zip library documentation error type: behavior versions: Python 3.10, Python 3.11, Python 3.6, Python 3.7, Python 3.8, Python 3.9

[issue42209] Incorrect line reported in syntax error

arian-f added the comment: There are still variations of this issue in python 3.10 - the line nr is correct - in script attached it's line 2 (the attached script is otherwise the same): f'{ 1_a }' resulting in: File "test.py", line 1 ( 1_a ) ^ SyntaxError: invalid

[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 ___

[issue45615] Missing test for type of error when printing traceback for non-exception

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

ERROR: No matching distribution found for PyQt5==5.15.4

, or if this message has been addressed to you in error, please immediately **notify**  the sender by reply email and delete this message and **its **attachments.  Any unauthorized use, dissemination, copying, or storage of this message or its attachments **is subject to criminal and civil liability

[issue32849] Fatal Python error: Py_Initialize: can't initialize sys standard streams

Change by Dong-hee Na : -- nosy: +corona10 nosy_count: 5.0 -> 6.0 pull_requests: +28310 pull_request: https://github.com/python/cpython/pull/30082 ___ Python tracker ___

[issue30225] EBADF error on x86 Tiger 3.x buildbot

Change by Dong-hee Na : -- nosy: +corona10 nosy_count: 4.0 -> 5.0 pull_requests: +28309 pull_request: https://github.com/python/cpython/pull/30082 ___ Python tracker ___

[issue46061] Journal execution gives fatal error in Python 3.10.1

Change by Eric V. Smith : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46061] Journal execution gives fatal error in Python 3.10.1

Christian Heimes added the comment: We cannot help you unless you show us your code and provide a reproducer. -- nosy: +christian.heimes ___ Python tracker ___

[issue46061] Journal execution gives fatal error in Python 3.10.1

Ajaya Sutar added the comment: It is a simply python script. Even if you will run a simply python script without any content that is giving error. Just for example journal.py if we run it is also giving error. In python 3.8, we are able to create // create sub-interpreter using

<    2   3   4   5   6   7   8   9   10   11   >