[issue41236] "about" button in MacOS caused an error

[Ned Deily]

Ned Deily  added the comment:

Terry, based on the error message provided, i.e. "About Widget Demo", I assumed 
that the poster was not using IDLE here. But we can't tell without more input.

"when I run 3.9 test.pythoninfo, I am asked to install gcc tools and maybe 
xcode.  Is this expected?"

When doing Python development on macOS, you will need to have the 
Apple-supplied development tools installed and ones appropriate for the macOS 
release. As the Developer's Guide explains 
(https://devguide.python.org/setup/#macos-and-os-x), the necessary tools are 
available if you install the full Xcode development environment from the Mac 
App Store but that's a big download and most of it is not necessary for just 
cpython work. If you haven't already downloaded Xcode, then the first time you 
(or, in this case test.pythoninfo) try to use one of the development tools from 
the terminal shell command line, macOS offers to download and install a 
lightweight subset of what's available in Xcode, called the Command Line Tools. 
 You can also force the installation of the CLT by using "xcode-select 
--install". Once the CLT are installed, they are normally automatically updated 
as needed by the macOS Software Update process.

--

___
Python tracker 

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

[issue41277] documentation: os.setxattr() errno EEXIST and ENODATA

[Pablo Dumas]

New submission from Pablo Dumas :

Shouldn't os.setxattr() errno EEXIST be when "XATTR_CREATE was specified, and 
the attribute exists already" and errno ENODATA be when "XATTR_REPLACE was 
specified, and the attribute does not exist."? In the current os module 
documentation, it's the other way around: "If XATTR_REPLACE is given and the 
attribute does not exist, EEXISTS will be raised. If XATTR_CREATE is given and 
the attribute already exists, the attribute will not be created and ENODATA 
will be raised."... Thanks!

--
messages: 373516
nosy: w0rthle$$
priority: normal
severity: normal
status: open
title: documentation: os.setxattr() errno EEXIST and ENODATA
type: behavior
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

[issue41276] Min / Max returns different values depending on parameter order

[Calvin Davis]

Calvin Davis  added the comment:

Thank you for the clarification, sorry for the report! You're awesome!

--

___
Python tracker 

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

[issue41276] Min / Max returns different values depending on parameter order

[Steven D'Aprano]

Steven D'Aprano  added the comment:

In your first example, `min([(-5, 2), (0, 2)])` the min() function compares the 
two tuples and finds that the first one is lexicographically smaller:

py> (-5, 2) < (0, 2)
True

so (-5, 2) is considered the minimum. In the second example, using the key 
function compares 2 with 2, but since they are equal, the *first* tuple wins 
and is considered the minimum, and so using the key function doesn't change the 
result.

In your third example, after reversing the list, you have `min([(0, 2), (-5, 
2)])` and the min() function compares the two tuples and finds the *second* 
tuple is the smaller:

py> (0, 2) < (-5, 2)
False

But in the fourth example, using the key function, yet again the comparison 
compares 2 with 2 and finds them equal, and so the *first* tuple wins and (0, 
2) is declared the minimum.

When using the key function, only the second item of the tuple is looked at; 
the first item is ignored. So the difference between 0 and -5 is irrelevant, 
and the tie is decided by which element was seen first.

--

___
Python tracker 

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

[issue41276] Min / Max returns different values depending on parameter order

[Steven D'Aprano]

Steven D'Aprano  added the comment:

This is correct behaviour. What makes you think otherwise?

For future bug reports, please don't post screen shots of text, copy and paste 
the text into the body of your bug report.

Posting screenshots makes it difficult for us to copy and run your code, and 
discriminates against the blind and visually impaired who may be reading this 
with a screen-reader, which doesn't not work with images.

--
nosy: +steven.daprano
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

[issue41276] Min / Max returns different values depending on parameter order

[Calvin Davis]

New submission from Calvin Davis :

See attached image

The behavior of min() (and probably max and other related functions) changes 
depending on the order of the parameters it sorts.

In the image, I sorted two tuples, coordinate points, with the same Y value and 
different X values. When the X values were in increasing order, finding the 
minimum x value and minimum y value were the same. However if the list was 
reversed, finding the minimum x and y values in the list provided different 
results.

--
assignee: terry.reedy
components: IDLE
files: yqzRk0Y.png
messages: 373512
nosy: Calvin Davis, terry.reedy
priority: normal
severity: normal
status: open
title: Min / Max returns different values depending on parameter order
type: behavior
versions: Python 3.7
Added file: https://bugs.python.org/file49314/yqzRk0Y.png

___
Python tracker 

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

[issue32528] Change base class for futures.CancelledError

[Guido van Rossum]

Guido van Rossum  added the comment:

Can you send a PR against what’s new 3.8?

On Fri, Jul 10, 2020 at 20:14 JustAnotherArchivist 
wrote:

>
> JustAnotherArchivist  added the comment:
>
> As another datapoint, this also broke some of my code on 3.8 because I was
> using `concurrent.futures.CancelledError` rather than
> `asyncio.CancelledError` to handle cancelled futures. And I'm certainly not
> the only one to have done this given that it's mentioned in at least two
> Stack Overflow answers: https://stackoverflow.com/a/38655063 and
> https://stackoverflow.com/a/36277556
>
> While I understand the rationale behind this change, it would've been good
> to include this inheritance detail in the 3.8 release notes.
>
> --
> nosy: +JustAnotherArchivist
>
> ___
> Python tracker 
> 
> ___
>
-- 
--Guido (mobile)

--

___
Python tracker 

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

[issue32528] Change base class for futures.CancelledError

[JustAnotherArchivist]

JustAnotherArchivist  added the comment:

As another datapoint, this also broke some of my code on 3.8 because I was 
using `concurrent.futures.CancelledError` rather than `asyncio.CancelledError` 
to handle cancelled futures. And I'm certainly not the only one to have done 
this given that it's mentioned in at least two Stack Overflow answers: 
https://stackoverflow.com/a/38655063 and https://stackoverflow.com/a/36277556

While I understand the rationale behind this change, it would've been good to 
include this inheritance detail in the 3.8 release notes.

--
nosy: +JustAnotherArchivist

___
Python tracker 

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

[issue41202] Allow to provide custom exception handler to asyncio.run()

[Kyle Stanley]

Kyle Stanley  added the comment:

> Should I set status for this issue for closed with resolution rejected ?

I'll proceed with closing the issue.

> Should I delete branch on my forked git repo ?
> Can I delete my forked git repo ?

Might as well delete the branch, but the forked repo might be useful to keep 
around should you choose to open a PR to CPython in the future (although you 
can also just create a new one later). If you are interested in working on 
something else in the future, I'd recommend looking at the "newcomer 
friendly"/"easy" issues, or just looking for an existing open issue that you're 
interested in helping with. In most cases, working with a clearly defined issue 
is much easier than trying to propose a new one and getting it merged.

--
resolution:  -> wont fix
stage: patch review -> 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

[issue41265] lzma/bz2 module: inefficient buffer growth algorithm

[Ma Lin]

Ma Lin  added the comment:

Maybe the zlib module can also use the same algorithm.

zlib module's initial buffer size is 16KB [1], each time the size doubles [2].

[1] zlib module's initial buffer size:
https://github.com/python/cpython/blob/v3.9.0b4/Modules/zlibmodule.c#L32

[2] zlib module buffer growth algorithm:
https://github.com/python/cpython/blob/v3.9.0b4/Modules/zlibmodule.c#L174

--
nosy: +inada.naoki, rhettinger

___
Python tracker 

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

[issue41228] Fix the typo in the description of calendar.monthcalendar(year, month)

[Terry J. Reedy]

Change by Terry J. Reedy :


--
resolution:  -> fixed
stage: patch review -> 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

[issue41236] "about" button in MacOS caused an error

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Messages like this are an occasional nuisance when shutting down a tkinter app 
started in a terminal/console window.  I have gone to a lot of effort to 
suppress than in IDLE GUI tests so that other developers do not suffer the 
noise or puzzlement of thinking that there maybe was a test failure.

I can get them now *occasionally* if I start IDLE from a Windows console, open 
multiple windows, and close by right clicking the toolbar icon and selecting 
"Close all Windows" instead of closing properly by closing each window or 
selecting File => Exit.  I consider trying to fix this shutdown buglet to be 
low priority.  

When starting IDLE from an IDLE icon, any such messages go to /dev/NULL. 

After experimenting, I believe Baozhen started IDLE from Terminal with 'python3 
-m idlelib'.  The top menu then has second entry "Python" instead of "IDLE" 
with first item "About Python" instead of "About IDLE".  But it brings up the 
"About IDLE" tk dialog box.  I also suspect  there was some shutdown action, so 
we must know every user action needed to reproduce the issue, and then see if 
it occurs in 3.8 or later. 

Ned, when I run 3.9 test.pythoninfo, I am asked to install gcc tools and maybe 
xcode.  Is this expected?

--
nosy: +terry.reedy

___
Python tracker 

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

[issue41220] add optional make_key argument to lru_cache

[Felipe Rodrigues]

Felipe Rodrigues  added the comment:

Correction: (...) on the _caller_ to solve the hashing* issue (...)

--

___
Python tracker 

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

[issue41220] add optional make_key argument to lru_cache

[Felipe Rodrigues]

Felipe Rodrigues  added the comment:

Hello all,

I love discussions about caching! While I do see the point of Itayazolay's 
proposal, I think that it should be on the _caller_ to solve the caching issue, 
and not on the _callee_ to provide a way to make it happen.

That is, I think that if one wants to use a cache, they should make sure their 
arguments are hashable and not that we should modify called functions to 
provide workarounds for those.

--
nosy: +fbidu

___
Python tracker 

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

[issue41275] Clarify whether Futures can be awaited multiple times

[JustAnotherArchivist]

New submission from JustAnotherArchivist :

While the situation is clear regarding coroutine objects (#25887), as far as I 
can see, the documentation doesn't specify whether asyncio.Futures can be 
awaited multiple times. The code has always (at least since the integration 
into CPython) allowed for it since Future.__await__ simply returns 
Future.result() if it is already done. Is this guaranteed/intended behaviour, 
as also implied by some of the comments on #25887, or is it considered an 
implementation detail?

Here are the only two things I found in the documentation regarding this:

> library/asyncio-task: When a Future object is awaited it means that the 
> coroutine will wait until the Future is resolved in some other place.

> library/asyncio-future: Future is an awaitable object. Coroutines can await 
> on Future objects until they either have a result or an exception set, or 
> until they are cancelled.

Neither of these say anything about awaiting a Future that is already resolved, 
i.e. has a result, has an exception, or was cancelled.

If this is intended to be guaranteed, it should be mentioned in the Future 
documentation. If it is considered an implementation detail, it's probably not 
necessary to explicitly mention this anywhere, but it might be a good idea to 
add another line to e.g. the asyncio.wait example on how to correctly retrieve 
the result of an already-awaited Future/Task.

--
components: asyncio
messages: 373504
nosy: JustAnotherArchivist, asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: Clarify whether Futures can be awaited multiple times
type: enhancement

___
Python tracker 

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

[issue41234] Remove symbol.sym_name

[Terry J. Reedy]

Terry J. Reedy  added the comment:

I verified that import symbol works in 3.9 and raises in 3.10.  So yes, doc and 
its reference should have gone too.  Good catch.

--
nosy: +terry.reedy

___
Python tracker 

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

[issue41273] asyncio: proactor read transport: use recv_into instead of recv

[Tony]

Change by Tony :


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

___
Python tracker 

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

[issue41228] Fix the typo in the description of calendar.monthcalendar(year, month)

[miss-islington]

miss-islington  added the comment:


New changeset c77f71f9819022fa3adeb2f710e564a392ff24c6 by Miss Islington (bot) 
in branch '3.8':
bpo-41228: Fix /a/are/ in monthcalendar() descripton (GH-21372)
https://github.com/python/cpython/commit/c77f71f9819022fa3adeb2f710e564a392ff24c6


--

___
Python tracker 

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

[issue41228] Fix the typo in the description of calendar.monthcalendar(year, month)

[miss-islington]

miss-islington  added the comment:


New changeset a77b1f6b5bb3b76cb913e62ad68f5fd803d515bd by Miss Islington (bot) 
in branch '3.9':
bpo-41228: Fix /a/are/ in monthcalendar() descripton (GH-21372)
https://github.com/python/cpython/commit/a77b1f6b5bb3b76cb913e62ad68f5fd803d515bd


--

___
Python tracker 

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

[issue41233] Missing links to errnos on Built-in Exceptions page

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Only 3.8+ for bug fixes.

--
nosy: +terry.reedy
versions:  -Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

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

[issue41232] Python `functools.wraps` doesn't deal with defaults correctly

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Is this actually a bugfix?

--
nosy: +terry.reedy
versions: +Python 3.10 -Python 3.8

___
Python tracker 

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

[issue41229] Asynchronous generator memory leak

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Only 3.8+ for bug fixes.

--
nosy: +terry.reedy

___
Python tracker 

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

[issue41231] Type annotations lost when using wraps by default

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Only 3.8+ for bug fixes.

--
nosy: +terry.reedy
versions:  -Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

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

[issue41228] Fix the typo in the description of calendar.monthcalendar(year, month)

[miss-islington]

Change by miss-islington :


--
pull_requests: +20587
pull_request: https://github.com/python/cpython/pull/21441

___
Python tracker 

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

[issue41228] Fix the typo in the description of calendar.monthcalendar(year, month)

[miss-islington]

Change by miss-islington :


--
keywords: +patch
nosy: +miss-islington
nosy_count: 3.0 -> 4.0
pull_requests: +20586
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/21440

___
Python tracker 

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

[issue41229] Asynchronous generator memory leak

[Terry J. Reedy]

Change by Terry J. Reedy :


--
versions:  -Python 3.6, Python 3.7

___
Python tracker 

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

[issue41228] Fix the typo in the description of calendar.monthcalendar(year, month)

[Terry J. Reedy]

Terry J. Reedy  added the comment:


New changeset 344dce312a0cf86d5a5772d54843cc179acaf6e3 by Nima Dini in branch 
'master':
bpo-41228: Fix /a/are/ in monthcalendar() descripton (GH-21372)
https://github.com/python/cpython/commit/344dce312a0cf86d5a5772d54843cc179acaf6e3


--
nosy: +terry.reedy

___
Python tracker 

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

[issue41212] Emoji Unicode failing in standard release of Python 3.8.3 / tkinter 8.6.8

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Python internally uses an encoding system that represents all unicode chars 
efficiently, including O(1) indexing.  It is not utf-8, which does not do O(1) 
indexing.

There is already an issue about upgrading (separately) the Python Windows and 
macOS installers to install tcl/tk 8.6.9.

With the currrent 8.6.9 and probably earlier, and since an important tkinter 
patch last fall for #13153, a tkinter/tk text widget will display astral 
characters that the font in use can produce.  For example, in 3.9.0, I see the 
TV set printed in IDLE
>>> '\U0001f4bb'
'💻'
but not in the Windows Console Python REPL, which shows 'box space box box'.

However, astral characters discombobutate editing (#39126),at least on Windows, 
they are counted as 2 or 4 chars.  The difference between behavior before and 
after Serhiy's patch and between display and editing likely explains different 
reports on SO.

--
nosy: +terry.reedy
resolution:  -> third party
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

[issue41004] [CVE-2020-14422] Hash collisions in IPv4Interface and IPv6Interface

[Jesús Cea Avión]

Change by Jesús Cea Avión :


--
nosy: +jcea

___
Python tracker 

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

[issue41274] Better way to random.seed()?

[Steven D'Aprano]

Steven D'Aprano  added the comment:

This is definitely cool though. It might make a really sweet example in the 
demos that come with Python, or in the tutorial, showcasing both the 
awesomeness of HelioViewer and how to use Python to connect to web APIs.

https://github.com/python/cpython/tree/master/Tools/demo

--
nosy: +steven.daprano

___
Python tracker 

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

[issue41259] Find adverbs is not correct on the documentation

[Raymond Hettinger]

Raymond Hettinger  added the comment:

I think it's fine as-is.  The real purpose of the example is show basic 
patterns in writing regexes.  Pig-latin examples or searching for words ending 
in -ly make for nice beginner examples.   I like the OP's modification because 
it teaches a general skill (the importance of \b for making sure you get whole 
words).

We could add a link to the Natural Language Toolkit for people who are getting 
serious about searching for parts of speech.

--

___
Python tracker 

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

[issue41274] Better way to random.seed()?

[Juan Jimenez]

Juan Jimenez  added the comment:

Thanks Rémi. :)

--

___
Python tracker 

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

[issue41274] Better way to random.seed()?

[Raymond Hettinger]

Raymond Hettinger  added the comment:

Marking as closed for these reasons listed by Rémi Lapeyre.

Also note that the default is to use a system source of entropy.  Time is only 
used as a fallback if such as source is unavailable.

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

[issue41274] Better way to random.seed()?

[Raymond Hettinger]

Raymond Hettinger  added the comment:

> is it possible to write a new module that overrides the seed()
> method in the random library in its initialization code and 
> replaces it with this method of seeding the generator?

Yes.  The simplest way is override seed() in a subclass.  You can put that 
subclass in a new module if you like and can even call the class "Random" if 
desired.

>>> class InputRandom(random.Random):
def seed(self, a=None):
if a is None:
a = int(input('Enter a seed: '))
super().seed(a)


>>> r = InputRandom()
Enter a seed: 1234
>>> r.random()
0.9664535356921388
>>> r.random()
0.4407325991753527
>>> r.seed()
Enter a seed: 1234
>>> r.random()
0.9664535356921388
>>> r.seed(1234)
>>> r.random()
0.9664535356921388

--
nosy: +rhettinger

___
Python tracker 

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

[issue41274] Better way to random.seed()?

[Juan Jimenez]

Juan Jimenez  added the comment:

I'm not a Python guru, but I was wondering, is it possible to write a new 
module that overrides the seed() method in the random library in its 
initialization code and replaces it with this method of seeding the generator?

--

___
Python tracker 

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

[issue41274] Better way to random.seed()?

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

Hi, this is very specific and I don't think a way to seed the random generator 
using a third uncontrolled party will get merged in Python. You should probably 
try to package this as a third party library.

--
nosy: +remi.lapeyre

___
Python tracker 

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

[issue41274] Better way to random.seed()?

[Juan Jimenez]

New submission from Juan Jimenez :

I have invented a new way to seed the random number generator with about as 
random a source of seeds as can be found: hashes generated from high cadence, 
high resolution images of the surface of the Sun. These are captured by the 
Solar Dynamics Observatory's (SDO) Atmospheric Imaging Assembly's (AIA) cameras 
at various frequencies. I wrote the POC code in Python and can be seen at 
https://github.com/flybd5/heliorandom. The HelioViewer project liked the idea 
and modified their API to do essentially what my POC code does at 
https://api.helioviewer.org/?action=getRandomSeed. Perhaps a solarseed() call 
could be created for the library to get seeds that way rather than from the 
system clock?

--
components: Library (Lib)
messages: 373487
nosy: flybd5
priority: normal
severity: normal
status: open
title: Better way to random.seed()?
type: enhancement
versions: Python 3.10

___
Python tracker 

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

[issue41270] NamedTemporaryFile is not its own iterator.

[Tony]

Change by Tony :


--
nosy: +tontinton
nosy_count: 3.0 -> 4.0
pull_requests: +20585
pull_request: https://github.com/python/cpython/pull/21439

___
Python tracker 

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

[issue41272] New clause in FOR and WHILE instead of ELSE

[Eric V. Smith]

Eric V. Smith  added the comment:

You should bring this up on the python-ideas mailing list so that it gets more 
visibility.

--
nosy: +eric.smith

___
Python tracker 

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

[issue41256] activate script created by venv is not smart enough

[Eric V. Smith]

Eric V. Smith  added the comment:

Changing versions to those that are currently receiving support.

--
nosy: +eric.smith
versions:  -Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

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

[issue41253] unittest -h shows a flag -s but it doesn't work

[Eric V. Smith]

Eric V. Smith  added the comment:

This appears to just be a misunderstanding: -s is a flag to "unittest 
discover", not to "unittest" itself. I think this is clear from the help text, 
so I'm closing this.

If I'm incorrect, let me know.

--
nosy: +eric.smith
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

[issue41273] asyncio: proactor read transport: use recv_into instead of recv

[Tony]

New submission from Tony :

Using recv_into instead of recv in the transport _loop_reading will speed up 
the process.

>From what I checked it's about 120% performance increase.

This is only because there should not be a new buffer allocated each time we 
call recv, it's really wasteful.

--
messages: 373483
nosy: tontinton
priority: normal
severity: normal
status: open
title: asyncio: proactor read transport: use recv_into instead of recv

___
Python tracker 

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

[issue41261] 3.9-dev SEGV in object_recursive_isinstance in ast.literal_eval

[Arcadiy Ivanov]

Arcadiy Ivanov  added the comment:

Nevermind, `ast`/`_ast` is not pre-loaded by default, so it's in fact getting 
GC'ed after the first `run_path` is executed.

--

___
Python tracker 

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

[issue41261] 3.9-dev SEGV in object_recursive_isinstance in ast.literal_eval

[Arcadiy Ivanov]

Arcadiy Ivanov  added the comment:

> If sys.modules['_ast'] is cleared and then _ast is imported again, 
> _PyState_AddModule() is called to store the new _ast module instance which 
> calls astmodule_clear() on the old module instance.

I'm confused about this. In the repro below the sys.modules.clear() is indeed 
cleared, but references to all modules are retained. 

Where is the garbage collection/module re-initialization coming from? All of 
the references are live.

--

___
Python tracker 

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

[issue41261] 3.9-dev SEGV in object_recursive_isinstance in ast.literal_eval

[Arcadiy Ivanov]

Arcadiy Ivanov  added the comment:

Yes, indeed, please, because I don't know what I would do for 3.9 if this is 
not fixed. :D

--

___
Python tracker 

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

[issue41272] New clause in FOR and WHILE instead of ELSE

[catrudis]

New submission from catrudis :

ELSE-clause in FOR and WHILE has unclear syntax. I suggest new clause instead:

if COND:
  ...
[elif COND:
  ...]
[else:
  ...]

This IF-clause like must be immediately after FOR- or WHILE-cycle (only comment 
allowed between). It looks like a regular IF, but COND is special.
COND may be "break", "pass" or "finally". "if break:" - if used break-operator 
to exit cycle. "if pass:" - cycle executed 0 times. "if finally:" - cycle 
executed 0 or more times ("pass-case"  is included in "finally-case"). For 
compatibility only "else:" means "if finally:".
It's compatible enhancement. No new keyword. There can be no combination 
"break", "pass" or "finally" after "if"/"elif:" in current version.

--
components: Interpreter Core
messages: 373479
nosy: catrudis
priority: normal
severity: normal
status: open
title: New clause in FOR and WHILE instead of ELSE
type: enhancement

___
Python tracker 

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

[issue36346] Prepare for removing the legacy Unicode C API

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset 4c8f09d7cef8c7aa07d5b5232b5b64f63819a743 by Serhiy Storchaka in 
branch 'master':
bpo-36346: Make using the legacy Unicode C API optional (GH-21437)
https://github.com/python/cpython/commit/4c8f09d7cef8c7aa07d5b5232b5b64f63819a743


--

___
Python tracker 

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

[issue41271] Add support for io_uring to cpython

[Cooper Lees]

New submission from Cooper Lees :

Would adding support for io_uring in Linux to stadlib IO and/or asyncio make 
sense?

More info on io_uring:
- https://kernel.dk/io_uring.pdf
- https://lwn.net/Articles/810414/

--
components: IO
messages: 373477
nosy: cooperlees
priority: normal
severity: normal
status: open
title: Add support for io_uring to cpython
type: enhancement
versions: Python 3.10

___
Python tracker 

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

[issue17490] Improve ast.literal_eval test suite coverage

[Batuhan Taskaya]

Change by Batuhan Taskaya :


--
nosy: +BTaskaya

___
Python tracker 

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

[issue41261] 3.9-dev SEGV in object_recursive_isinstance in ast.literal_eval

[Batuhan Taskaya]

Change by Batuhan Taskaya :


--
nosy: +BTaskaya

___
Python tracker 

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

[issue41261] 3.9-dev SEGV in object_recursive_isinstance in ast.literal_eval

[STINNER Victor]

STINNER Victor  added the comment:

It would be nice to fix this 3.9 regression before 3.9 final.

--
priority: normal -> release blocker

___
Python tracker 

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

[issue20171] Derby #2: Convert 115 sites to Argument Clinic in Modules/_cursesmodule.c

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
resolution:  -> fixed
stage: patch review -> 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

[issue20179] Derby #10: Convert 50 sites to Argument Clinic across 4 files

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
resolution:  -> fixed
stage: patch review -> 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

[issue41270] NamedTemporaryFile is not its own iterator.

[Peter]

Change by Peter :


--
nosy: +maubp

___
Python tracker 

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

[issue39959] Bug on multiprocessing.shared_memory

[David Parks]

David Parks  added the comment:

Having a flag seems like a good solution to me. I've also encountered this 
issue and posted on stack overflow about it here:

https://stackoverflow.com/questions/62748654/python-3-8-shared-memory-resource-tracker-producing-unexpected-warnings-at-appli

--
nosy: +davidparks21

___
Python tracker 

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

[issue20179] Derby #10: Convert 50 sites to Argument Clinic across 4 files

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset 9650fe0197779b4dfded94be111e39c5810f098f by Zackery Spytz in 
branch 'master':
bpo-20179: Convert the _overlapped module to the Argument Clinic (GH-14275)
https://github.com/python/cpython/commit/9650fe0197779b4dfded94be111e39c5810f098f


--

___
Python tracker 

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

[issue39017] Infinite loop in the tarfile module

[Ethan Furman]

Ethan Furman  added the comment:

Absolutely!

But first, you'll need to sign the Contributor License Agreement:

  https://www.python.org/psf/contrib/contrib-form/

Thank you for your help!

--

___
Python tracker 

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

[issue41145] EmailMessage.as_string is altering the message state and actually fix bugs

[R. David Murray]

R. David Murray  added the comment:

The as_strings docs say:

"Flattening the message may trigger changes to the Message if defaults need to 
be filled in to complete the transformation to a string (for example, MIME 
boundaries may be generated or modified)."

So, while this is indeed an API design bug, it isn't an actual bug in the code 
but rather is expected behavior, currently.  The historical reason for this is 
that the generator code looks at the entire message to make sure the boundary 
string is unique.  My long term plan for email included plans to rewrite the 
generator, and I was going to fix this issue at that point.  My life got too 
busy to be able to continue with email development work, though, so that never 
happened.

It has been *years* since I've looked at the code.  Thinking about it now, I'm 
wondering if it would be possible to use a GUID technique to generate the 
boundary and thus do exactly as you say: have make_alternative (and anything 
else that causes a boundary to be needed) pre-create the boundary.  That, I 
think, would mean we wouldn't need to change the generator, even though it 
would still be doing its (inefficient) check that the boundary was unique.  I'm 
not sure if it would work, though; it's been too long since I've looked at the 
relevant code.

--
type: resource usage -> behavior

___
Python tracker 

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

[issue30044] shutil.copystat should (allow to) copy ownership, and other attributes

[Eryk Sun]

Eryk Sun  added the comment:

In Windows, I wouldn't expect shutil.copy2 to preserve the owner and ACLs. They 
change whenever a file gets copied via CopyFileExW [1]. Keeping them exactly as 
in the source file generally requires a privileged backup and restore 
operation, such as via BackupRead [2] and BackupWrite [3]. Unless the caller 
has SeRestorePrivilege, the owner can only be set to one of the SIDs in the 
caller's groups that are flagged as SE_GROUP_OWNER, which is usually just the 
user's SID or, for an admin, the Administrators SID. Also, for copying the 
system ACL, adding or removing audit and scoped-policy-identifier entries 
requires SeSecurityPrivilege.

CopyFileExW copies all data streams in a file, which is typically just the 
anonymous data stream, but an NTFS/ReFS file can have multiple named data 
streams. For metadata, it copies the change and modify timestamps (but not the 
create and access timestamps), file attributes (readonly, hidden, system, 
archive, temporary, not-content-indexed), extended attributes, and resource 
attributes [4]. 

Separating this functionality into shutil.copy and shutil.copystat would be 
fairly involved. These functions could be left as is and just document the 
discrepancy in shutil.copy2, or new functions could be implemented in the nt or 
_winapi module to list the data streams in a file and get/set file attributes 
and system resource attributes. Supporting extended attributes would require 
the native NT API, and for little benefit since they're mostly used for 
"$Kernel." prefixed attributes that can only be set by kernel-mode callers such 
as drivers.

---

[1]: 
https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-copyfileexw
[2]: 
https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-backupread
[3]: 
https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-backupwrite
[4]: Resource attributes are like extended attributes, but a named resource 
attribute is a tuple of one or more items with a given data type (integer, 
string, or bytes) that's stored as an entry in the file's system ACL. Keeping 
them in the SACL allows conditional access/audit entries to reference them in 
an access check or access audit. Unlike audit entries in the SACL, reading and 
writing resource attributes doesn't require SeSecurityPrivilege.

--
nosy: +eryksun

___
Python tracker 

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

[issue41255] Argparse.parse_args exits on unrecognized option with exit_on_error=False

[paul j3]

paul j3  added the comment:

The docs could change 

"catch errors manually"

to

"catch ArgumentError manually"

But while 'argparse.ArgumentError' is imported, it is not documented. We have 
to study the code to learn when it is raised.  

Its class def:

def __init__(self, argument, message):

shows it's tied to a specific 'argument', an Action object.  Most commonly it 
is produced by reraising a ValueError, TypeError or ArgumentTypeError during 
the check_values step.

Unrecognized arguments, and missing required arguments errors aren't produced 
while processing an argument, but rather while checking  things after parsing.  
So they can't raise an ArgumentError, and aren't handled by this new parameter.

I found a old issue that discusses this https://bugs.python.org/issue9938,  
https://github.com/python/cpython/pull/15362

There wasn't much discussion about the scope of this change, or about the 
documentation wording.  My only comment was in 2013, 
https://bugs.python.org/msg192147

Until we iron out the wording I think this patch should be reverted.

While exploring other problems, I thought it would be a good idea of refactor 
parse_known_args and _parse_known_args.  Specifically I'd move the 'required' 
testing and self.error() calls out of _parse_known_args, allowing a developer 
to write their own versions of parse_known_args.  The goal was to make it 
easier to test for mixes of seen and unseen arguments.  

In light of the current issue, we might want to look into consolidating all (or 
at least most) of the calls to self.error() in one function.  Until then, the 
documented idea of modifying the error() method itself is the best 
user/developer tool, 
https://docs.python.org/3.10/library/argparse.html#exiting-methods

--

___
Python tracker 

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

[issue41227] minor typo in asyncio transport protocol

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

Thanks Faris for the report and @ys19991 for the patch. Closing this as fixed.

--
nosy: +xtreak
resolution:  -> fixed
stage: patch review -> 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

[issue36346] Prepare for removing the legacy Unicode C API

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
pull_requests: +20584
pull_request: https://github.com/python/cpython/pull/21437

___
Python tracker 

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

[issue41227] minor typo in asyncio transport protocol

[miss-islington]

Change by miss-islington :


--
pull_requests: +20583
pull_request: https://github.com/python/cpython/pull/21436

___
Python tracker 

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

[issue41227] minor typo in asyncio transport protocol

[miss-islington]

Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 5.0 -> 6.0
pull_requests: +20582
pull_request: https://github.com/python/cpython/pull/21435

___
Python tracker 

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

[issue41268] 3.9-dev regression? TypeError: exec_module() missing 1 required positional argument: 'module'

[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

[issue39017] Infinite loop in the tarfile module

[Rishi]

Rishi  added the comment:

Hi ! I would like to start contributing to CPython. Can I start working on this 
issue ?

--

___
Python tracker 

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

[issue41270] NamedTemporaryFile is not its own iterator.

[Roundup Robot]

Change by Roundup Robot :


--
keywords: +patch
nosy: +python-dev
nosy_count: 1.0 -> 2.0
pull_requests: +20581
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/21434

___
Python tracker 

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

[issue41270] NamedTemporaryFile is not its own iterator.

[Seth Sims]

New submission from Seth Sims :

_TemporaryFileWrapper does not proxy __next__ to the underlying file object. 
There was a discussion on the mailing list in 2016 mentioning this, however it 
seems it was dropped without a consensus. Biopython encountered this issue 
(referenced below) and we agree it violates our assumptions about how the 
NamedTemporaryFile should work. I think it would be fairly trivial to fix by 
just returning `self.file.readline()`

mailing list thread: 
https://mail.python.org/pipermail/python-list/2016-July/862590.html

biopython discussion: https://github.com/biopython/biopython/pull/3031

--
components: Library (Lib)
messages: 373467
nosy: Seth Sims
priority: normal
severity: normal
status: open
title: NamedTemporaryFile is not its own iterator.
type: behavior
versions: Python 3.10, Python 3.5, Python 3.6, 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

[issue41269] Wrong subtraction calculations

[Mark Dickinson]

Mark Dickinson  added the comment:

Thanks for the report. This isn't a Python bug, but a common issue when working 
with floating-point numbers.

I recommend taking a look at this section of the tutorial for more information: 
https://docs.python.org/3.8/tutorial/floatingpoint.html

--
nosy: +mark.dickinson
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

[issue41269] Wrong subtraction calculations

[Ivan]

New submission from Ivan :

I've started to learn python and tried command:
print(-2.989 + 2)
it gives me result of -0.9889
same error can be observed with numbers from 4 and below like:
print(-2.989 + 4)
1.0111

print(-2.989 + 3)
0.01112

print(-2.989 + 1)
-1.9889

Numbers above 4 seam to work fine

--
components: Windows
files: python error.jpg
messages: 373465
nosy: Svabo, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Wrong subtraction calculations
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file49313/python error.jpg

___
Python tracker 

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

[issue41268] 3.9-dev regression? TypeError: exec_module() missing 1 required positional argument: 'module'

[Hugo van Kemenade]

New submission from Hugo van Kemenade :

For the past 3 months we've been testing Pillow on Travis CI using 3.9-dev, 
which Travis builds nightly from the 3.9 branch.

Two days ago the 3.9-dev build passed, but it failed yesterday with the same 
Pillow commit, and all subsequent builds.

* Last pass: https://travis-ci.org/github/python-pillow/Pillow/jobs/706015838
* First fail: https://travis-ci.org/github/hugovk/Pillow/jobs/706476038

Diffing the logs, here's the CPython commits for each:

platform linux 3.9.0b4+ (heads/3.9:edeaf61, Jul  7 2020, 06:29:52)
platform linux 3.9.0b4+ (heads/3.9:1d1c574, Jul  8 2020, 07:05:21)

Diff of those commits:

https://github.com/python/cpython/compare/edeaf61b6827ab3a8673aff1fb7717917f08f003..1d1c5743400bdf384ec83eb6ba5b39a355d121e3

It's also failing with the most recent:

platform linux 3.9.0b4+ (heads/3.9:e689789, Jul  9 2020, 07:57:24)

I didn't see anything obvious to cause it, so thought I'd better report it here 
to be on the safe side.

Our tracking issue: https://github.com/python-pillow/Pillow/issues/4769

Here's the traceback:

Finished processing dependencies for Pillow==7.3.0.dev0
python3 selftest.py
Traceback (most recent call last):
  File "/home/travis/build/hugovk/Pillow/selftest.py", line 6, in 
from PIL import Image, features
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 664, in _load_unlocked
  File "", line 627, in _load_backward_compatible
  File "", line 259, in load_module
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/Pillow-7.3.0.dev0-py3.9-linux-x86_64.egg/PIL/Image.py",
 line 94, in 
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 664, in _load_unlocked
  File "", line 627, in _load_backward_compatible
  File "", line 259, in load_module
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/Pillow-7.3.0.dev0-py3.9-linux-x86_64.egg/PIL/_imaging.py",
 line 8, in 
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/Pillow-7.3.0.dev0-py3.9-linux-x86_64.egg/PIL/_imaging.py",
 line 7, in __bootstrap__
TypeError: exec_module() missing 1 required positional argument: 'module'
Makefile:59: recipe for target 'install-coverage' failed
make: *** [install-coverage] Error 1
Traceback (most recent call last):
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/config/__init__.py",
 line 495, in _importconftest
return self._conftestpath2mod[key]
KeyError: PosixPath('/home/travis/build/hugovk/Pillow/conftest.py')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/opt/python/3.9-dev/lib/python3.9/runpy.py", line 197, in 
_run_module_as_main
return _run_code(code, main_globals, None,
  File "/opt/python/3.9-dev/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pytest/__main__.py",
 line 7, in 
raise SystemExit(pytest.main())
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/config/__init__.py",
 line 105, in main
config = _prepareconfig(args, plugins)
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/config/__init__.py",
 line 257, in _prepareconfig
return pluginmanager.hook.pytest_cmdline_parse(
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/hooks.py",
 line 286, in __call__
return self._hookexec(self, self.get_hookimpls(), kwargs)
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/manager.py",
 line 93, in _hookexec
return self._inner_hookexec(hook, methods, kwargs)
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/manager.py",
 line 84, in 
self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/callers.py",
 line 203, in _multicall
gen.send(outcome)
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/helpconfig.py",
 line 90, in pytest_cmdline_parse
config = outcome.get_result()
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/callers.py",
 line 80, in get_result
raise ex[1].with_traceback(ex[2])
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/pluggy/callers.py",
 line 187, in _multicall
res = hook_impl.function(*args)
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/config/__init__.py",
 line 836, in pytest_cmdline_parse
self.parse(args)
  File 
"/home/travis/virtualenv/python3.9-dev/lib/python3.9/site-packages/_pytest/config/__init__.py",
 line 1044, in parse
self._preparse(args, addopts=addopts)
  File 
"/home/travis/virtualenv/python

[issue41202] Allow to provide custom exception handler to asyncio.run()

[tomaszdrozdz]

tomaszdrozdz  added the comment:

I just wanted to call  

def main():
asyncio.run(...)

But I can go with Your aproach.  
Thanks for discusion.  

Should I set status for this issue for closed with resolution rejected ?  

Should I delete branch on my forked git repo ?
Can I delete my forked git repo ?

--

___
Python tracker 

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

[issue39017] Infinite loop in the tarfile module

[Rishi]

Change by Rishi :


--
nosy: +rishi93

___
Python tracker 

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

[issue41267] Attribute error: Pandas module doesn't have 'Plotting' attribute

[Eric V. Smith]

Eric V. Smith  added the comment:

This bug tracker is for reporting bugs in python, not for getting help using 
python.

I suggest asking for help on the python-list mailing list: 
https://mail.python.org/mailman/listinfo/python-list

Or, since this sounds like you're having problems with pandas, perhaps a 
pandas-specific forum would be better. I'm not familiar with the pandas 
community to know where you should look, sorry.

--
nosy: +eric.smith
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed
type: performance -> 

___
Python tracker 

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

[issue41267] Attribute error: Pandas module doesn't have 'Plotting' attribute

[owais]

New submission from owais :

Hello... I am deploying a django application over the AWS Cloud Server EC2 
windows instance having AMD64 architecture. I have installed python 3.7.6 over 
the server and install all modules (numpy pandas matplotlib django etc) using 
pip. I have set the sqlite server on AWS. I changed the path variables from 
local dir to server dir and also change the database server name. but When I 
run the server from cmd by typing "python manage.py runserver" I am facing an 
issue/error that says pandas module does not have plotting module. Whereas I 
checked in site-pakages under pandas folder, there is a subfolder named as 
'plotting'. I have again installed the newer version of pip by upgrade pip 
command then install the pandas but no success acheived. Kindly help me out I 
am attaching 2 pictures, one is the error and other is project directory where 
all scripts are present.

--
components: Windows
files: Error.zip
messages: 373461
nosy: owais.ali, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Attribute error: Pandas module doesn't have 'Plotting' attribute
type: performance
versions: Python 3.7
Added file: https://bugs.python.org/file49312/Error.zip

___
Python tracker 

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

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

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 8182cc2e68a3c6ea5d5342fed3f1c76b0521fbc1 by Victor Stinner in 
branch 'master':
bpo-39573: Use the Py_TYPE() macro (GH-21433)
https://github.com/python/cpython/commit/8182cc2e68a3c6ea5d5342fed3f1c76b0521fbc1


--

___
Python tracker 

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

[issue41261] 3.9-dev SEGV in object_recursive_isinstance in ast.literal_eval

[STINNER Victor]

Change by STINNER Victor :


--
nosy: +dino.viehland

___
Python tracker 

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

[issue41175] Static analysis issues reported by GCC 10

[miss-islington]

miss-islington  added the comment:


New changeset 51b36ed96d29c9440fbca18fb0c9e3087f763da5 by Miss Islington (bot) 
in branch '3.9':
bpo-41175: Guard against a NULL pointer dereference within bytearrayobject 
(GH-21240)
https://github.com/python/cpython/commit/51b36ed96d29c9440fbca18fb0c9e3087f763da5


--

___
Python tracker 

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

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

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +20580
pull_request: https://github.com/python/cpython/pull/21433

___
Python tracker 

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

[issue41175] Static analysis issues reported by GCC 10

[miss-islington]

miss-islington  added the comment:


New changeset 33672c019179be279ae979f709c974593fbbbe84 by Miss Islington (bot) 
in branch '3.8':
bpo-41175: Guard against a NULL pointer dereference within bytearrayobject 
(GH-21240)
https://github.com/python/cpython/commit/33672c019179be279ae979f709c974593fbbbe84


--

___
Python tracker 

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

[issue41175] Static analysis issues reported by GCC 10

[miss-islington]

Change by miss-islington :


--
pull_requests: +20579
pull_request: https://github.com/python/cpython/pull/21432

___
Python tracker 

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

[issue41175] Static analysis issues reported by GCC 10

[miss-islington]

Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 2.0 -> 3.0
pull_requests: +20578
pull_request: https://github.com/python/cpython/pull/21431

___
Python tracker 

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

[issue41261] 3.9-dev SEGV in object_recursive_isinstance in ast.literal_eval

[STINNER Victor]

STINNER Victor  added the comment:

This bug is a follow-up of bpo-41194: "Python 3.9.0b3 crash on compile() in 
PyAST_Check() when the _ast module is loaded more than once".

--

___
Python tracker 

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

[issue41261] 3.9-dev SEGV in object_recursive_isinstance in ast.literal_eval

[STINNER Victor]

STINNER Victor  added the comment:

Ok, I can reproduce the crash on the 3.9 branch using: ./python repro.py.

The first problem is that astmodule_clear() doesn't reset the initiallized 
member: add "state->initialized = 0;".

The _ast module is special. Not only it has regular module function which 
access the module state, it also has 3 functions in C APIs which are called 
directly:

* PyAST_Check()
* PyAST_mod2obj()
* PyAST_obj2mod()

These functions require to have access to the _ast module. In Python 3.9, I 
chose to use a global state, as it was done in Python 3.8.

If sys.modules['_ast'] is cleared and then _ast is imported again, 
_PyState_AddModule() is called to store the new _ast module instance which 
calls astmodule_clear() on the old module instance.

The problem is that when astmodule_clear() is called, the new instance is 
already created and so exposes the "old" _ast.AST type.

1) import _ast: call init_types() which creates AST type #1
2) del sys.modules['_ast]
3) import _ast: create a new module which exposes AST type #1
3) import _ast: also clears the old module (_PyState_AddModule()) which calls 
astmodule_clear()
4) Calling PyAST_Check() calls init_types() which creates AST type #2: 
PyAST_Check() returns false, since AST type #1 and AST type #2 are different

--

In the master branch, I modified PyAST_Check(), PyAST_mod2obj() and 
PyAST_obj2mod() to import the _ast module and get the state from the module. 
The state is not global in master.

For 3.9, I'm not sure what is the best option:

* Backport master changes (not well tested yet, but is it worse than this known 
crash?)
* Never clear the state: leak references at Python exit.

--

___
Python tracker 

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

[issue38893] broken container/selinux integration

[Christian Heimes]

Change by Christian Heimes :


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

___
Python tracker 

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

[issue41266] Wrong hint when class methods and builtins named same

[wyz23x2]

New submission from wyz23x2 :

There is a function hex(number, /), and float objects have a method hex().
When something like 1.3.hex( is typed, the yellow box's first line contains 
hex(number, /). But the method is actually hex(), no arguments. It confuses 
users.
And when 1.3.list( is typed, there isn't a list() method in floats, but the 
hint still pops up and shows the __doc__ for list(iterable=(), /).

--
assignee: terry.reedy
components: IDLE
messages: 373455
nosy: terry.reedy, wyz23x2
priority: normal
severity: normal
status: open
title: Wrong hint when class methods and builtins named same
versions: Python 3.10, 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

[issue41265] lzma/bz2 module: inefficient buffer growth algorithm

[Ma Lin]

New submission from Ma Lin :

lzma/bz2 modules are using the same buffer growth algorithm: [1][2]

newsize = size + (size >> 3) + 6;

lzma/bz2 modules' default output buffer is 8192 bytes [3][4], so the growth 
step is below.

For many cases, maybe the buffer is resized too many times.
Is it possible to design a new growth algorithm that grows faster when the size 
is not very large.

  1: 8,196 bytes
  2: 9,226 bytes
  3: 10,385 bytes
  4: 11,689 bytes
  5: 13,156 bytes
  6: 14,806 bytes
  7: 16,662 bytes
  8: 18,750 bytes
  9: 21,099 bytes
 10: 23,742 bytes
 11: 26,715 bytes
 12: 30,060 bytes
 13: 33,823 bytes
 14: 38,056 bytes
 15: 42,819 bytes
 16: 48,177 bytes
 17: 54,205 bytes
 18: 60,986 bytes
 19: 68,615 bytes
 20: 77,197 bytes
 21: 86,852 bytes
 22: 97,714 bytes
 23: 109,934 bytes
 24: 123,681 bytes
 25: 139,147 bytes
 26: 156,546 bytes
 27: 176,120 bytes
 28: 198,141 bytes
 29: 222,914 bytes
 30: 250,784 bytes
 31: 282,138 bytes
 32: 317,411 bytes
 33: 357,093 bytes
 34: 401,735 bytes
 35: 451,957 bytes
 36: 508,457 bytes
 37: 572,020 bytes
 38: 643,528 bytes
 39: 723,975 bytes
 40: 814,477 bytes
 41: 916,292 bytes
 42: 1,030,834 bytes
 43: 1,159,694 bytes
 44: 1,304,661 bytes
 45: 1,467,749 bytes
 46: 1,651,223 bytes
 47: 1,857,631 bytes
 48: 2,089,840 bytes
 49: 2,351,076 bytes
 50: 2,644,966 bytes
 51: 2,975,592 bytes
 52: 3,347,547 bytes
 53: 3,765,996 bytes
 54: 4,236,751 bytes
 55: 4,766,350 bytes
 56: 5,362,149 bytes
 57: 6,032,423 bytes
 58: 6,786,481 bytes
 59: 7,634,797 bytes
 60: 8,589,152 bytes
 61: 9,662,802 bytes
 62: 10,870,658 bytes
 63: 12,229,496 bytes
 64: 13,758,189 bytes
 65: 15,477,968 bytes
 66: 17,412,720 bytes
 67: 19,589,316 bytes
 68: 22,037,986 bytes
 69: 24,792,740 bytes
 70: 27,891,838 bytes
 71: 31,378,323 bytes
 72: 35,300,619 bytes
 73: 39,713,202 bytes
 74: 44,677,358 bytes
 75: 50,262,033 bytes
 76: 56,544,793 bytes
 77: 63,612,898 bytes
 78: 71,564,516 bytes
 79: 80,510,086 bytes
 80: 90,573,852 bytes
 81: 101,895,589 bytes
 82: 114,632,543 bytes
 83: 128,961,616 bytes
 84: 145,081,824 bytes
 85: 163,217,058 bytes
 86: 183,619,196 bytes
 87: 206,571,601 bytes
 88: 232,393,057 bytes
 89: 261,442,195 bytes
 90: 294,122,475 bytes
 91: 330,887,790 bytes
 92: 372,248,769 bytes
 93: 418,779,871 bytes
 94: 471,127,360 bytes
 95: 530,018,286 bytes
 96: 596,270,577 bytes
 97: 670,804,405 bytes
 98: 754,654,961 bytes
 99: 848,986,837 bytes
100: 955,110,197 bytes

[1] lzma buffer growth algorithm:
https://github.com/python/cpython/blob/v3.9.0b4/Modules/_lzmamodule.c#L133

[2] bz2 buffer growth algorithm:
https://github.com/python/cpython/blob/v3.9.0b4/Modules/_bz2module.c#L121

[3] lzma default buffer size:
https://github.com/python/cpython/blob/v3.9.0b4/Modules/_lzmamodule.c#L124

[4] bz2 default buffer size:
https://github.com/python/cpython/blob/v3.9.0b4/Modules/_bz2module.c#L109

--
components: Library (Lib)
messages: 373454
nosy: malin
priority: normal
severity: normal
status: open
title: lzma/bz2 module: inefficient buffer growth algorithm
type: performance
versions: Python 3.10

___
Python tracker 

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

[issue41075] Make support of navigating through prev. commands in IDLE more conspicuous

[wyz23x2]

Change by wyz23x2 :


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

[issue41145] EmailMessage.as_string is altering the message state and actually fix bugs

[Eric V. Smith]

Change by Eric V. Smith :


--
components: +email
nosy: +barry, r.david.murray

___
Python tracker 

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

[issue35350] importing "ctypes" immediately causes a segmentation fault

[Christian Heimes]

Christian Heimes  added the comment:

Python 2.7 has reached its end of lifetime. Please re-open the bug if you can 
reproduce the issue on Python 3.8 or newer.

--
nosy: +christian.heimes
resolution:  -> out of date
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

[issue26328] shutil._copyxattr() function shouldn't fail if setting security.selinux xattr fails

[Christian Heimes]

Christian Heimes  added the comment:

I'm marking this as duplicate of #38893. The other bug has more information.

--
nosy: +christian.heimes
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> broken container/selinux integration

___
Python tracker 

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

[issue38893] broken container/selinux integration

[Christian Heimes]

Change by Christian Heimes :


--
assignee:  -> christian.heimes
versions: +Python 3.10 -Python 3.7

___
Python tracker 

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

[issue38893] broken container/selinux integration

[Christian Heimes]

Christian Heimes  added the comment:

The issue came up at $WORK now. Core utils like copy command ignore 
"security.selinux" xattr unless the user explicitly asks to preserve the 
security context, see

https://github.com/coreutils/coreutils/blob/6a3d2883fed853ee01079477020091068074e12d/src/copy.c#L867-L891
https://github.com/philips/attr/blob/1cc88bd4c17ef99ace22c8be362d513f155b1387/libattr/attr_copy_fd.c#L109-L111

_copyxattr() ignores most errnos that are listed in the man page of setxattr(2) 
but not EACCES. The man page of setxattr(2) also points to stat(2) which lists 
EACCES as possible errno.

I see three simple and two more complicated solutions:

1) ignore EACCES completely
2) ignore EACCES for "security.selinux"
3) ignore EACCES for "security.*"
4) provide a callback similar to the check() callback in libattr's 
attr_copy_fd(). Only copy an xattr when the callback is not set or returns True.
5) provide an extra option to skip security context

Related: https://bugs.python.org/issue24564#msg351555 also suggests that 
copyxattr should ignore ENOSYS in listxattr. Some file systems (NFS?) seem to 
lack xattr.

Hynek, you implemented most of copyxattr in 0beab058dd4 back in 2013. What's 
your opinion?

--
nosy: +hynek

___
Python tracker 

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

[issue36346] Prepare for removing the legacy Unicode C API

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset d878349bac6c154fbfeffe7d4b38e2ddb833f135 by Serhiy Storchaka in 
branch 'master':
bpo-36346: Do not use legacy Unicode C API in ctypes. (#21429)
https://github.com/python/cpython/commit/d878349bac6c154fbfeffe7d4b38e2ddb833f135


--

___
Python tracker 

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

[issue40982] copytree example in shutil

[Wansoo Kim]

Wansoo Kim  added the comment:

Can I solve this issue?

--
nosy: +ys19991

___
Python tracker 

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

[issue41264] Do not use the name of the built-in function as a variable.

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

We usually do not accept pure cosmetic changes.

--
nosy: +serhiy.storchaka
resolution:  -> not a bug
stage: patch review -> 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

[issue20257] test_socket fails if using tipc module and SELinux enabled

[Christian Heimes]

Christian Heimes  added the comment:

The bug report is over six years ago and I haven't seen any TIPC related issues 
for a while. The test suite has additional guards to skip TIPC tests when the 
Kernel module is not loaded.

--
nosy: +christian.heimes
resolution:  -> out of date
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

[issue24163] shutil.copystat fails when attribute security.selinux is present

[Christian Heimes]

Christian Heimes  added the comment:

I'm marking this as duplicate of #38893 because the newer bug contains more 
information.

--
nosy: +christian.heimes
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> broken container/selinux integration

___
Python tracker 

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

[issue30044] shutil.copystat should (allow to) copy ownership, and other attributes

[Christian Heimes]

Christian Heimes  added the comment:

POSIX ACLs and SELinux context information are stored in extended file 
attributes. The information is copied from source to destination. POSIX ACLs 
are stored in xattr "system.posix_acl_access" and SELinux context in xattr 
"security.selinux".

--
keywords: +easy
nosy: +christian.heimes
stage:  -> needs patch
versions: +Python 3.10 -Python 3.7

___
Python tracker 

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

[issue36346] Prepare for removing the legacy Unicode C API

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
pull_requests: +20576
pull_request: https://github.com/python/cpython/pull/21429

___
Python tracker 

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