[issue41035] zipfile.Path does not work properly with zip archives where paths start with /

sorrow added the comment: >It seems you may have discovered a use-case that violates that expectation, a >case where `/a.txt` is identical to `a.txt`. The thing is: it's not. >Can you tell me more about your use-case and why zipp.Path/zipfile.Path should >support it? I received a .zip

[issue41047] argparse: misbehavior when combining positionals and choices

Change by paul j3 : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue41047] argparse: misbehavior when combining positionals and choices

paul j3 added the comment: It is an old unresolved issue (which resurfaced a few months ago) https://bugs.python.org/issue9625 argparse: Problem with defaults for variable nargs when using choices -- resolution: -> duplicate ___ Python tracker

[issue41047] argparse: misbehavior when combining positionals and choices

paul j3 added the comment: The error is raised in ._get_values with this section: # when nargs='*' on a positional, if there were no command-line # args, use the default if it is anything other than None elif (not arg_strings and action.nargs == ZERO_OR_MORE and

[issue40939] Remove the old parser

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

[issue41060] `with a as b` segfault in new peg parser

miss-islington added the comment: New changeset 71bb921829c33c30b2e111e18948df8c2b6731e4 by Lysandros Nikolaou in branch '3.9': [3.9] bpo-41060: Avoid SEGFAULT when calling GET_INVALID_TARGET in the grammar (GH-21020) (GH-21024)

[issue41060] `with a as b` segfault in new peg parser

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

[issue41060] `with a as b` segfault in new peg parser

Change by Lysandros Nikolaou : -- pull_requests: +20196 pull_request: https://github.com/python/cpython/pull/21024 ___ Python tracker ___

[issue41060] `with a as b` segfault in new peg parser

Pablo Galindo Salgado added the comment: New changeset 6c4e0bd974f2895d42b63d9d004587e74b286c88 by Lysandros Nikolaou in branch 'master': bpo-41060: Avoid SEGFAULT when calling GET_INVALID_TARGET in the grammar (GH-21020)

[issue40939] Remove the old parser

Pablo Galindo Salgado added the comment: New changeset d301d9473e9a9b78d6e6678e9fe5ef66d46084e1 by Lysandros Nikolaou in branch '3.9': [3.9] bpo-40939: Deprecate the PyParser_SimpleParse* functions (GH-21012) https://github.com/python/cpython/commit/d301d9473e9a9b78d6e6678e9fe5ef66d46084e1

[issue39960] Using typename.__setattr__ in extension type with Py_TPFLAGS_HEAPTYPE is broken (hackcheck too eager?)

Guido van Rossum added the comment: See also test_carloverre() in test_descr.py. I don't recall exactly what this was about, but that test is definitely relevant. -- ___ Python tracker

[issue39783] Optimize construction of Path from other Paths by just returning the same object?

Change by Rémi Lapeyre : -- versions: +Python 3.10 -Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35232] Add `module`/`qualname` arguments to make_dataclass for picklability

Change by Rémi Lapeyre : -- versions: +Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35232] Add `module`/`qualname` arguments to make_dataclass for picklability

Change by Rémi Lapeyre : -- versions: +Python 3.10 -Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33927] Allow json.tool to have identical infile and outfile

Change by Rémi Lapeyre : -- components: +Library (Lib) versions: +Python 3.10, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___

[issue35975] Put back the ability to parse files where async/await aren't keywords

Change by Guido van Rossum : -- pull_requests: +20195 pull_request: https://github.com/python/cpython/pull/21023 ___ Python tracker ___

[issue35975] Put back the ability to parse files where async/await aren't keywords

Change by Guido van Rossum : -- pull_requests: +20194 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/21022 ___ Python tracker ___

[issue35975] Put back the ability to parse files where async/await aren't keywords

Guido van Rossum added the comment: Hm, the backports have to be done manually, since the 3.8 parser and the 3.10 parser don't overlap, and 3.9 has both versions... -- ___ Python tracker

[issue35975] Put back the ability to parse files where async/await aren't keywords

Change by Guido van Rossum : -- status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35975] Put back the ability to parse files where async/await aren't keywords

Guido van Rossum added the comment: I'm fixing it -- can you verify? I have no easy way to test this. DO you think we should also add a note to the docs that this was broken in 3.8.0-3? -- ___ Python tracker

[issue35975] Put back the ability to parse files where async/await aren't keywords

Change by Guido van Rossum : -- pull_requests: +20193 pull_request: https://github.com/python/cpython/pull/21021 ___ Python tracker ___

[issue40965] Segfault when importing unittest module via C API

Steve Stagg added the comment: Fix was here: a75e730075 bpo-40294: Fix _asyncio when module is loaded/unloaded multiple times (GH-19542) Backport commit was: 6b0ca0aeab04d7b7b54086248ca9d5e70f770f2f >From my end, the issue seems to be resovled on tag v.3.8.3 --

[issue40965] Segfault when importing unittest module via C API

Steve Stagg added the comment: I was able to reproduce, follows is the raw LLDB output, I don't think this fails on master, will try some bisecting: * thread #1, name = 'runtest', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) frame #0: 0x77079ae7

[issue41060] `with a as b` segfault in new peg parser

Lysandros Nikolaou added the comment: Thanks for the report, Steve. I've now opened a PR that should fix this. -- ___ Python tracker ___

[issue41060] `with a as b` segfault in new peg parser

Change by Lysandros Nikolaou : -- assignee: -> lys.nikolaou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41060] `with a as b` segfault in new peg parser

Change by Lysandros Nikolaou : -- keywords: +patch pull_requests: +20192 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21020 ___ Python tracker

[issue40965] Segfault when importing unittest module via C API

Steve Stagg added the comment: This appears to have been introduced in 13915a3100 bpo-36356: Fix memory leak in _asynciomodule.c (GH-16598). Cannot reproduce on master -- ___ Python tracker

[issue41060] `with a as b` segfault in new peg parser

Lysandros Nikolaou added the comment: On it. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41060] `with a as b` segfault in new peg parser

Change by Guido van Rossum : -- nosy: +gvanrossum, pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41053] open() fails to read app exec links

Kagami Sascha Rosylight added the comment: It seems libuv and pwsh decided to detect and read them just as symlinks: https://github.com/libuv/libuv/pull/2812 https://github.com/PowerShell/PowerShell/pull/10331 Could Python do the same? -- ___

[issue41060] `with a as b` segfault in new peg parser

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

[issue41056] minor NULL pointer and sign issues reported by Coverity

miss-islington added the comment: New changeset 3ccb96c9782480e5ce646a4a130569fb92f2965d by Gregory P. Smith in branch 'master': bpo-41056: Use the fildes converter for fd to please Coverity. (GH-21011) https://github.com/python/cpython/commit/3ccb96c9782480e5ce646a4a130569fb92f2965d

[issue41005] Permission denied: 'xdg-settings' when executing 'jupyter notebook' from command line

Rémi Lapeyre added the comment: Can you give more information about your issue here. This part of the code was written like this on purpose as the comment says: # OS X can use below Unix support (but we prefer using the OS X # specific stuff) We have to be sure that there

[issue41060] `with a as b` segfault in new peg parser

Steve Stagg added the comment: Appears to have been introduced by: bpo-40334: Produce better error messages on invalid targets (GH-20106) 01ece63d42b830df106948db0aefa6c1ba24416a -- ___ Python tracker

[issue41060] `with a as b` segfault in new peg parser

New submission from Steve Stagg : Hi Fuzzing found the following: $ ./python/bin/python3 Python 3.10.0a0 (heads/master:eb0d5c38de, Jun 20 2020, 21:35:36) [Clang 10.0.0 ] on linux Type "help", "copyright", "credits" or "license" for more information. >>> with a as b fish:

[issue41053] open() fails to read app exec links

Eryk Sun added the comment: By design, appexec links (i.e. app execution aliases) cannot be followed automatically. There is no handler for them in the kernel. WinAPI CreateFileW fails with ERROR_CANT_ACCESS_FILE (1920), and the underlying NT status value is

[issue41059] Large number of Coverity reports for parser.c

Guido van Rossum added the comment: Good catch! Are all the coverity complaints about this kind of code? if (_res == NULL && PyErr_Occurred()) { ... } (Mostly for Pablo and Lysandros:) This comes from emit_action(). It is preceded by a line of the form _res = ; Most of the time the

[issue41035] zipfile.Path does not work properly with zip archives where paths start with /

Jason R. Coombs added the comment: Thanks sorrow for filing a report. I primarily developed this functionality. As I did, I found the 'zip' format to be under-specified, so I used real-world examples as models to infer a spec. It seems you may have discovered a use-case that violates that

[issue40065] py39: remove deprecation note for xml.etree.cElementTree

Ido Michael added the comment: Thanks Tal. Yes, I also got the impression we want to clean this, sorry Christian. Please let me know how to follow up on this. -- ___ Python tracker

[issue19670] SimpleCookie Generates Non-RFC6265-Compliant Cookies

Ido Michael added the comment: Opened a PR: GH-21017 The documentation in the internal functions was helpful. Should I also add it once decided on the format in here? Doc/library/http.cookies.rst:55 -- ___ Python tracker

[issue19670] SimpleCookie Generates Non-RFC6265-Compliant Cookies

Change by Ido Michael : -- keywords: +patch pull_requests: +20191 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21017 ___ Python tracker ___

[issue40939] Remove the old parser

Change by Lysandros Nikolaou : -- pull_requests: +20190 pull_request: https://github.com/python/cpython/pull/21016 ___ Python tracker ___

[issue41056] minor NULL pointer and sign issues reported by Coverity

Christian Heimes added the comment: I figured out how to run coverity scan builds again. It turned out the tool chain doesn't like GCC 10. clang 10 works, though. By the way I'm using login with Github. -- nosy: +christian.heimes ___ Python

[issue41059] Large number of Coverity reports for parser.c

Change by Paul Ganssle : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41056] minor NULL pointer and sign issues reported by Coverity

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

[issue41056] minor NULL pointer and sign issues reported by Coverity

miss-islington added the comment: New changeset eb0d5c38de7f970d8cd8524f4163d831c7720f51 by Gregory P. Smith in branch 'master': bpo-41056: Fix a NULL pointer dereference on MemoryError within the ssl module. (GH-21009)

[issue41056] minor NULL pointer and sign issues reported by Coverity

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

[issue41056] minor NULL pointer and sign issues reported by Coverity

Change by Gregory P. Smith : -- pull_requests: +20187 pull_request: https://github.com/python/cpython/pull/21013 ___ Python tracker ___

[issue41059] Large number of Coverity reports for parser.c

Change by Gregory P. Smith : -- components: +Interpreter Core ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41059] Large number of Coverity reports for parser.c

New submission from Gregory P. Smith : Here's an example: *** CID 1464688: Control flow issues (DEADCODE) /Parser/parser.c: 24243 in _tmp_147_rule() 24237 && 24238 (z = disjunction_rule(p)) // disjunction 24239 ) 24240 { 24241

[issue41056] minor NULL pointer and sign issues reported by Coverity

Gregory P. Smith added the comment: those were the three in the email (20 of 106), i need to figure out how to login to coverity again to see the rest. -- ___ Python tracker

[issue40939] Remove the old parser

Change by Lysandros Nikolaou : -- pull_requests: +20186 pull_request: https://github.com/python/cpython/pull/21012 ___ Python tracker ___

[issue41056] minor NULL pointer and sign issues reported by Coverity

Change by Gregory P. Smith : -- pull_requests: +20185 pull_request: https://github.com/python/cpython/pull/21011 ___ Python tracker ___

[issue41057] Division error

Steven D'Aprano added the comment: Further to what Mark said, I'm afraid you are mistaken when you thought that "the result was correct" on R. R cheats by not printing the full precision of the number, they just stop printing digits, giving a false impression of accuracy. You can prove this

[issue40939] Remove the old parser

Pablo Galindo Salgado added the comment: New changeset 314858e2763e76e77029ea0b691d749c32939087 by Lysandros Nikolaou in branch 'master': bpo-40939: Remove the old parser (Part 2) (GH-21005) https://github.com/python/cpython/commit/314858e2763e76e77029ea0b691d749c32939087 --

[issue41058] pdb reads source files using the locale encoding

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

[issue41035] zipfile.Path does not work properly with zip archives where paths start with /

Change by Brett Cannon : -- nosy: +alanmcintyre, serhiy.storchaka, twouters ___ Python tracker ___ ___ Python-bugs-list mailing

[issue41057] Division error

Mark Dickinson added the comment: This isn't a bug in Python; it's a consequence of the what-you-see-is-not-what-you-get nature of binary floating-point. The behaviour is explained in the tutorial, here: https://docs.python.org/3/tutorial/floatingpoint.html -- nosy: +mark.dickinson

[issue41035] zipfile.Path does not work properly with zip archives where paths start with /

Change by Brett Cannon : -- nosy: +jaraco ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41044] Pegen: double trailing comma on optional+sequence rules at python generator

miss-islington added the comment: New changeset 98621817504add1e985e2526614921bbe0d24fb6 by Miss Islington (bot) in branch '3.9': bpo-41044: Generate valid PEG python parsers for opt+seq rules (GH-20995) https://github.com/python/cpython/commit/98621817504add1e985e2526614921bbe0d24fb6

[issue41058] pdb reads source files using the locale encoding

New submission from Serhiy Storchaka : find_function() in pdb uses the locale encoding for reading source files. It should use the encoding specified by the coding cookie or UTF-8 if it is not specified. -- components: Library (Lib) messages: 371950 nosy: serhiy.storchaka priority:

[issue41044] Pegen: double trailing comma on optional+sequence rules at python generator

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

[issue35975] Put back the ability to parse files where async/await aren't keywords

Stefan Behnel added the comment: I wasn't sure which is better – solve it or leave it. But it seems a) easy to adapt to on user side, and b) solvable in CPython in a way that allows code that wants to adapt to work across 3.8.x versions. Only code that does not get adapted would risk failure

[issue41056] minor NULL pointer and sign issues reported by Coverity

Change by Gregory P. Smith : -- pull_requests: +20183 pull_request: https://github.com/python/cpython/pull/21009 ___ Python tracker ___

[issue41057] Division error

New submission from Fenn Ehk : When performing some basic calculations, the result is wrong. 0.4 + 8/100 Out[43]: 0.48004 0.3 + 8/100 Out[44]: 0.38 I thought it could be processor related and tried the same operation with R, but the result was correct. So I tried it on some

[issue41044] Pegen: double trailing comma on optional+sequence rules at python generator

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

[issue41044] Pegen: double trailing comma on optional+sequence rules at python generator

Pablo Galindo Salgado added the comment: New changeset 55460ee6dc9a4f16bd68d6b6be3a8398c7d4a596 by Batuhan Taskaya in branch 'master': bpo-41044: Generate valid PEG python parsers for opt+seq rules (GH-20995) https://github.com/python/cpython/commit/55460ee6dc9a4f16bd68d6b6be3a8398c7d4a596

[issue41056] minor NULL pointer and sign issues reported by Coverity

Change by Gregory P. Smith : -- keywords: +patch pull_requests: +20181 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/21007 ___ Python tracker

[issue41056] minor NULL pointer and sign issues reported by Coverity

New submission from Gregory P. Smith : *** CID 1464693: Null pointer dereferences (REVERSE_INULL) /Modules/_zoneinfo.c: 1625 in parse_abbr() 1619 ptr++; 1620 }

[issue40958] ASAN/UBSAN: heap-buffer-overflow in pegen.c

miss-islington added the comment: New changeset c9f83c173b0cc62d6fcdc363e9ab05f6664ff8f3 by Miss Islington (bot) in branch '3.9': bpo-40958: Avoid 'possible loss of data' warning on Windows (GH-20970) https://github.com/python/cpython/commit/c9f83c173b0cc62d6fcdc363e9ab05f6664ff8f3

[issue41055] Remove outdated tests for tp_print

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

[issue41055] Remove outdated tests for tp_print

New submission from Serhiy Storchaka : There are ancient tests for printing some basic types: str (actually a mix of Python 2 str and unicode), list, tuple, bool, set, deque, defaultdict. They are essentially tests for the tp_print slot. But since the tp_print slot is no longer used, they

[issue40939] Remove the old parser

Change by Lysandros Nikolaou : -- pull_requests: +20179 pull_request: https://github.com/python/cpython/pull/21005 ___ Python tracker ___

[issue35975] Put back the ability to parse files where async/await aren't keywords

Guido van Rossum added the comment: But it's a bug, right? The intention for sure is that the cf_feature_version field is only used when the PyCF_ONLY_AST flags is set in cf_flags, per the docs you cite as [3]. Why wouldn't it be possible to fix that? -- status: closed -> open

[issue41054] Simplify resource compilation on Windows

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

[issue40939] Remove the old parser

Guido van Rossum added the comment: You can delete symbol.py -- it has no use now that the old parser is gone. We should probably also update the regeneration targets in the Makefile. (At least review them.) -- ___ Python tracker

[issue41054] Simplify resource compilation on Windows

New submission from Nikita Nemkin : Every Windows project has a custom target (included from pyproject.props) that generates a header with definitions for resource files. Those definitions (PYTHON_DLL_NAME and FIELD3) can be passed directly to resource compiler. Another definition

[issue40939] Remove the old parser

Lysandros Nikolaou added the comment: I'm currently testing a commit that removes all these files on my fork, before I push it upstream. A question that I'm not 100% sure about is if we can already remove the symbol module. I guess it's okay since it got deprecated in 3.9 (bpo-40759) and

[issue41053] open() fails to read app exec links

New submission from Kagami Sascha Rosylight : After installing Python from Microsoft Store, this fails: ``` >>> open('C:\\Users\\Kagami\\AppData\\Local\\Microsoft\\WindowsApps\\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\\python.exe') Traceback (most recent call last): File "", line 1,

[issue35975] Put back the ability to parse files where async/await aren't keywords

Stefan Behnel added the comment: I was made aware [1] that the addition of the "cf_feature_version" field broke the backwards compatibility of the "PyRun_StringFlags()" function [2]. Unlike what the docs of "PyCompilerFlags" [3] suggest, the new field is not ignored there but must now be

[issue41052] Opt out serialization/deserialization for heap type

Change by Dong-hee Na : -- keywords: +patch pull_requests: +20177 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21002 ___ Python tracker ___

[issue41052] Opt out serialization/deserialization for heap type

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

[issue41052] Opt out serialization/deserialization for heap type

New submission from Dong-hee Na : See https://bugs.python.org/issue40077#msg371813 We noticed that heap type has different behavior about serialization/deserialization. Basically it can occur the regression issues. Two things needed. 1. opt out serialization/deserialization for converted

[issue40958] ASAN/UBSAN: heap-buffer-overflow in pegen.c

miss-islington added the comment: New changeset 861efc6e8fe7f030b1e193989b13287b31385939 by Lysandros Nikolaou in branch 'master': bpo-40958: Avoid 'possible loss of data' warning on Windows (GH-20970) https://github.com/python/cpython/commit/861efc6e8fe7f030b1e193989b13287b31385939

[issue40958] ASAN/UBSAN: heap-buffer-overflow in pegen.c

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

[issue41024] doc: Explicitly mention use of 'enum.Enum' as a valid container for 'choices' argument of 'argparse.ArgumentParser.add_argument'

miss-islington added the comment: New changeset 344c2a75c1c13de781962a3f80552e66a4c89024 by Vincent Férotin in branch 'master': bpo-41024: doc: Explicitly mention use of 'enum.Enum' as a valid container for '… (GH-20964)

[issue41051] Flush file after warning is written

Change by Manuel Jacob : -- keywords: +patch pull_requests: +20175 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21000 ___ Python tracker ___

[issue41039] Simplify python3.dll build

Change by Cheryl Sabella : -- nosy: +eryksun ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41051] Flush file after warning is written

New submission from Manuel Jacob : Calling warnings.warn() will write to a file, but not flush it. On Python 3.9+, it won’t usually be a problem because the file is most likely stderr, which is always line-buffered. However, on older Python versions or if a different file is used, the current

[issue41050] class multiprocessing.Value calls set_start_method

New submission from Kernel Plevitsky : I'm not sure if this is a bug or my carelessness. I cannot call set_start_method () if multiprocessing.Value() is declared in the class above than "if __name__ ==" __main__ "" The documentation for Value did not describe this. I have attached a code

[issue39960] Using typename.__setattr__ in extension type with Py_TPFLAGS_HEAPTYPE is broken (hackcheck too eager?)

Stefan Behnel added the comment: I ran into this, too. I agree that the "hackcheck" loop on heap types is probably wrong. https://github.com/python/cpython/blob/04fc4f2a46b2fd083639deb872c3a3037fdb47d6/Objects/typeobject.c#L5947-L5977 It was written at a time (Py2.3?) when (practically)

[issue41049] Document pointer comparison in PyObject_RichCompareBool()

tamuhey added the comment: > Hmm, I missed it. There is already a note in the link you provided I've read the comment before posting this issue. But I think there should be the following info: 1. example (float("nan")) 2. the result is inconsistent with PyObject_RichCompare --

[issue41049] Document pointer comparison in PyObject_RichCompareBool()

Raymond Hettinger added the comment: Hmm, I missed it. There is already a note in the link you provided" """Note If o1 and o2 are the same object, PyObject_RichCompareBool() will always return 1 for Py_EQ and 0 for Py_NE.""" -- resolution: -> out of date stage: patch review ->

[issue40939] Remove the old parser

Nikita Nemkin added the comment: Shouldn't the following files be deleted too? Include/bitset.h Include/grammar.h Include/graminit.h Include/parsetok.h Include/node.h Python/graminit.c Parser/node.c Also declarations: PyNode_Compile in Include/compile.h PyParser_SimpleParse* in

[issue41049] Document pointer comparison in PyObject_RichCompareBool()

Change by Raymond Hettinger : -- keywords: +patch pull_requests: +20174 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20999 ___ Python tracker

[issue41048] read_mime_types() should read the rule file using UTF-8, not the locale encoding

Change by Srinivas Reddy Thatiparthy(శ్రీనివాస్ రెడ్డి తాటిపర్తి) : -- keywords: +patch nosy: +thatiparthy nosy_count: 2.0 -> 3.0 pull_requests: +20173 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/20998

[issue41049] Document pointer comparison in PyObject_RichCompareBool()

Change by Raymond Hettinger : -- title: PyObject_RichCompareBool(nan, nan, eq) can be True -> Document pointer comparison in PyObject_RichCompareBool() ___ Python tracker ___

[issue41049] PyObject_RichCompareBool(nan, nan, eq) can be True

Raymond Hettinger added the comment: Thanks for the report. I'll add a note to the C API docs. -- assignee: -> rhettinger components: +Documentation -C API nosy: +rhettinger versions: -Python 3.5, Python 3.6, Python 3.7 ___ Python tracker

[issue41049] PyObject_RichCompareBool(nan, nan, eq) can be True

New submission from tamuhey : Applying PyObject_RichCompareBool to two `nan`s can be true if the two nans are same object, i.e. ``` a = float("nan") PyObject_RichCompareBool(a, a, Py_EQ) // True ``` I read the document

[issue13025] mimetypes should read the rule file using UTF-8, not the locale encoding

Serhiy Storchaka added the comment: However read_mime_types() still uses the locale encoding. See issue41048. -- nosy: +serhiy.storchaka ___ Python tracker ___

  1   2   >