[issue44535] Cannot build in VS 2022

Change by Steve Dower : -- keywords: +patch pull_requests: +25528 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26962 ___ Python tracker ___

[issue41180] marshal load bypass code.__new__ audit event

Change by Steve Dower : -- pull_requests: +25527 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/26961 ___ Python tracker ___

[issue44490] PEP 604 Union (int | str) doesn't have __parameters__

Ken Jin added the comment: I don't think we need the types.GenericAlias(int | list[T], str) workaround. GenericAlias already has code for extracting __parameters__ and implementing __getitem__. Someone would need to refactor and reuse them for Union too. That should be enough to trick

[issue44537] Document PGO in devguide

Guido van Rossum added the comment: Hm, there is now also info on how to build in the end user documentation in Doc/using/configure.rst. I am actually confused by the intention of documenting information about *building* CPython in the same place where we document *using* Python (and

[issue44538] ast.Slice 3.9.6 documentation bug

New submission from Tim : Based off the ast 3.9.6 documentation (https://docs.python.org/3/library/ast.html), we would expect `Slice` to inherit from `expr`. However, looking at `ast.Slice.__mro__` produces the following output: `(, , , )`. It appears that instead of inheriting from

[issue44537] Document PGO in devguide

New submission from Guido van Rossum : The only docs for PGO seem to be in the toplevel README.rst. Sinec that is what's shown to all visitors to the GitHub repo, perhaps this information is not so useful there, and instead a section could be added to the devguide? (Ditto for LTO.) Note

[issue44523] weakref.proxy documentation might be outdated

miss-islington added the comment: New changeset 2df13e1211cf420bf6557df02e694bf1653a0ebe by Miss Islington (bot) in branch '3.10': bpo-44523: Remove the pass-through for hash() in weakref proxy objects (GH-26950)

[issue44523] weakref.proxy documentation might be outdated

Pablo Galindo Salgado added the comment: New changeset f790bc8084d3dfd723889740f9129ac8fcb2fa02 by Miss Islington (bot) in branch '3.9': bpo-44523: Remove the pass-through for hash() in weakref proxy objects (GH-26950) (GH-26960)

[issue44523] weakref.proxy documentation might be outdated

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

[issue44523] weakref.proxy documentation might be outdated

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

[issue44523] weakref.proxy documentation might be outdated

Pablo Galindo Salgado added the comment: New changeset e2fea101fd5517f33371b04432842b971021c3bf by Pablo Galindo in branch 'main': bpo-44523: Remove the pass-through for hash() in weakref proxy objects (GH-26950)

[issue44523] weakref.proxy documentation might be outdated

Change by miss-islington : -- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +25525 pull_request: https://github.com/python/cpython/pull/26959 ___ Python tracker

[issue44490] PEP 604 Union (int | str) doesn't have __parameters__

Jelle Zijlstra added the comment: I'd also be OK with returning a `types.GenericAlias(int | list[T], str)`, which might be simpler. It doesn't matter for static type checkers, and runtime type checkers can extract what they need anyway. -- ___

[issue44490] PEP 604 Union (int | str) doesn't have __parameters__

Guido van Rossum added the comment: So I guess to expand on Jelle's example, Alias[str] should return (int | list[str]), right? That makes sense since that's how Union works. -- ___ Python tracker

[issue44490] PEP 604 Union (int | str) doesn't have __parameters__

Jelle Zijlstra added the comment: Mypy is definitely not going to support direct access to `__parameters__`; what Guido is referring to is whether usage of types.Union that would require `__parameters__` at runtime is accepted by mypy. For example, this: from typing import TypeVar T =

[issue41180] marshal load bypass code.__new__ audit event

Steve Dower added the comment: I'm going to revert this and replace it with a marshal.loads (and dumps) event instead. The performance impact on loading .pyc files is too great, as it triggers the hook for each function. Without severely modifying importlib we can't bypass the call that's

[issue44490] PEP 604 Union (int | str) doesn't have __parameters__

Jack DeVries added the comment: mypy does not support __parameters__: (venv) ➜ cpython git:(main) cat repro.py from typing import TypeVar T = TypeVar('T') (int | list[T]).__parameters__ (venv) ➜ cpython git:(main) mypy --version mypy

[issue44490] PEP 604 Union (int | str) doesn't have __parameters__

Guido van Rossum added the comment: I intended for someone to write some test programs and report back here what mypy actually supports and what it doesn't. -- ___ Python tracker

[issue33025] urlencode produces bad output from ssl.CERT_NONE and friends that chokes decoders

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44530] Propagate qualname from the compiler unit to code objects for finer grained profiling data

Gabriele N Tornetta added the comment: Thanks for the feedback. I certainly appreciate all the concerns around this proposed change. @Mark.Shannon 1. This is the desired behaviour as profiling data should be attached to the actual code objects that correlate with the actual source content.

[issue43950] Include column offsets for bytecode instructions

Change by Ammar Askar : -- nosy: +ammar2 nosy_count: 8.0 -> 9.0 pull_requests: +25524 pull_request: https://github.com/python/cpython/pull/26958 ___ Python tracker ___

[issue6407] multiprocessing Pool should allow custom task queue

Irit Katriel added the comment: It should be possible to do this now through the context, but it's not documented: >>> import multiprocessing as mp >>> ctx = mp.get_context() >>> ctx.SimpleQueue > >>> ctx.SimpleQueue = list >>> ctx.SimpleQueue -- nosy: +iritkatriel

[issue38062] Clarify that atexit.unregister matches by equality, not identity

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

[issue38062] Clarify that atexit.unregister matches by equality, not identity

Irit Katriel added the comment: New changeset 02859df10591789c72eb185a4f7dd9cc1ea8dcbb by Miss Islington (bot) in branch '3.9': bpo-38062: [doc] clarify that atexit uses equality comparisons internally. (GH-26935) (GH-26957)

[issue38062] Clarify that atexit.unregister matches by equality, not identity

Irit Katriel added the comment: New changeset 08aa26e4355da6f916da0c97d00774800ee0fc46 by Miss Islington (bot) in branch '3.10': bpo-38062: [doc] clarify that atexit uses equality comparisons internally. (GH-26935) (GH-26956)

[issue38062] Clarify that atexit.unregister matches by equality, not identity

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

[issue38062] Clarify that atexit.unregister matches by equality, not identity

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

[issue38062] Clarify that atexit.unregister matches by equality, not identity

Irit Katriel added the comment: New changeset 12803c59d54ff1a45a5b08cef82652ef199b3b07 by Jack DeVries in branch 'main': bpo-38062: [doc] clarify that atexit uses equality comparisons internally. (GH-26935) https://github.com/python/cpython/commit/12803c59d54ff1a45a5b08cef82652ef199b3b07

[issue40522] [subinterpreters] Get the current Python interpreter state from Thread Local Storage (autoTSSkey)

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15751] [subinterpreters] Make the PyGILState API compatible with subinterpreters

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40601] [C API] Hide static types from the limited C API

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39511] [subinterpreters] Per-interpreter singletons (None, True, False, etc.)

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40077] Convert static types to heap types: use PyType_FromSpec()

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44523] weakref.proxy documentation might be outdated

Pablo Galindo Salgado added the comment: Just also to be clear on my original message, reverting it to a previous behaviour would disallow some patterns that could be useful: >>> class A: ... ... ... >>> a = A() >>> d = {a: None} >>> weakref.proxy(a) in d True But I agree is better to

[issue1635741] Py_Finalize() doesn't clear all Python objects at exit

Change by h-vetinari : -- nosy: +h-vetinari ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44523] weakref.proxy documentation might be outdated

Pablo Galindo Salgado added the comment: Thanks Neil for your input. I am indeed reverting that change to its previous behaviour. -- ___ Python tracker ___

[issue44523] weakref.proxy documentation might be outdated

Neil Schemenauer added the comment: It seems to me the old behaviour (don't forward hash) was done for good reasons. If the referent might go away, it is not valid to use it as a dict key since the hash and eq result changes. If it can't go away, what reason is there to use a weakref and

[issue43950] Include column offsets for bytecode instructions

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

[issue43945] [Enum] standardize format() behavior

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue30717] Add unicode grapheme cluster break algorithm

Change by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16801] Preserve original representation for integers / floats in docstrings

Mark Dickinson added the comment: FWIW, the relevant change seems to be this one: https://github.com/sphinx-doc/sphinx/pull/7155 -- ___ Python tracker ___

[issue16801] Preserve original representation for integers / floats in docstrings

Mark Dickinson added the comment: I suspect the difference is due to a change in the way that Sphinx handles the py:method directive: the rst source for `pathlib.Path.touch` hasn't changed between 3.9 and 3.10, but the 3.9 docs are built with Sphinx 2.4.4, while the 3.10 docs are built with

[issue44536] wrong output of np.lcm.reduce(*awg)

Mark Dickinson added the comment: It looks as though you're reporting an issue with NumPy; this tracker is for the Python core language, which doesn't include NumPy. For NumPy bugs, use the NumPy bug tracker at https://github.com/numpy/numpy/issues. (Though I don't think this _is_ a NumPy

[issue24339] iso6937 encoding missing

Maarten Derickx added the comment: Hi Marc-Andre Lemburg, Thanks for your responses and guidance. At least your pointers to charmap_encode and charmap_decode helped, since it shows at least what the general idea is on how to deal with these types of encodings. In the mean time I did

[issue43950] Include column offsets for bytecode instructions

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

[issue44536] wrong output of np.lcm.reduce(*awg)

New submission from 申泷轩 <751630...@qq.com>: np.lcm.reduce([1,2,3,100]) Out[125]: 300 np.lcm.reduce([1,2,3,100,101]) Out[126]: 30300 np.lcm.reduce([1,2,3,100,101,99019]) Out[127]: -1294691596 30300*99019 Out[128]: 3000275700 -- assignee: docs@python components: Documentation files: a

[issue44531] Add _PyType_AllocNoTrack() function: allocate without tracking in the GC

STINNER Victor added the comment: For the background of this issue, please see bpo-38392: https://bugs.python.org/issue38392#msg354074 -- ___ Python tracker ___

[issue43832] asyncio + multiprocessing = core dump in sem_trywait

Kunal added the comment: Oh, it looks like it's because the context for the Event doesn't match when created this way (the default context on linux is fork). The problem goes away if the Event instance is created from the spawn context -- specifically, patching dump_core.py ``` @@ -22,14

[issue44524] __name__ attribute in typing module

Guido van Rossum added the comment: It sounds reasonable to add the __name__ attribute. Since these objects aren't really types, the default mechanism for constructing a type doesn't give them this. Are there other attributes that are missing? We should probably add those too. --

[issue44531] Add _PyType_AllocNoTrack() function: allocate without tracking in the GC

Pablo Galindo Salgado added the comment: > About subclasses, I'm not sure if it's safe to call the traverse function if > a subclass overrides it and visits its own member which are not in the > built-in type (like dict or tuple). Technically the traverse should only call visit on the

[issue24339] iso6937 encoding missing

Marc-Andre Lemburg added the comment: Right, the charmap codec was built with the Unicode Consortium mappings in mind. However, you may have some luck decoding the two byte chars in ISO 6937 using combining code points in Unicode. With some extra post processing you could also normalize the

[issue44531] Add _PyType_AllocNoTrack() function: allocate without tracking in the GC

STINNER Victor added the comment: > How is that going to help third party extensions and subclasses? It doesn't solve bpo-40142 issue for third party extensions. About subclasses, I'm not sure if it's safe to call the traverse function if a subclass overrides it and visits its own member

[issue44531] Add _PyType_AllocNoTrack() function: allocate without tracking in the GC

STINNER Victor added the comment: New changeset 823460daa9fab3d0cf00ec553d1e35635ef73d40 by Victor Stinner in branch 'main': bpo-44531: Fix type_repr() if tp_name is NULL (GH-26948) https://github.com/python/cpython/commit/823460daa9fab3d0cf00ec553d1e35635ef73d40 --

[issue43215] Document Happy Eyeballs arguments of asyncio.open_connection

Change by Illia Volochii : -- versions: +Python 3.11 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43832] asyncio + multiprocessing = core dump in sem_trywait

Kunal added the comment: I was trying to reproduce the problem and can get the core dump to happen with a smaller program as well -- it doesn't seem related to asyncio specifically but seems to be a bug with multiprocessing.Event (or probably the primitives inside it). ``` #!/usr/bin/env

[issue43625] CSV has_headers heuristic could be improved

Andrei Kulakov added the comment: Skip: I've updated the PR Expanded the docs a bit, I think they give a good rough idea of the logic but I feel like they can probably be improved more, let me know what you think! I spent some time thinking about it but found it tricky! :) --

[issue44526] Doc typo in "What’s New In Python 3.10" (x/y-axis)

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

[issue44531] Add _PyType_AllocNoTrack() function: allocate without tracking in the GC

Pablo Galindo Salgado added the comment: > Anyway, I propose to add a new _PyType_AllocNoTrack() function which > allocates memory without tracking the newly allocated object directly in the > GC. How is that going to help third party extensions and subclasses? -- nosy: +pablogsal

[issue42588] Improvements to graphlib.TopologicalSorter.static_order() documentation

Pablo Galindo Salgado added the comment: New changeset 3ba65cdcefcec7866be482138a5ea8aafbd07e59 by Miss Islington (bot) in branch '3.9': bpo-42588: Update the docs for the TopologicalSorter.static_order() method (GH-26834) (GH-26952)

[issue44530] Propagate qualname from the compiler unit to code objects for finer grained profiling data

Pablo Galindo Salgado added the comment: This also has the side effect of making marshalled code objects bigger, and we keep adding to this in 3.11 with the new exception table and soon with PEP 657. Given that a lot of people are concerned about this and that this change only affects a

[issue44524] __name__ attribute in typing module

Ken Jin added the comment: Lars, yes you're right that __name__ is documented in datamodel, sorry I wasn't clear in my original message. What I meant was that specifically for the typing module, it's not exposed anywhere in its docs https://docs.python.org/3/library/typing.html. > If I were

[issue16801] Preserve original representation for integers / floats in docstrings

Éric Araujo added the comment: Please open a ticket! This one is about docstrings and pydoc; docs.python.org is built from rst docs with sphinx. -- versions: +Python 3.11 -Python 3.4 ___ Python tracker

[issue16842] Allow to override a function signature for pydoc with a docstring

Éric Araujo added the comment: This proposal pre-dates signature objects; I wonder if they can be used to handle the use cases here. -- versions: -Python 3.4 ___ Python tracker

[issue44533] Where are the log file(s)

Éric Araujo added the comment: The python interpreter does not create log files by itself, it would be the specific command or script that you ran that does that and prints the message you show. -- nosy: +eric.araujo resolution: -> third party status: open -> pending type: behavior

[issue44524] __name__ attribute in typing module

Lars van Gemerden added the comment: I was not aware the __name__ attribute is an implementation detail. It is described in the docs: https://docs.python.org/3/reference/datamodel.html. I have been using it since python 2.7, for example for logging. The function “split_module_names” is just

[issue24339] iso6937 encoding missing

Maarten Derickx added the comment: The route via gencodec or more generally via charmap_encode and charmap_decode seems to be one that is not possible without some low level CPython code adjustments. The reason for this is that charmap_encode and charmap_decode only seem to support mappings

[issue44535] Cannot build in VS 2022

New submission from Steve Dower : The project files require an additional check in PCbuild/python.props to select the right toolset for VisualStudioVersion=17.0. Without this, everything will refuse to build. The toolset is still v142, so there should be not compatibility issues. The

[issue43625] CSV has_headers heuristic could be improved

Skip Montanaro added the comment: Here's a NEWS entry. -- Added file: https://bugs.python.org/file50132/2021-06-29-07-27-08.bpo-43625.ZlAxhp.rst ___ Python tracker ___

[issue16801] Preserve original representation for integers / floats in docstrings

Scott Stevens added the comment: I'm now seeing docs.python.org has regressed. For 3.9, calls present their defaults in octal, in 3.10 (beta), they're presented in decimal. https://docs.python.org/3.10/library/pathlib.html#pathlib.Path.touch

[issue43625] CSV has_headers heuristic could be improved

Skip Montanaro added the comment: Here is a change to the has_header documentation and an extra test case documenting the behavior when the sample contains strings. I'm not sure about the wording of the doc change, perhaps you can tweak it? Seems kind of clumsy to me. If it seems okay to

[issue44534] unittest.mock.Mock.unsafe doc is garbled

New submission from Roy Smith : At https://docs.python.org/3.9/library/unittest.mock.html#unittest.mock.Mock, it says: unsafe: By default if any attribute starts with assert or assret will raise an AttributeError. That's not an English sentence. I think what was intended was, "By default

[issue44526] Doc typo in "What’s New In Python 3.10" (x/y-axis)

Joannah Nanjekye added the comment: I mean intended wording -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44526] Doc typo in "What’s New In Python 3.10" (x/y-axis)

Joannah Nanjekye added the comment: Since this is the intended behavior, we can just close the issue. -- nosy: +nanjekyejoannah ___ Python tracker ___

[issue43625] CSV has_headers heuristic could be improved

Skip Montanaro added the comment: I retract my comment about fixed length strings in the non-numeric case. There are clearly test cases (which I probably wrote, considering the values) where the sample as a header but the values are of varying length. Misread of the code on my part. I have

[issue44524] __name__ attribute in typing module

Ken Jin added the comment: > Is this intentional? It seems a little inconsistent. The `__name__` attribute is for internal use only. It's subject to change every release along with other implementation details. Sorry, I don't really understand what this issue is requesting. Do you want to

[issue43625] CSV has_headers heuristic could be improved

Skip Montanaro added the comment: Thanks @andrei.avk. You are right, only the complex test is required. I suppose it's okay to commit this, but reviewing the full code of the has_header method leaves me thinking this is just putting lipstick on a pig. If I read the code correctly, there are

[issue42588] Improvements to graphlib.TopologicalSorter.static_order() documentation

miss-islington added the comment: New changeset d9fc4c3deb617beb1d0bbfdb4efc905a4192ff0a by Miss Islington (bot) in branch '3.10': bpo-42588: Update the docs for the TopologicalSorter.static_order() method (GH-26834)

[issue42588] Improvements to graphlib.TopologicalSorter.static_order() documentation

Pablo Galindo Salgado added the comment: Thanks, Ran and Andrei for your contributions! :) -- nosy: -miss-islington resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue42588] Improvements to graphlib.TopologicalSorter.static_order() documentation

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

[issue42588] Improvements to graphlib.TopologicalSorter.static_order() documentation

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

[issue42588] Improvements to graphlib.TopologicalSorter.static_order() documentation

Pablo Galindo Salgado added the comment: New changeset 0d7f7975d55eff7e3dfcebd14e765fc6cd7d3e40 by andrei kulakov in branch 'main': bpo-42588: Update the docs for the TopologicalSorter.static_order() method (GH-26834)

[issue44523] weakref.proxy documentation might be outdated

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

[issue44529] Using typing.Union in isinstance checks

Change by Eric V. Smith : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44490] PEP 604 Union (int | str) doesn't have __parameters__

Ken Jin added the comment: Yurii, thanks for the offer. We only need to implement __getitem__ if union supports TypeVars. Which means __parameters__ need to be implemented too (or at least a private internal implementation of it). I interpreted Guido's message above as to wait and see if

[issue44490] PEP 604 Union (int | str) doesn't have __parameters__

Yurii Karabas <1998uri...@gmail.com> added the comment: Should `__getitem__` be implemented for `types.Union`? I can implement it if no one is working on it. P.S. mypy currently does not support it: ``` Value of type "types.Union" is not indexable ``` -- nosy: +uriyyo

[issue44471] Raise TypeError in ExitStack.enter_context() for bad argument

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

[issue12022] AttributeError should report the same details when raised by lookup_special() as when raised in the REPL

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

[issue44471] Raise TypeError in ExitStack.enter_context() for bad argument

Serhiy Storchaka added the comment: New changeset 6cb145d23f5cf69b6d7414877d142747cd3d134c by Serhiy Storchaka in branch 'main': bpo-44471: Change error type for bad objects in ExitStack.enter_context() (GH-26820)

[issue12022] AttributeError should report the same details when raised by lookup_special() as when raised in the REPL

Serhiy Storchaka added the comment: New changeset 20a88004bae8ead66a205a125e1fe979376fc3ea by Serhiy Storchaka in branch 'main': bpo-12022: Change error type for bad objects in "with" and "async with" (GH-26809)

[issue44530] Propagate qualname from the compiler unit to code objects for finer grained profiling data

Mark Shannon added the comment: I think this is a worthwhile improvement. A few comments on this issue and your PR. 1. We already have qualified names on functions and generators and those can be modified by @decorators. In those cases, the code object and the function would disagree. Code

[issue44440] logging does not work as documented (setLevel)

Vinay Sajip added the comment: As Henk-Jaap points out, this is not a bug. You can't take a single sentence or even paragraph without considering the whole picture. In particular, this section https://docs.python.org/3/howto/logging.html#what-happens-if-no-configuration-is-provided

[issue44533] Where are the log file(s)

New submission from tygrus : The Python app shows errors and says "Check the logs for full command output." But where are the logs? And how to understand the data in the logs? -- messages: 396704 nosy: tygrus priority: normal severity: normal status: open title: Where are the log

[issue44532] multi subinterpreters use _PyStructSequence_InitType failed.

Change by junyixie : -- keywords: +patch pull_requests: +25516 stage: -> patch review pull_request: https://github.com/python/cpython/pull/26949 ___ Python tracker ___

[issue44532] multi subinterpreters use _PyStructSequence_InitType failed.

New submission from junyixie : In _PyStructSequence_InitType, it will check type is initialized. but when we have multi subinterpreters, type may be initialized expected. when type already been initialized, should return 0 rather than throw exception. ```c /* PyTypeObject has already been

[issue44526] Doc typo in "What’s New In Python 3.10" (x/y-axis)

Brandt Bucher added the comment: I don’t think this is a typo. When x is 0, the point resides somewhere upon the vertical y axis. When y is 0, the point resides somewhere upon the horizontal x axis. Try plotting the points (0, 1) and (1, 0), for example. --

[issue44526] Doc typo in "What’s New In Python 3.10" (x/y-axis)

Change by Brandt Bucher : -- nosy: +brandtbucher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: