[issue39722] decimal differs between pure Python and C implementations

Raymond Hettinger added the comment: Thanks for double checking. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue39722] decimal differs between pure Python and C implementations

Shantanu added the comment: Sounds good, thought I'd check! :-) Definitely looks annoying to remove from the Python version too. -- ___ Python tracker ___

[issue39722] decimal differs between pure Python and C implementations

Raymond Hettinger added the comment: I wouldn't worry about this. The context argument for the dunder methods isn't part of the public API. It is just an internal implementation detail that was necessary for the Python implementation but would make no sense at all for the C

[issue39721] Fix constness of members of tok_state struct.

Change by SilentGhost : -- nosy: +serhiy.storchaka, vstinner type: -> behavior versions: +Python 3.9 ___ Python tracker ___ ___

[issue35950] io.BufferedReader.writabe is False, but io.BufferedReader.truncate does not raise OSError

Change by Berker Peksag : -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39717] Fix exception causes in tarfile module

Ram Rachum added the comment: I'm also strongly against using `from None`. When I'm debugging, I'm like a man who got lost in the desert and is about to die of thirst. Any possible insight into what happened is like an oasis, even if there are just a few drops of water there. Also, some

[issue39723] io.open_code should accept PathLike objects

Change by Shantanu : -- keywords: +patch pull_requests: +17969 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18602 ___ Python tracker ___

[issue39704] Disable code coverage

Terry J. Reedy added the comment: The recently reinstated long 30+ line reports are useless nuisance for me. I delete them. A single line line to a report, without flagging, would be OK. -- nosy: +terry.reedy ___ Python tracker

[issue39723] io.open_code should accept PathLike objects

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39653] test_posix fails during make test

Terry J. Reedy added the comment: == ERROR: test_no_such_executable (test.test_posix.TestPosixSpawnP) -- Traceback (most recent call last): File

[issue39636] Can't change Treeview row color in Tkinter

Terry J. Reedy added the comment: What OS, what Python version, what tk version? For the latter, start IDLE and go to Help - About IDLE. -- nosy: +terry.reedy ___ Python tracker

[issue39717] Fix exception causes in tarfile module

Martin Panter added the comment: Please don’t use “from None” in library code. It hides exceptions raised by the calling application that would help debugging. E.g. -- nosy: +martin.panter ___ Python

[issue39723] io.open_code should accept PathLike objects

New submission from Shantanu : Currently io.open_code (added in Python 3.8) only accepts str arguments. As per PEP 519, it should probably also accept PathLike. It might be worth extending it to accept bytes as well, both for convenience and because documentation claims it should be

[issue39573] Make PyObject an opaque structure in the limited C API

Andy Lester added the comment: Just added a new PR to finish off the remaining places to use Py_IS_TYPE() https://github.com/python/cpython/pull/18601 -- ___ Python tracker

[issue39573] Make PyObject an opaque structure in the limited C API

Change by Andy Lester : -- pull_requests: +17968 pull_request: https://github.com/python/cpython/pull/18601 ___ Python tracker ___

[issue39722] decimal differs between pure Python and C implementations

Change by Karthikeyan Singaravelan : -- nosy: +facundobatista, mark.dickinson, rhettinger, skrah ___ Python tracker ___ ___

[issue39717] Fix exception causes in tarfile module

Ethan Furman added the comment: I know we are not in the habit of making large-scale changes to take advantage of new features and enhancements, but I think this may be one of the few exceptions to the rule, and it has to do with what the text between the two tracebacks means: -

[issue39722] decimal differs between pure Python and C implementations

New submission from Shantanu : The dunder methods on decimal.Decimal accept an extra context argument in the pure Python version which the C version does not (violating PEP 399). This came up in https://github.com/python/typeshed/pull/3633, where Sebastian provided the following summary of

[issue39679] functools: singledispatchmethod doesn't work with classmethod

Karthikeyan Singaravelan added the comment: Sorry, I had the part only to detect annotations attached. My part is something similar to yours except it stores the appropriate function in the registry itself instead of passing the arguments at __get__ . --

[issue39721] Fix constness of members of tok_state struct.

Change by Andy Lester : -- keywords: +patch pull_requests: +17967 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18600 ___ Python tracker ___

[issue39721] Fix constness of members of tok_state struct.

New submission from Andy Lester : The function PyTokenizer_FromUTF8 from Parser/tokenizer.c had a comment: /* XXX: constify members. */ This patch addresses that. In the tok_state struct: * end and start were non-const but could be made const * str and input were const but should

[issue39717] Fix exception causes in tarfile module

Raymond Hettinger added the comment: Ethan, would you make the call on this? My recommendation is to close because we usually don't churn APIs unless there is a demonstrable benefit. Also, the current code reflects the dominant practice in the standard library which is both faster and

[issue39720] Signature.bind TypeErrors could be more helpful

New submission from Frazer McLean : Signature.bind does not tell you if a missing argument is keyword-only for example. I created the following snippet to examine the differences: import inspect def run(f): try: f() except TypeError as exc:

[issue39707] Abstract property setter/deleter implementation not enforced.

Guido van Rossum added the comment: I agree with Raymond here. This is a job for a static type checker like mypy. Closing. -- resolution: -> rejected stage: -> resolved status: open -> closed ___ Python tracker

[issue39719] tempfile.SpooledTemporaryFile still has softspace property

Change by Shantanu : -- keywords: +patch pull_requests: +17966 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18599 ___ Python tracker ___

[issue39719] tempfile.SpooledTemporaryFile still has softspace property

New submission from Shantanu : The softspace attribute of files was removed in Python 3 (mentioned in https://raw.githubusercontent.com/python/cpython/master/Misc/HISTORY) However, tempfile.SpooledTemporaryFile still has a softspace property that attempts to return read the softspace

[issue39718] TYPE_IGNORE, COLONEQUAL missing from py38 changes in token docs

Change by Shantanu : -- keywords: +patch pull_requests: +17965 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18598 ___ Python tracker ___

[issue39718] TYPE_IGNORE, COLONEQUAL missing from py38 changes in token docs

New submission from Shantanu : Changed in version 3.8 section of https://docs.python.org/3/library/token.html should mention the addition of TYPE_IGNORE and COLONEQUAL -- assignee: docs@python components: Documentation messages: 362436 nosy: docs@python, hauntsaninja priority: normal

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Tim Peters added the comment: Thanks, Stefan! This turned out better than I expected ;-) I'm closing the report, under the likely assumption that nobody cares enough about obscure inelegancies in the Python version to bother. -- status: open -> closed

[issue39679] functools: singledispatchmethod doesn't work with classmethod

Viktor Roytman added the comment: I tried to apply this change but it didn't work, failing with this error $ ~/.pyenv/versions/3.8.1/bin/python -m bad_classmethod_as_documented Traceback (most recent call last): File "/home/viktor/.pyenv/versions/3.8.1/lib/python3.8/runpy.py",

[issue39715] Implement __repr__ methods for AST classes

Serhiy Storchaka added the comment: For more informative representation you can use ast.dump(). -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Change by Stefan Krah : -- stage: patch review -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Stefan Krah added the comment: libmpdec and the docs are done, the question remains what to do with decimal.py. It has the same behavior, but I don't think users are running decimal.py with very large precisions. Anyway, unassigning myself in case anyone else wants to work on a patch.

[issue39717] Fix exception causes in tarfile module

Ram Rachum added the comment: > What do you think it is necessary to switch from implicit chaining to > explicit chaining? I didn't say it's necessary, but I think it's beneficial. I find that message between exceptions useful when I'm debugging and I'd like to keep it accurate in as many

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Stefan Krah added the comment: New changeset d6965ff026f35498e554bc964ef2be8f4d80eb7f by Miss Islington (bot) in branch '3.8': bpo-39576: docs: set context for decimal arbitrary precision arithmetic (GH-18594) (#18597)

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Stefan Krah added the comment: New changeset 00e45877e33d32bb61aa13a2033e3bba370bda4d by Miss Islington (bot) in branch '3.7': bpo-39576: docs: set context for decimal arbitrary precision arithmetic (GH-18594) (#18596)

[issue39716] argparse.ArgumentParser does not raise on duplicated subparsers, even though it does on duplicated flags

Raymond Hettinger added the comment: Would you like to work-up a patch to fix this? -- ___ Python tracker ___ ___ Python-bugs-list

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

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

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

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

[issue39717] Fix exception causes in tarfile module

Raymond Hettinger added the comment: If this were new code, there would be a better case for the direct-cause style even though it is more cluttered and a bit slower. I'm only questioning whether it make sense to change it in already deployed code, possibly risking breakage. AFAICT,

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Stefan Krah added the comment: New changeset a025d4ca99fb4c652465368e0b4eb03cf4b316b9 by Stefan Krah in branch 'master': bpo-39576: docs: set context for decimal arbitrary precision arithmetic (#18594) https://github.com/python/cpython/commit/a025d4ca99fb4c652465368e0b4eb03cf4b316b9

[issue39717] Fix exception causes in tarfile module

New submission from Raymond Hettinger : What do you think it is necessary to switch from implicit chaining to explicit chaining? If anyone is currently relying on __context__ vs __cause__, this patch will break their code. In a traceback, the only visible difference is in the text between

[issue39715] Implement __repr__ methods for AST classes

Change by Raymond Hettinger : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39715] Implement __repr__ methods for AST classes

Ram Rachum added the comment: I understand that we have to be really careful in including information that could have unlimited size. But I think we have lots of information that isn't that way. For example, for ClassDef and FunctionDef objects, we could include the name. For Assign, we

[issue39717] Fix exception causes in tarfile module

Change by Ram Rachum : -- components: Library (Lib) nosy: cool-RR priority: normal pull_requests: 17962 severity: normal status: open title: Fix exception causes in tarfile module type: behavior versions: Python 3.9 ___ Python tracker

[issue39715] Implement __repr__ methods for AST classes

Batuhan Taskaya added the comment: What kind of repr do you have in your mind? If the repr you are thinking contains field information, it would be no-go. Fields of AST objects can contain other objects and fields of that objects can contain more objects (this goes up to the recursion limit

[issue39715] Implement __repr__ methods for AST classes

Change by Karthikeyan Singaravelan : -- nosy: +BTaskaya, pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue39716] argparse.ArgumentParser does not raise on duplicated subparsers, even though it does on duplicated flags

Change by Karthikeyan Singaravelan : -- nosy: +paul.j3, rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue39705] Tutorial, 5.6 Looping Techniques, sorted() example

Eric V. Smith added the comment: That sounds like a good improvement, Raymond. -- ___ Python tracker ___ ___ Python-bugs-list

[issue39716] argparse.ArgumentParser does not raise on duplicated subparsers, even though it does on duplicated flags

New submission from Antony Lee : If one tries to add twice the same flag to an ArgumentParser, one gets a helpful exception: from argparse import ArgumentParser p = ArgumentParser() p.add_argument("--foo") p.add_argument("--foo") results in argparse.ArgumentError:

[issue38342] ImportError: cannot import name 'MetadataPathFinder' from 'importlib.metadata'

Manjusaka added the comment: Hello Mariatta I have tested the code below on 3.8.1 what's installed by pyenv on my Mac from importlib.metadata import version, requires, files version('requests') it works correctly. I think it depends on the tool what's used to install python --

[issue39715] Implement __repr__ methods for AST classes

New submission from Ram Rachum : I was playing with the `ast` library today, and it's frustrating to see objects like these: [<_ast.Import object at 0x033FB048>, <_ast.Import object at 0x033FB0F0>, <_ast.ImportFrom object at 0x033FB160>, <_ast.Import

[issue35950] io.BufferedReader.writabe is False, but io.BufferedReader.truncate does not raise OSError

Change by Inada Naoki : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.9 -Python 3.7 ___ Python tracker ___

[issue39714] ElementTree limitation

New submission from Ananth Vijalapuram : I am trying to parse a very large XML file. Here is the output: python3.7.4 crif_parser.py Retrieved 3593891712 characters <- this is printed from my script Traceback (most recent call last): File "crif_parser.py", line 9, in tree =

[issue35950] io.BufferedReader.writabe is False, but io.BufferedReader.truncate does not raise OSError

miss-islington added the comment: New changeset fd5116c0e77aec05f67fb24f10562ac920648035 by Berker Peksag in branch 'master': bpo-35950: Raise UnsupportedOperation in BufferedReader.truncate() (GH-18586) https://github.com/python/cpython/commit/fd5116c0e77aec05f67fb24f10562ac920648035

[issue39713] ElementTree limitation

Change by Ananth Vijalapuram : -- resolution: -> later stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue39713] ElementTree limitation

New submission from Ananth Vijalapuram : I am trying to parse a very large XML file. Here is the output: /usr/intel/bin/python3.7.4 crif_parser.py Retrieved 3593891712 characters <- this is printed from my script Traceback (most recent call last): File "crif_parser.py", line 9, in tree

[issue39705] Tutorial, 5.6 Looping Techniques, sorted() example

Raymond Hettinger added the comment: I prefer to keep the example as-is. It is an idiomatic way to loop over sets. The introductory text can be modified to explain that sets eliminate duplicates, that sets are ordered, and that sorted() puts them back in a deterministic order. --

[issue39712] Doc for `-X dev` option should mention PYTHONDEVMODE

New submission from Antoine Pitrou : In the doc for `-X` options (https://docs.python.org/3/using/cmdline.html#id5), when an option can be triggered through an equivalent environment variable, that variable is mentioned. An exception to that is `-X dev`, which can also be triggered by the

[issue39707] Abstract property setter/deleter implementation not enforced.

Raymond Hettinger added the comment: Off-hand, I don't see how this can be easily fixed because the setters and deleters are all part of a single property object. When the subclass defines a property without a getter and setter, the inherited abstract property (that does have a getter and

[issue39704] Disable code coverage

Ammar Askar added the comment: Also just to clarify, the actual coverage build which measures the build. That is: https://github.com/python/cpython/blob/d4d17fd2cf69e7c8f4cd03fbf2d575370945b952/.travis.yml#L75-L114 is fine. The build succeeds and the coverage can be seen online at

[issue39711] SIGBUS and core dumped during tests of 3.8.1

New submission from Dennis Clarke : The testsuite fails badly with a SIGBUS thus : . . . 0:01:37 load avg: 2.81 [ 26/423/1] test_frozen passed 0:01:40 load avg: 2.77 [ 27/423/1] test_eof passed -- running: test_importlib (31.7 sec), test_socket (31.2 sec) 0:01:41 load avg: 2.75 [ 28/423/1]

[issue39710] "will be returned as unicode" reminiscent from Python 2

New submission from Julien Palard : In https://docs.python.org/3/library/calendar.html#calendar.LocaleTextCalendar I read "If this locale includes an encoding all strings containing month and weekday names will be returned as unicode." `unicode` here is a mention of the `unicode` type from

[issue39704] Disable code coverage

Stefan Krah added the comment: They are allowed failures but the build is still marked in red: https://github.com/python/cpython/pull/18567 So if you look at the front page you have to click through red results only to find that the reason is code coverage. --

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Stefan Krah added the comment: Updated docs: https://github.com/python/cpython/pull/18594 The PR uses some of Tim's suggestions while also explaining how to calculate the amount of memory used in a single large decimal. Hopefully it isn't too much information. --

[issue39537] Change line number table format

Mark Shannon added the comment: Serhiy, Although the code generator is syntax directed, not all code has an explicit piece of syntax attached. For example in the following code: ``` def foo(): if x: print("yes") else: print("no") ``` the compiler emits code to return

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Change by Stefan Krah : -- pull_requests: +17961 pull_request: https://github.com/python/cpython/pull/18594 ___ Python tracker ___

[issue39709] missing CFLAGS during make tests results in test and compile failure

New submission from Dennis Clarke : Seems to be an error in the Makefile(s) in that the "make test" can not compile some code for the correct architecture : The process seems to begin well and fine : alpha$ LD_LIBRARY_PATH=`pwd` /usr/local/bin/gmake test 2>&1 | tee

[issue39708] final link stage in compile fails for 3.8.1 with missing CFLAGS

New submission from Dennis Clarke : During compile after a sucessful configure the final link stage fails : /opt/developerstudio12.6/bin/cc -R/usr/local/lib -L/usr/local/lib -R/usr/local/lib -L/usr/local/lib-o python Programs/python.o -Wl,-R,/usr/local/lib -L. -lpython3.8d -lsocket

[issue39681] pickle.load expects an object that implements readinto

Change by Antoine Pitrou : -- assignee: -> pitrou type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue39681] pickle.load expects an object that implements readinto

Change by Antoine Pitrou : -- keywords: +patch pull_requests: +17960 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18592 ___ Python tracker ___

[issue39694] Incorrect dictionary unpacking when calling str.format

Akos Kiss added the comment: I've come up with some extra examples (use cases?): ```py import collections class str2(str): def format(self, *args, **kwargs): return super().format(*args, **kwargs) def unpacknonekey(s): print('input:', type(s), s) try: print('str

[issue39707] Abstract property setter/deleter implementation not enforced.

New submission from Arn Vollebregt (KPN) : When concretely implementing an abstract ABC class with an abstract property getter, setter and deleter it is not enfored that the setter and deleter are implemented. Instead, the property is treated as a read-only property (as would normally be the

[issue39706] unittest.IsolatedAsyncioTestCase hangs on asyncio.CancelledError

New submission from Andrey Moiseev : The following code hangs: import asyncio import unittest class TestCancellation(unittest.IsolatedAsyncioTestCase): async def test_works(self): raise asyncio.CancelledError() if __name__ == '__main__': unittest.main() --

[issue39628] msg.walk memory leak?

Marco added the comment: uhm, no. I can no more reproduce this. I was wrong. Sorry for the noise. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue39681] pickle.load expects an object that implements readinto

Antoine Pitrou added the comment: Well, in the mmap case, this is trivially fixed by writing: ``` with open("my_data.pkl", "r+b") as f_in: mm = mmap.mmap(f_in.fileno(), 0) print(pickle.loads(memoryview(mm))) ``` It will also be faster this way, since the pickle will be read directly from

[issue39648] Update math.gcd() to accept "n" arguments.

Change by Ananthakrishnan : -- keywords: +patch pull_requests: +17959 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18590 ___ Python tracker ___

[issue39648] Update math.gcd() to accept "n" arguments.

Ananthakrishnan added the comment: Thanks for the hint.Made changes. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue39705] Tutorial, 5.6 Looping Techniques, sorted() example

Eric V. Smith added the comment: The code is converting to a set first, then calls sorted() on that set. So "apple" is removed when the set is created. I'm not sure the example should throw in creating a set while it's talking about sorting. -- nosy: +eric.smith

[issue35727] sys.exit() in a multiprocessing.Process does not align with Python behavior

Antoine Pitrou added the comment: Sorry for the delay. I've now merged the PR for 3.9. Since this is a slight behaviour change, and the original issue was easy to workaround, I won't backport it. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed

[issue35727] sys.exit() in a multiprocessing.Process does not align with Python behavior

Antoine Pitrou added the comment: New changeset c2ac4cf040ea950bf552d1e77bea613a1a5474fe by Christopher Hunt in branch 'master': bpo-35727: Use exit code 0 on sys.exit() in multiprocessing.Process. (GH-11538) https://github.com/python/cpython/commit/c2ac4cf040ea950bf552d1e77bea613a1a5474fe

[issue39705] Tutorial, 5.6 Looping Techniques, sorted() example

New submission from Mirwi : >>> basket = ['apple', 'orange', 'apple', 'pear', 'orange', 'banana'] >>> for f in sorted(set(basket)): ... print(f) ... apple banana orange pear Shouldn't 'apple' appear two times as basket is a list that allows duplicates, not a set? I'm just doing my first

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Stefan Krah added the comment: "So non-integer powers are left out" in isolation would indeed be wrong, but actual sentence is unambiguously qualified with: "... since _decimal has no notion of exact non-integer powers yet.", which clearly states that exact non-integer powers exist and

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Vedran Čačić added the comment: Well, it all depends on how do you intend to read it. To me, the closing quote and "So non-integer powers are left out" after it suggested that the non-integer powers being left out is somehow a consequence of the above paragraph. When in fact instead of "so"

[issue39648] Update math.gcd() to accept "n" arguments.

Ananthakrishnan added the comment: Yes I know. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected

Tal Einat added the comment: Thanks for the PR, Alex! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.9 -Python 3.3, Python 3.4 ___ Python tracker

[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected

Tal Einat added the comment: New changeset d4331c56b4f6fe6f18caf19fc1ecf9fec14f7066 by alclarks in branch 'master': bpo-9495: avoid confusing chained exception in argparse test (GH-17120) https://github.com/python/cpython/commit/d4331c56b4f6fe6f18caf19fc1ecf9fec14f7066 -- nosy:

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

Stefan Krah added the comment: Vedran, msg362365 is meant to say: "This PR implements $SOMEWHAT_MATHEMATICAL_SPEC except for inexact power." Had I put the caveat inside the statement as well, the message would have been: "This PR implements

[issue39704] Disable code coverage

Karthikeyan Singaravelan added the comment: Thanks for the clarification, I agree on disabling automatic coverage comments. Aren't these builds already optional in Travis marked as allow failures and status is reported once the required builds pass though the coverage builds keep running?

[issue39704] Disable code coverage

Stefan Krah added the comment: I'd definitely disable the automatic comment and prefer that the build happens on buildbot.python.org rather than affecting the GitHub build status. -- ___ Python tracker