[issue39722] decimal differs between pure Python and C implementations

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Thanks for double checking.

--
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39722] decimal differs between pure Python and C implementations

[Shantanu]

Shantanu  added the comment:

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

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39722] decimal differs between pure Python and C implementations

[Raymond Hettinger]

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 implementation.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39721] Fix constness of members of tok_state struct.

[SilentGhost]

Change by SilentGhost :


--
nosy: +serhiy.storchaka, vstinner
type:  -> behavior
versions: +Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Berker Peksag]

Change by Berker Peksag :


--
nosy: +berker.peksag

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39717] Fix exception causes in tarfile module

[Ram Rachum]

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 tools like Django and Sentry show you all the local variables for 
your stacktraces, which is a godsend. These often have important information 
that sheds light on what went wrong, and if you remove the traceback they'll be 
gone.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39723] io.open_code should accept PathLike objects

[Shantanu]

Change by Shantanu :


--
keywords: +patch
pull_requests: +17969
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/18602

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39704] Disable code coverage

[Terry J. Reedy]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39723] io.open_code should accept PathLike objects

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
nosy: +xtreak

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39653] test_posix fails during make test

[Terry J. Reedy]

Terry J. Reedy  added the comment:

==
ERROR: test_no_such_executable (test.test_posix.TestPosixSpawnP)
--
Traceback (most recent call last):
  File "/home/zachary/Python-3.8.1/Lib/test/test_posix.py", line 1529, in 
test_no_such_executable
pid = self.spawn_func(no_such_executable,
NotADirectoryError: [Errno 20] Not a directory: 'no_such_executable'

is all that is needed.

--
nosy: +terry.reedy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Terry J. Reedy]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39717] Fix exception causes in tarfile module

[Martin Panter]

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 tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39723] io.open_code should accept PathLike objects

[Shantanu]

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 interchangeable with ``open(path, 'rb')``.

https://github.com/python/cpython/blob/3.8/Modules/_io/_iomodule.c#L510

--
components: Library (Lib)
messages: 362446
nosy: hauntsaninja
priority: normal
severity: normal
status: open
title: io.open_code should accept PathLike objects
type: enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Andy Lester]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Andy Lester]

Change by Andy Lester :


--
pull_requests: +17968
pull_request: https://github.com/python/cpython/pull/18601

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39722] decimal differs between pure Python and C implementations

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
nosy: +facundobatista, mark.dickinson, rhettinger, skrah

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39717] Fix exception causes in tarfile module

[Ethan Furman]

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:

-
"During handling of the above exception, another exception occurred:"

-> there is a bug in the exception handler.
-

-
"The above exception was the direct cause of the following exception:"

-> the first error is the cause and the second error is what we want the user 
to pay attention to.
-

Whether or not the stdlib is buggy is a pretty big distinction.

If this is a change worth making the follow-on question is should we be raising 
from the previous exception, or from None?  How much value is the previous 
exception adding?

In cases where the new exception contains the text of the old one I think `from 
None` should be preferred; in cases where import errors get translated into 
CompressionErrors those import errors are sometimes useful and sometimes just 
noise -- perhaps including `str(e)` in the new exception is the best way there 
as well.

I'll need to do some research before I decide.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39722] decimal differs between pure Python and C implementations

[Shantanu]

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 the issue:
```
Python 3.8.1 (default, Jan 14 2020, 19:41:43) 
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from _decimal import Decimal as CDecimal
>>> from _pydecimal import Decimal as PyDecimal
>>> PyDecimal(1).__abs__(None)
Decimal('1')
>>> CDecimal(1).__abs__(None)
Traceback (most recent call last):
  File "", line 1, in 
TypeError: expected 0 arguments, got 1
```

--
components: Library (Lib)
messages: 362443
nosy: hauntsaninja
priority: normal
severity: normal
status: open
title: decimal differs between pure Python and C implementations

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Karthikeyan Singaravelan]

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__ .

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39721] Fix constness of members of tok_state struct.

[Andy Lester]

Change by Andy Lester :


--
keywords: +patch
pull_requests: +17967
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/18600

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39721] Fix constness of members of tok_state struct.

[Andy Lester]

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 have been non-const

Changes to support this include:
* decode_str() now returns a char * since it is allocated.
* PyTokenizer_FromString() and PyTokenizer_FromUTF8() each creates a
new char * for an allocate string instead of reusing the input
const char *.
* PyTokenizer_Get() and tok_get() now take const char ** arguments.
* Various local vars are const or non-const accordingly.

I was able to remove five casts that cast away constness.

--
components: Interpreter Core
messages: 362441
nosy: petdance
priority: normal
severity: normal
status: open
title: Fix constness of members of tok_state struct.

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39717] Fix exception causes in tarfile module

[Raymond Hettinger]

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 more concise.

--
assignee:  -> ethan.furman
nosy: +ethan.furman

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39720] Signature.bind TypeErrors could be more helpful

[Frazer McLean]

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:
print(exc.args[0])
else:
raise RuntimeError('Expected to raise!')
sig = inspect.signature(f)
try:
sig.bind()
except TypeError as exc:
print(exc.args[0])
else:
raise RuntimeError('Expected to raise!')
print()

@run
def f1(pos_only, /): ...

@run
def f2(pos_or_kw): ...

@run
def f3(*, kw_only): ...

Output on current 3.9 master:

f1() missing 1 required positional argument: 'pos_only'
missing a required argument: 'pos_only'

f2() missing 1 required positional argument: 'pos_or_kw'
missing a required argument: 'pos_or_kw'

f3() missing 1 required keyword-only argument: 'kw_only'
missing a required argument: 'kw_only'

I am willing to create a PR so that the TypeError for f3 says "missing a 
required keyword-only argument: 'kw_only'", if this would be accepted.

--
components: Library (Lib)
messages: 362439
nosy: RazerM
priority: normal
severity: normal
status: open
title: Signature.bind TypeErrors could be more helpful
type: enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Guido van Rossum]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39719] tempfile.SpooledTemporaryFile still has softspace property

[Shantanu]

Change by Shantanu :


--
keywords: +patch
pull_requests: +17966
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/18599

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39719] tempfile.SpooledTemporaryFile still has softspace property

[Shantanu]

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 attribute.

```
In [23]: t = tempfile.SpooledTemporaryFile()

In [24]: t.softspace
---
AttributeErrorTraceback (most recent call last)
 in 
> 1 t.softspace

/usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/tempfile.py
 in softspace(self)
749 @property
750 def softspace(self):
--> 751 return self._file.softspace
752 
753 def tell(self):

AttributeError: '_io.BytesIO' object has no attribute 'softspace'
```

--
messages: 362437
nosy: hauntsaninja
priority: normal
severity: normal
status: open
title: tempfile.SpooledTemporaryFile still has softspace property

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Shantanu]

Change by Shantanu :


--
keywords: +patch
pull_requests: +17965
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/18598

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Shantanu]

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
severity: normal
status: open
title: TYPE_IGNORE, COLONEQUAL missing from py38 changes in token docs

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Tim Peters]

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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Viktor Roytman]

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", line 
193, in _run_module_as_main
return _run_code(code, main_globals, None,
  File "/home/viktor/.pyenv/versions/3.8.1/lib/python3.8/runpy.py", line 
86, in _run_code
exec(code, run_globals)
  File "/home/viktor/scratch/bad_classmethod_as_documented.py", line 4, in 

class Negator:
  File "/home/viktor/scratch/bad_classmethod_as_documented.py", line 12, in 
Negator
def _(cls, arg: int):
  File "/home/viktor/.pyenv/versions/3.8.1/lib/python3.8/functools.py", 
line 1006, in register
return self.dispatcher.register(cls, func=method)
  File "/home/viktor/.pyenv/versions/3.8.1/lib/python3.8/functools.py", 
line 959, in register
argname, cls = next(iter(get_type_hints(func).items()))
  File "/home/viktor/.pyenv/versions/3.8.1/lib/python3.8/typing.py", line 
1252, in get_type_hints
raise TypeError('{!r} is not a module, class, method, '
TypeError:  is not a module, class, 
method, or function.

After digging around a bit, this diff seems to work (not sure if there's a 
better way to do it) (also this one doesn't seem to care whether @staticmethod 
is applied to the implementation methods):

$ diff -u functools-orig.py functools.py
--- functools-orig.py   2020-02-21 16:14:56.141934001 -0500
+++ functools.py2020-02-21 16:17:19.959905849 -0500
@@ -843,14 +843,18 @@
 if func is None:
 if isinstance(cls, type):
 return lambda f: register(cls, f)
-ann = getattr(cls, '__annotations__', {})
+if isinstance(cls, (classmethod, staticmethod)):
+ann = getattr(cls.__func__, '__annotations__', {})
+func = cls.__func__
+else:
+ann = getattr(cls, '__annotations__', {})
+func = cls
 if not ann:
 raise TypeError(
 f"Invalid first argument to `register()`: {cls!r}. "
 f"Use either `@register(some_class)` or plain `@register` "
 f"on an annotated function."
 )
-func = cls
 
 # only import typing if annotation parsing is necessary
 from typing import get_type_hints
@@ -908,6 +912,8 @@
 def __get__(self, obj, cls=None):
 def _method(*args, **kwargs):
 method = self.dispatcher.dispatch(args[0].__class__)
+if isinstance(self.func, classmethod):
+return method.__get__(obj, cls)(cls, *args, **kwargs)
 return method.__get__(obj, cls)(*args, **kwargs)
 
 _method.__isabstractmethod__ = self.__isabstractmethod__

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39715] Implement __repr__ methods for AST classes

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

For more informative representation you can use ast.dump().

--
nosy: +serhiy.storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Stefan Krah]

Change by Stefan Krah :


--
stage: patch review -> resolved

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Stefan Krah]

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.

--
assignee: skrah -> 
resolution:  -> fixed
versions: +Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39717] Fix exception causes in tarfile module

[Ram Rachum]

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 places as I can. 

I think that the more accurate it is, the more people will learn to trust that 
it has meaning and understand it. 

> If anyone is currently relying on __context__ vs __cause__, this patch will 
> break their code.

I think that the standard you're setting for backward compatibility is 
unreasonably high.

The only code I can think of that inspects `__context__` and `__cause__` is 
code that formats exceptions to be shown to the user, such as Django's debug 
page, Wing IDE's Exceptions pane, whatever's going on in PyCharm etc. That kind 
of code is responsible for checking for both `__context__` and `__cause__` and 
showing the correct message.

If you've seen code outside of the category above that uses `__context__`, I'd 
be curious to see it.

Fortunately, this point is moot since using `raise foo from bar` sets the 
`__context__ = __cause__ = bar`, so the `__context__` will not be changed.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Stefan Krah]

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)
https://github.com/python/cpython/commit/d6965ff026f35498e554bc964ef2be8f4d80eb7f


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Stefan Krah]

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)
https://github.com/python/cpython/commit/00e45877e33d32bb61aa13a2033e3bba370bda4d


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Would you like to work-up a patch to fix this?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[miss-islington]

Change by miss-islington :


--
pull_requests: +17964
pull_request: https://github.com/python/cpython/pull/18597

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[miss-islington]

Change by miss-islington :


--
pull_requests: +17963
pull_request: https://github.com/python/cpython/pull/18596

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39717] Fix exception causes in tarfile module

[Raymond Hettinger]

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, nothing is currently broken and the 
minor change in traceback wording would not confer a real benefit.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Stefan Krah]

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


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39717] Fix exception causes in tarfile module

[Raymond Hettinger]

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 the 
exceptions:

- During handling of the above exception, another exception occurred:
+ The above exception was the direct cause of the following exception:

While we haven't been 100% consistent about this, the norm has been to either 
use implicit chaining or use "from None" to turn-off chaining.  The "from e" 
approach can be used to alter the explicit chain, perhaps skipping over one or 
more exceptions, but that isn't the case here.

--
nosy: +rhettinger

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39715] Implement __repr__ methods for AST classes

[Raymond Hettinger]

Change by Raymond Hettinger :


--
nosy: +brett.cannon

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39715] Implement __repr__ methods for AST classes

[Ram Rachum]

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 could include the lhs. For Import, we could include the module 
name, etc.

And for all objects, we could include the number of descendants that they have, 
so people could more easily understand which are tiny and which are huge.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39717] Fix exception causes in tarfile module

[Ram Rachum]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39715] Implement __repr__ methods for AST classes

[Batuhan Taskaya]

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 where the child can not be no longer 
calculated). This is why we have ast.dump instead. For small debuggings there 
are 3rd party libraries (e.g: asteria) which adds __repr__ on runtime for 
working on nodes, but on a real application this can cause more problem then it 
benefits.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39715] Implement __repr__ methods for AST classes

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
nosy: +BTaskaya, pablogsal

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
nosy: +paul.j3, rhettinger

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Eric V. Smith]

Eric V. Smith  added the comment:

That sounds like a good improvement, Raymond.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antony Lee]

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: argument --foo: conflicting option string: --foo

However, adding twice the same subparser raises no exception:

from argparse import ArgumentParser
p = ArgumentParser()
sp = p.add_subparsers()
sp.add_parser("foo")
sp.add_parser("foo")

even though the two subparsers shadow one another in the same way as two 
identical flags.

--
components: Library (Lib)
messages: 362421
nosy: Antony.Lee
priority: normal
severity: normal
status: open
title: argparse.ArgumentParser does not raise on duplicated subparsers, even 
though it does on duplicated flags
versions: Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Manjusaka]

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

--
nosy: +Manjusaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39715] Implement __repr__ methods for AST classes

[Ram Rachum]

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 object at 0x033FB1D0>,
 <_ast.Assign object at 0x033FB240>,
 <_ast.If object at 0x033FB630>]

A little bit more information about each object in the `__repr__` would make 
this module much easier to work with.

--
components: Library (Lib)
messages: 362419
nosy: cool-RR
priority: normal
severity: normal
status: open
title: Implement __repr__ methods for AST classes
type: enhancement
versions: Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Inada Naoki]

Change by Inada Naoki :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.9 -Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39714] ElementTree limitation

[Ananth Vijalapuram]

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 = ET.fromstring(data)
  File "python3/3.7.4/lib/python3.7/xml/etree/ElementTree.py", line 1315, in XML
parser.feed(text)
OverflowError: size does not fit in an int

--
components: XML
messages: 362418
nosy: Ananth Vijalapuram
priority: normal
severity: normal
status: open
title: ElementTree limitation
type: behavior
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[miss-islington]

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


--
nosy: +miss-islington

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39713] ElementTree limitation

[Ananth Vijalapuram]

Change by Ananth Vijalapuram :


--
resolution:  -> later
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39713] ElementTree limitation

[Ananth Vijalapuram]

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 = ET.fromstring(data)
  File "/usr/intel/pkgs/python3/3.7.4/lib/python3.7/xml/etree/ElementTree.py", 
line 1315, in XML
parser.feed(text)
OverflowError: size does not fit in an int

--
components: XML
messages: 362416
nosy: Ananth Vijalapuram
priority: normal
severity: normal
status: open
title: ElementTree limitation
type: behavior
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raymond Hettinger]

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.

--
assignee: docs@python -> rhettinger
nosy: +rhettinger

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antoine Pitrou]

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 
PYTHONDEVMODE variable, but that isn't mentioned in the CLI doc.

Other missing environment variables in the CLI doc are PYTHONFAULTHANDLER and 
PYTHONTRACEMALLOC.

--
assignee: docs@python
components: Documentation
keywords: easy, newcomer friendly
messages: 362414
nosy: docs@python, eric.araujo, ezio.melotti, mdk, pitrou, vstinner, willingc
priority: normal
severity: normal
stage: needs patch
status: open
title: Doc for `-X dev` option should mention PYTHONDEVMODE
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Raymond Hettinger]

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 setter) is masked.

Right now, ABCMeta only looks at the concrete property.  It would have to be 
modified to scan the next in MRO for an abstract property and the pick apart 
its component fget, fset, and fdel.  That would be a significant jump in 
complexity with only a minimal payoff.

--
nosy: +gvanrossum, rhettinger

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39704] Disable code coverage

[Ammar Askar]

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 
https://codecov.io/gh/python/cpython to get a high-level overview of coverage.

The integration with codecov as a status check and it's comments are the real 
nuisance.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39711] SIGBUS and core dumped during tests of 3.8.1

[Dennis Clarke]

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] test_poplib passed -- running: 
test_importlib (32.8 sec), test_socket (32.2 sec)
0:01:45 load avg: 2.71 [ 29/423/1] test_aifc passed -- running: test_importlib 
(37.2 sec), test_socket (36.7 sec)
0:01:46 load avg: 2.71 [ 30/423/1] test_unicode_file_functions passed -- 
running: test_importlib (37.8 sec), test_socket (37.2 sec)
0:01:51 load avg: 2.71 [ 31/423/1] test_listcomps passed -- running: 
test_importlib (42.9 sec), test_socket (42.4 sec)
0:01:54 load avg: 2.75 [ 32/423/1] test_asdl_parser passed -- running: 
test_importlib (46.0 sec), test_socket (45.4 sec)
0:01:57 load avg: 2.77 [ 33/423/1] test_richcmp passed -- running: 
test_importlib (49.1 sec), test_socket (48.6 sec)
0:02:01 load avg: 2.78 [ 34/423/1] test_importlib passed (48.3 sec) -- running: 
test_socket (51.8 sec)
0:02:04 load avg: 2.76 [ 35/423/1] test_rlcompleter passed -- running: 
test_socket (55.6 sec)
0:02:08 load avg: 2.75 [ 36/423/1] test_sys_setprofile passed -- running: 
test_socket (59.0 sec)
0:02:16 load avg: 2.72 [ 37/423/1] test_tuple passed -- running: test_socket (1 
min 7 sec), test_capi (31.0 sec)
0:02:39 load avg: 2.73 [ 38/423/1] test_c_locale_coercion passed -- running: 
test_ast (31.4 sec), test_socket (1 min 30 sec), test_capi (53.8 sec)
0:02:44 load avg: 2.76 [ 39/423/1] test_symtable passed -- running: test_ast 
(36.6 sec), test_socket (1 min 35 sec), test_capi (58.9 sec)
0:03:01 load avg: 2.88 [ 40/423/1] test_ast passed (51.2 sec) -- running: 
test_socket (1 min 52 sec), test_capi (1 min 15 sec)
0:03:04 load avg: 2.89 [ 41/423/1] test_pow passed -- running: test_socket (1 
min 55 sec), test_capi (1 min 18 sec)
0:03:19 load avg: 2.90 [ 42/423/1] test_http_cookiejar passed -- running: 
test_socket (2 min 10 sec), test_capi (1 min 33 sec)
0:03:21 load avg: 2.88 [ 43/423/1] test_defaultdict passed -- running: 
test_socket (2 min 12 sec), test_capi (1 min 36 sec)
0:03:24 load avg: 2.86 [ 44/423/1] test_winconsoleio skipped -- running: 
test_socket (2 min 15 sec), test_capi (1 min 38 sec)
test_winconsoleio skipped -- test only relevant on win32
0:03:34 load avg: 2.77 [ 45/423/1] test_cprofile passed -- running: test_socket 
(2 min 25 sec), test_capi (1 min 48 sec)
0:03:37 load avg: 2.75 [ 46/423/1] test_nntplib passed -- running: test_socket 
(2 min 28 sec), test_capi (1 min 51 sec)
0:03:42 load avg: 2.74 [ 47/423/1] test_xml_dom_minicompat passed -- running: 
test_socket (2 min 33 sec), test_capi (1 min 56 sec)
0:03:46 load avg: 2.77 [ 48/423/1] test_pkgimport passed -- running: 
test_socket (2 min 37 sec), test_capi (2 min)
0:04:00 load avg: 2.80 [ 49/423/1] test_timeout passed -- running: test_socket 
(2 min 51 sec), test_capi (2 min 14 sec)
0:04:04 load avg: 2.78 [ 50/423/1] test_pkg passed -- running: test_socket (2 
min 54 sec), test_capi (2 min 18 sec)
0:04:09 load avg: 2.79 [ 51/423/1] test_mimetypes passed -- running: 
test_support (34.9 sec), test_socket (2 min 59 sec), test_capi (2 min 23 sec)
0:04:18 load avg: 2.85 [ 52/423/1] test_base64 passed -- running: test_support 
(44.1 sec), test_socket (3 min 9 sec), test_capi (2 min 32 sec)
0:04:23 load avg: 2.88 [ 53/423/1] test_metaclass passed -- running: 
test_support (48.9 sec), test_socket (3 min 13 sec), test_capi (2 min 37 sec)
0:04:24 load avg: 2.89 [ 54/423/2] test_timeit crashed (Exit code 1) -- 
running: test_support (50.4 sec), test_socket (3 min 15 sec), test_capi (2 min 
38 sec)
Traceback (most recent call last):
  File "/usr/local/build/Python-3.8.1/Lib/runpy.py", line 193, in 
_run_module_as_main
  File "/usr/local/build/Python-3.8.1/Lib/runpy.py", line 86, in _run_code
  File "/usr/local/build/Python-3.8.1/Lib/test/regrtest.py", line 14, in 

  File "/usr/local/build/Python-3.8.1/Lib/test/libregrtest/__init__.py", line 
1, in 
  File "/usr/local/build/Python-3.8.1/Lib/test/libregrtest/cmdline.py", line 4, 
in 
  File "/usr/local/build/Python-3.8.1/Lib/test/support/__init__.py", line 6, in 

  File "/usr/local/build/Python-3.8.1/Lib/asyncio/__init__.py", line 8, in 

  File "/usr/local/build/Python-3.8.1/Lib/asyncio/base_events.py", line 45, in 

  File "/usr/local/build/Python-3.8.1/Lib/asyncio/staggered.py", line 10, in 

  File "", line 991, in _find_and_load
  File "", line 975, in _find_and_load_unlocked
  File "", line 671, in _load_unlocked
  File "", line 779, in exec_module
  File "", line 874, in get_code
  File "", line 972, in get_data
MemoryError
Warning -- regrtest worker thread failed: Traceback (most recent call last):
  File "/usr/local/build/Python-3.8.1/Lib/test/libregrtest/runtest_mp.py", line 
264, in run
mp_result = self._runtest(test_name)
  File "/usr/local/build/Python-3.8.1/Lib/test/libregrtest/runtest_mp.py", line 
229, in 

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

[Julien Palard]

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 Python 2 which does no 
longer exists, so the whole sentence can just be removed.

It happen also in the next paragraph, and twice in Lib/calendar.py.

In Python 2:

>>> print type(calendar.LocaleTextCalendar(locale="C").formatmonth(2020, 1))

>>> print 
>>> type(calendar.LocaleTextCalendar(locale="en_US.UTF8").formatmonth(2020, 1))


In Python 3:

>>> print(type(calendar.LocaleTextCalendar(locale="C").formatmonth(2020, 1)))

>>> print(type(calendar.LocaleTextCalendar(locale="en_US.UTF8").formatmonth(2020,
>>>  1)))


--
assignee: docs@python
components: Documentation
keywords: easy
messages: 362410
nosy: docs@python, mdk
priority: normal
severity: normal
status: open
title: "will be returned as unicode" reminiscent from Python 2

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39704] Disable code coverage

[Stefan Krah]

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.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Stefan Krah]

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.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39537] Change line number table format

[Mark Shannon]

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 from the function (LOAD_CONST None; 
RETURN_VALUE), but there is no explicit return, and no meaningful line number 
for the return.

Also consider, the artificial try-except block generated for async for loops 
and the cleanup code for named exception variables.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Stefan Krah]

Change by Stefan Krah :


--
pull_requests: +17961
pull_request: https://github.com/python/cpython/pull/18594

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Dennis Clarke]

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 
../python_3.8.1_SunOS5.10_sparc64vii+.003.test.log
LD_LIBRARY_PATH=/usr/local/build/python_3.8.1_SunOS5.10_sparc64vii+.003 
./python -E -S -m sysconfig --generate-posix-vars ;\
if test $? -ne 0 ; then \
echo "generate-posix-vars failed" ; \
rm -f ./pybuilddir.txt ; \
exit 1 ; \
fi
/opt/developerstudio12.6/bin/cc -c -xcode=pic32   -std=iso9899:2011 
-errfmt=error -erroff=%none -errshort=full -xstrconst -xildoff -m64 
-xmemalign=8s -xnolibmil -xcode=pic32 -xregs=no%appl -xlibmieee -mc -g -xs 
-ftrap=%none -Qy -xbuiltin=%none -xdebugformat=dwarf -xunroll=1 -xarch=sparc 
-L/usr/local/lib -R/usr/local/lib -D_REENTRANT -std=iso9899:2011 -errfmt=error 
-erroff=%none -errshort=full -xstrconst -xildoff -m64 -xmemalign=8s -xnolibmil 
-xcode=pic32 -xregs=no%appl -xlibmieee -mc -g -xs -ftrap=%none -Qy 
-xbuiltin=%none -xdebugformat=dwarf -xunroll=1 -xarch=sparc -L/usr/local/lib 
-R/usr/local/lib-I../Python-3.8.1/Include/internal -IObjects -IInclude 
-IPython -I. -I../Python-3.8.1/Include -I/usr/local/include -D_TS_ERRNO 
-D_POSIX_PTHREAD_SEMANTICS -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=600 
-I/usr/local/include -D_TS_ERRNO -D_POSIX_PTHREAD_SEMANTICS 
-D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=600 -xcode=pic32 -DPy_BUILD_CORE -o 
Modules/_math.o ../Python-3.8.1/Modules/_math.c
cc: Warning: multiple use of -Q option, previous one discarded.
LD_LIBRARY_PATH=/usr/local/build/python_3.8.1_SunOS5.10_sparc64vii+.003 
CC='/opt/developerstudio12.6/bin/cc' LDSHARED='/opt/developerstudio12.6/bin/cc 
-std=iso9899:2011 -errfmt=error -erroff=%none -errshort=full -xstrconst 
-xildoff -m64 -xmemalign=8s -xnolibmil -xcode=pic32 -xregs=no%appl -xlibmieee 
-mc -g -xs -ftrap=%none -Qy -xbuiltin=%none -xdebugformat=dwarf -xunroll=1 
-xarch=sparc -L/usr/local/lib -R/usr/local/lib -G -R/usr/local/lib 
-L/usr/local/lib -R/usr/local/lib -L/usr/local/lib  ' OPT='' 
_TCLTK_INCLUDES='' _TCLTK_LIBS=''   ./python -E ../Python-3.8.1/setup.py  
build
running build
running build_ext
building '_struct' extension
creating build/temp.solaris-2.10-sun4u.64bit-3.8-pydebug/usr
creating build/temp.solaris-2.10-sun4u.64bit-3.8-pydebug/usr/local
creating build/temp.solaris-2.10-sun4u.64bit-3.8-pydebug/usr/local/build
creating 
build/temp.solaris-2.10-sun4u.64bit-3.8-pydebug/usr/local/build/Python-3.8.1
creating 
build/temp.solaris-2.10-sun4u.64bit-3.8-pydebug/usr/local/build/Python-3.8.1/Modules
.
.
.
/opt/developerstudio12.6/bin/cc -std=iso9899:2011 -errfmt=error -erroff=%none 
-errshort=full -xstrconst -xildoff -m64 -xmemalign=8s -xnolibmil -xcode=pic32 
-xregs=no%appl -xlibmieee -mc -g -xs -ftrap=%none -Qy -xbuiltin=%none 
-xdebugformat=dwarf -xunroll=1 -xarch=sparc -L/usr/local/lib -R/usr/local/lib 
-G -R/usr/local/lib -L/usr/local/lib -R/usr/local/lib -L/usr/local/lib 
-R/usr/local/lib -L/usr/local/lib -std=iso9899:2011 -errfmt=error -erroff=%none 
-errshort=full -xstrconst -xildoff -m64 -xmemalign=8s -xnolibmil -xcode=pic32 
-xregs=no%appl -xlibmieee -mc -g -xs -ftrap=%none -Qy -xbuiltin=%none 
-xdebugformat=dwarf -xunroll=1 -xarch=sparc -L/usr/local/lib -R/usr/local/lib 
-I/usr/local/include -D_TS_ERRNO -D_POSIX_PTHREAD_SEMANTICS 
-D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE=600 
build/temp.solaris-2.10-sun4u.64bit-3.8-pydebug/usr/local/build/Python-3.8.1/Modules/_uuidmodule.o
 -L. -L/usr/local/lib -R/usr/local/lib -luuid -o 
build/lib.solaris-2.10-sun4u.64bit-3.8-pydebug/_uuid.so
cc: Warning: multiple use of -Q option, previous one discarded.
*** WARNING: renaming "_curses" since importing it failed: ld.so.1: python: 
fatal: relocation error: file 
build/lib.solaris-2.10-sun4u.64bit-3.8-pydebug/_curses.so: symbol acs32map: 
referenced symbol not found
*** WARNING: renaming "_curses_panel" since importing it failed: No module 
named '_curses'
INFO: Could not locate ffi libs and/or headers

Python build finished successfully!
The necessary bits to build these optional modules were not found:
_gdbm ossaudiodev  
To find the necessary bits, look in setup.py in detect_modules() for the 
module's name.


The following modules found by detect_modules() in setup.py, have been
built by the Makefile instead, as configured by the Setup files:
_abc  atexitpwd
time   


Failed to build these modules:
_ctypes


Following modules built successfully but were removed because they could not be 
imported:
_curses   _curses_panel

running build_scripts
creating build/scripts-3.8
copying and adjusting 

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

[Dennis Clarke]

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 -lnsl -lintl -lrt -ldl 
-lsendfile  -lm   -lm 
ld: fatal: file /opt/developerstudio12.6/lib/compilers/crti.o: wrong ELF class: 
ELFCLASS32
ld: fatal: file processing errors. No output written to python
gmake: *** [Makefile:578: python] Error 2

real 107.96
user 100.96
sys 21.96
alpha$

Easily done manually : 

alpha$ $CC $CFLAGS -R/usr/local/lib -L/usr/local/lib \
> -o python Programs/python.o \
> -Wl,-R,/usr/local/lib -L. -lpython3.8d -lsocket -lnsl -lintl -lrt -ldl 
> -lsendfile  -lm
alpha$ 

alpha$ file python 
python: ELF 64-bit MSB executable SPARCV9 Version 1, dynamically linked, not 
stripped
alpha$

--
components: Build
messages: 362405
nosy: blastwave
priority: normal
severity: normal
status: open
title: final link stage in compile fails for 3.8.1 with missing CFLAGS
type: compile error
versions: Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antoine Pitrou]

Change by Antoine Pitrou :


--
assignee:  -> pitrou
type:  -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antoine Pitrou]

Change by Antoine Pitrou :


--
keywords: +patch
pull_requests: +17960
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/18592

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39694] Incorrect dictionary unpacking when calling str.format

[Akos Kiss]

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 key:', s.format(**{'bar': 'qux'}))
print('none key:', s.format(**{'bar': 'qux', None: ''}))
except TypeError as e:
print('error:', e)

template = 'foo {bar} baz'
unpacknonekey(template)
unpacknonekey(str2(template))
unpacknonekey(collections.UserString(template))
```

The above script gives the following output:

```
input:  foo {bar} baz
str key: foo qux baz
none key: foo qux baz
input:  foo {bar} baz
str key: foo qux baz
error: format() keywords must be strings
input:  foo {bar} baz
str key: foo qux baz
error: format() keywords must be strings
```

This shows inconsistency between `format` of `str` and subclasses of `str` or 
the standard library's `UserString`.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Arn Vollebregt (KPN)]

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 case without a setter/deleter definition for a property) and 
the setter/deleter code from the abstract class is not present in the child 
class.

I would expect a TypeError exception when an abstract property is defined with 
a getter, setter and deleter but only the getter is implemented in a subclass 
(as is the case when not implementing the property getter). As a fallback, I 
would find it acceptable the code from the abstract class to be present in the 
child class, so at least the code that is defined there (in this case raising a 
NotImplementedError exception) would be executed.

An interactive interpreter session to replicate this behavior:

arn@hacktop:~$ python3
Python 3.7.5 (default, Nov 20 2019, 09:21:52)
[GCC 9.2.1 20191008] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import abc
>>>
>>> # Define the (abstract) interface.
... class MyInterface(abc.ABC):
...
... # Property getter.
... @property
... @abc.abstractmethod
... def myProperty(self) -> str:
... raise NotImplementedError
...
... # Property setter.
... @myProperty.setter
... @abc.abstractmethod
... def myProperty(self, value: str) -> None:
... raise NotImplementedError
...
... # Property deleter.
... @myProperty.deleter
... @abc.abstractmethod
... def myProperty(self) -> None:
... raise NotImplementedError
...
>>> # Implemented the interface.
... class MyImplementation(MyInterface):
... 
... # No abstract method implementation(s).
... pass
...
>>> # Creation of MyImplementation object raises TypeError as expected.
... obj = MyImplementation()
Traceback (most recent call last):
  File "", line 2, in 
TypeError: Can't instantiate abstract class MyImplementation with abstract 
methods myProperty
>>> import dis
>>> # The property getter code would raise an exception as defined in 
>>> MyInterface.
... dis.dis(MyImplementation.myProperty.fget.__code__.co_code)
  0 LOAD_GLOBAL  0 (0)
  2 RAISE_VARARGS1
  4 LOAD_CONST   0 (0)
  6 RETURN_VALUE
>>> # The property setter code would raise an exception as defined in 
>>> MyInterface.
... dis.dis(MyImplementation.myProperty.fset.__code__.co_code)
  0 LOAD_GLOBAL  0 (0)
  2 RAISE_VARARGS1
  4 LOAD_CONST   0 (0)
  6 RETURN_VALUE
>>> # The property deleter code would raise an exception as defined in 
>>> MyInterface.
... dis.dis(MyImplementation.myProperty.fdel.__code__.co_code)
  0 LOAD_GLOBAL  0 (0)
  2 RAISE_VARARGS1
  4 LOAD_CONST   0 (0)
  6 RETURN_VALUE
>>> # Let's reimplement with only the property getter.
... class MyImplementation(MyInterface):
...
... # Only implement abstract property getter.
... @property
... def myProperty(self) -> str:
... return "foobar"
...
>>> # Object can be created (against expectations).
... obj = MyImplementation()
>>> # The property getter works as defined.
... obj.myProperty
'foobar'
>>> # The property cannot be set (read-only).
... obj.myProperty = "barfoo"
Traceback (most recent call last):
  File "", line 2, in 
AttributeError: can't set attribute
>>> # The property cannot be deleted (read-only).
... del obj.myProperty
Traceback (most recent call last):
  File "", line 2, in 
AttributeError: can't delete attribute
>>> # The property getter code returns a string as defined in MyImplementation.
... type(MyImplementation.myProperty.fget)

>>> dis.dis(MyImplementation.myProperty.fget.__code__.co_code)
  0 LOAD_CONST   1 (1)
  2 RETURN_VALUE
>>> # The property setter code however does not exist, although defined in 
>>> MyInterface.
... type(MyImplementation.myProperty.fset)

>>> # Nor does the property deleter code, although defined in MyInterface.
... type(MyImplementation.myProperty.fdel)


--
messages: 362403
nosy: arn.vollebregt.kpn
priority: normal
severity: normal
status: open
title: Abstract property setter/deleter implementation not enforced.
type: behavior
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39706] unittest.IsolatedAsyncioTestCase hangs on asyncio.CancelledError

[Andrey Moiseev]

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()

--
components: asyncio
messages: 362402
nosy: Andrey Moiseev, asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: unittest.IsolatedAsyncioTestCase hangs on asyncio.CancelledError
type: behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39628] msg.walk memory leak?

[Marco]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antoine Pitrou]

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 
memory instead of going through read() calls.

This makes me think that perhaps this issue isn't as bad: it forces people to 
abandon bad idioms :-)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Ananthakrishnan]

Change by Ananthakrishnan :


--
keywords: +patch
pull_requests: +17959
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/18590

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Ananthakrishnan]

Ananthakrishnan  added the comment:

Thanks for the hint.Made changes.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Eric V. Smith]

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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antoine Pitrou]

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
versions: +Python 3.9 -Python 3.7, Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antoine Pitrou]

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


--
nosy: +pitrou

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Mirwi]

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 steps into Python and may be mislead. In that case, 
sorry for the fuzz.

--
assignee: docs@python
components: Documentation
messages: 362395
nosy: docs@python, mirwi
priority: normal
severity: normal
status: open
title: Tutorial, 5.6 Looping Techniques, sorted() example
type: enhancement
versions: Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Stefan Krah]

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
_decimal does not recognize them (it usually produces exact results
in the respective cases but still sets Inexact).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Vedran Čačić]

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" I think "except" or "alas":-) should 
have been.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Ananthakrishnan]

Ananthakrishnan  added the comment:

Yes I know.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Tal Einat]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Tal Einat]

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: +taleinat

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39576] Surprising MemoryError in `decimal` with MAX_PREC

[Stefan Krah]

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 $SOMEWHAT_MATHEMATICAL_SPEC_EXCEPT_FOR_INEXACT_POWER except 
for inexact power."


Bur GNU is not UNIX and all that... ;)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39704] Disable code coverage

[Karthikeyan Singaravelan]

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?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39704] Disable code coverage

[Stefan Krah]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com