date:20200703



miss-islington  added the comment:


New changeset 6857ebefc048e316f948091946d337b5ada807a4 by Miss Islington (bot) 
in branch '3.8':
bpo-33864: Clarify the docs for typing.ByteString (GH-21311)
https://github.com/python/cpython/commit/6857ebefc048e316f948091946d337b5ada807a4


--

___
Python tracker 

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

[issue33864] collections.abc.ByteString does not register memoryview



miss-islington  added the comment:


New changeset 1cbcf9833f26588a16b5b69d202df727dbd09968 by Miss Islington (bot) 
in branch '3.9':
bpo-33864: Clarify the docs for typing.ByteString (GH-21311)
https://github.com/python/cpython/commit/1cbcf9833f26588a16b5b69d202df727dbd09968


--

___
Python tracker 

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

[issue33864] collections.abc.ByteString does not register memoryview



Change by miss-islington :


--
pull_requests: +20465
pull_request: https://github.com/python/cpython/pull/21313

___
Python tracker 

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

[issue33864] collections.abc.ByteString does not register memoryview



Change by miss-islington :


--
pull_requests: +20464
pull_request: https://github.com/python/cpython/pull/21312

___
Python tracker 

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

[issue33864] collections.abc.ByteString does not register memoryview



miss-islington  added the comment:


New changeset b40e434386cd94a367d4a256e3364771140160e7 by Zackery Spytz in 
branch 'master':
bpo-33864: Clarify the docs for typing.ByteString (GH-21311)
https://github.com/python/cpython/commit/b40e434386cd94a367d4a256e3364771140160e7


--
nosy: +miss-islington

___
Python tracker 

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

[issue33864] collections.abc.ByteString does not register memoryview

2020-07-03 Thread Zackery Spytz



Change by Zackery Spytz :


--
keywords: +patch
nosy: +ZackerySpytz
nosy_count: 5.0 -> 6.0
pull_requests: +20463
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/21311

___
Python tracker 

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

[issue41205] Documentation Decimal power 0 to the 0 is Nan (versus 0 to the 0 which is 1)

2020-07-03 Thread Tim Peters



Tim Peters  added the comment:

Huh! I thought everyone in Standards World gave up by now, and agreed 0**0 
should be 1.

--
nosy: +tim.peters

___
Python tracker 

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

a bit feedback for JSON documents

2020-07-03 Thread 황병희

There is some comment for
https://docs.python.org/3.10/library/json.html.

The latest RFC number is 8259. 

Thanks,

Sincerely, JSON fan Byung-Hee

-- 
^고맙습니다 _白衣從軍_ 감사합니다_^))//
-- 
https://mail.python.org/mailman/listinfo/python-list

[issue41192] Some audit events are undocumented

2020-07-03 Thread Saiyang Gou



Change by Saiyang Gou :


--
pull_requests: +20462
pull_request: https://github.com/python/cpython/pull/21310

___
Python tracker 

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

[issue41205] Documentation Decimal power 0 to the 0 is Nan (versus 0 to the 0 which is 1)

2020-07-03 Thread 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

[issue41203] Replace references to OS X in documentation with macOS

2020-07-03 Thread Karthikeyan Singaravelan



Change by Karthikeyan Singaravelan :


--
components: +macOS
nosy: +ned.deily, ronaldoussoren

___
Python tracker 

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

[issue41207] distutils.command.build_ext raises FileNotFoundError

2020-07-03 Thread Jason R. Coombs



Change by Jason R. Coombs :


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

[issue41207] distutils.command.build_ext raises FileNotFoundError

2020-07-03 Thread Jason R. Coombs



New submission from Jason R. Coombs :

In [pypa/setuptools#2228](https://github.com/pypa/setuptools/issues/2228), by 
adopting the distutils codebase from a late release of CPython, Setuptools 
stumbled onto an API-breaking change in distutils rooted at issue39763.

Details are in the Setuptools investigation, but to summarize:

- distutils.ccompiler.CCompiler.compile declares "raises CompileError on 
failure" and calls `self._compile`, implemented by subclasses.
- In at least `distutils.unixcompiler.UnixCCompiler._compile`, 
`distutils.spawn.spawn` is called (through CCompiler.spawn).
- Since GH-18743, `distutils.spawn.spawn` calls `subprocess.Popen` which raises 
FileNotFoundError when the target executable doesn't exist.
- Programs trapping CompileError but not FileNotFoundError will crash where 
once they had error handling.

Setuptools discovered this behavior in the 48.0 release when it incorporated 
these distutils changes into a vendored release of Setuptools, but the failures 
exhibited will apply to all builds (including pyyaml) on Python 3.9.

--
assignee: lukasz.langa
components: Distutils
keywords: 3.9regression
messages: 372973
nosy: dstufft, eric.araujo, jaraco, lukasz.langa
priority: release blocker
severity: normal
status: open
title: distutils.command.build_ext raises FileNotFoundError
type: crash
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

[issue39763] distutils.spawn should use subprocess (hang in parallel builds on QNX)

2020-07-03 Thread Jason R. Coombs



Jason R. Coombs  added the comment:

I've flagged issue41207 as a regression stemming from this effort.

--
nosy: +jaraco

___
Python tracker 

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

[issue41165] [Python 3.10] Remove APIs deprecated long enough

2020-07-03 Thread Inada Naoki



Change by Inada Naoki :


--
keywords: +patch
pull_requests: +20461
pull_request: https://github.com/python/cpython/pull/21309

___
Python tracker 

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

[issue41192] Some audit events are undocumented

2020-07-03 Thread Saiyang Gou



Saiyang Gou  added the comment:

I've created PR 21308 for this. BTW, is issue 39567 (`os.walk`, `os.fwalk`, 
`pathlib.Path.glob` and `pathlib.Path.rglob`) intentionally not backported to 
3.8?

--

___
Python tracker 

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

[issue41192] Some audit events are undocumented

2020-07-03 Thread Saiyang Gou



Change by Saiyang Gou :


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

___
Python tracker 

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

[RELEASE] Python 3.9.0b4 is now ready for testing

2020-07-03 Thread Łukasz Langa

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I’m pleased to announce the release of 
Python 3.9.0b4. Get it here:

https://www.python.org/downloads/release/python-390b4/ 


This is a beta preview of Python 3.9

Python 3.9 is still in development. This release, 3.9.0b4, is the fourth of 
five planned beta release previews.

Beta release previews are intended to give the wider community the opportunity 
to test new features and bug fixes and to prepare their projects to support the 
new feature release.

Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.9 during the beta phase and report issues found to the Python bug tracker 
 as soon as possible. While the release is planned to 
be feature complete entering the beta phase, it is possible that features may 
be modified or, in rare cases, deleted up until the start of the release 
candidate phase (2020-08-10). Our goal is have no ABI changes after beta 5 and 
as few code changes as possible after 3.9.0rc1, the first release candidate. To 
achieve that, it will be extremely important to get as much exposure for 3.9 as 
possible during the beta phase.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.

Major new features of the 3.9 series, compared to 3.8

Some of the new major new features and changes in Python 3.9 are:

PEP 584 , Union Operators in dict

PEP 585 , Type Hinting Generics In 
Standard Collections

PEP 593 , Flexible function and 
variable annotations

PEP 602 , Python adopts a stable 
annual release cadence

PEP 615 , Support for the IANA Time 
Zone Database in the Standard Library

PEP 616 , String methods to remove 
prefixes and suffixes

PEP 617 , New PEG parser for CPython

BPO 38379 , garbage collection does not 
block on resurrected objects;

BPO 38692 , os.pidfd_open added that allows 
process management without races and signals;

BPO 39926 , Unicode support updated to 
version 13.0.0;

BPO 1635741 , when Python is initialized 
multiple times in the same process, it does not leak memory anymore;

A number of Python builtins (range, tuple, set, frozenset, list, dict) are now 
sped up using PEP 590  vectorcall;

A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, 
_functools, _json, _locale, operator, resource, time, _weakref) now use 
multiphase initialization as defined by PEP 489 
;

A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 .

(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know .)

The next pre-release, the fifth beta release of Python 3.9, will be 3.9.0b5. It 
is currently scheduled for 2020-07-20.

More resources

Online Documentation 
PEP 596 , 3.9 Release Schedule
Report bugs at https://bugs.python.org .
Help fund Python and its community .
Your friendly release team,
Ned Deily @nad 
Steve Dower @steve.dower 
Łukasz Langa @ambv 
___
Python-announce-list mailing list -- python-announce-list@python.org
To unsubscribe send an email to python-announce-list-le...@python.org
https://mail.python.org/mailman3/lists/python-announce-list.python.org/
Member address: arch...@mail-archive.com

[RELEASE] Python 3.9.0b4 is now ready for testing

2020-07-03 Thread Łukasz Langa

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I’m pleased to announce the release of 
Python 3.9.0b4. Get it here:

https://www.python.org/downloads/release/python-390b4/ 


This is a beta preview of Python 3.9

Python 3.9 is still in development. This release, 3.9.0b4, is the fourth of 
five planned beta release previews.

Beta release previews are intended to give the wider community the opportunity 
to test new features and bug fixes and to prepare their projects to support the 
new feature release.

Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.9 during the beta phase and report issues found to the Python bug tracker 
 as soon as possible. While the release is planned to 
be feature complete entering the beta phase, it is possible that features may 
be modified or, in rare cases, deleted up until the start of the release 
candidate phase (2020-08-10). Our goal is have no ABI changes after beta 5 and 
as few code changes as possible after 3.9.0rc1, the first release candidate. To 
achieve that, it will be extremely important to get as much exposure for 3.9 as 
possible during the beta phase.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.

Major new features of the 3.9 series, compared to 3.8

Some of the new major new features and changes in Python 3.9 are:

PEP 584 , Union Operators in dict

PEP 585 , Type Hinting Generics In 
Standard Collections

PEP 593 , Flexible function and 
variable annotations

PEP 602 , Python adopts a stable 
annual release cadence

PEP 615 , Support for the IANA Time 
Zone Database in the Standard Library

PEP 616 , String methods to remove 
prefixes and suffixes

PEP 617 , New PEG parser for CPython

BPO 38379 , garbage collection does not 
block on resurrected objects;

BPO 38692 , os.pidfd_open added that allows 
process management without races and signals;

BPO 39926 , Unicode support updated to 
version 13.0.0;

BPO 1635741 , when Python is initialized 
multiple times in the same process, it does not leak memory anymore;

A number of Python builtins (range, tuple, set, frozenset, list, dict) are now 
sped up using PEP 590  vectorcall;

A number of Python modules (_abc, audioop, _bz2, _codecs, _contextvars, _crypt, 
_functools, _json, _locale, operator, resource, time, _weakref) now use 
multiphase initialization as defined by PEP 489 
;

A number of standard library modules (audioop, ast, grp, _hashlib, pwd, 
_posixsubprocess, random, select, struct, termios, zlib) are now using the 
stable ABI defined by PEP 384 .

(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know .)

The next pre-release, the fifth beta release of Python 3.9, will be 3.9.0b5. It 
is currently scheduled for 2020-07-20.

More resources

Online Documentation 
PEP 596 , 3.9 Release Schedule
Report bugs at https://bugs.python.org .
Help fund Python and its community .
Your friendly release team,
Ned Deily @nad 
Steve Dower @steve.dower 
Łukasz Langa @ambv 
-- 
https://mail.python.org/mailman/listinfo/python-list

[issue41206] behaviour change with EmailMessage.set_content

2020-07-03 Thread David Bremner



New submission from David Bremner :

Works in 3.8.3, but not in 3.8.4rc1

from email.message import EmailMessage
msg = EmailMessage()
msg.set_content("")

Apparently now at least one newline is required.

--
components: email
messages: 372971
nosy: barry, bremner, r.david.murray
priority: normal
severity: normal
status: open
title: behaviour change with EmailMessage.set_content
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

[issue41204] Use of unitialized variable `fields` along error path in code generated from asdl_c.py



Change by STINNER Victor :


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

___
Python tracker 

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

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath



Change by STINNER Victor :


--
pull_requests: +20458
pull_request: https://github.com/python/cpython/pull/21306

___
Python tracker 

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

[issue41162] Clear audit hooks after destructors



Steve Dower  added the comment:


New changeset b9e288cc1bfd583e887f784e38d9c511b43c0c3a by Steve Dower in branch 
'3.8':
bpo-41162: Clear audit hooks later during finalization (GH-21222)
https://github.com/python/cpython/commit/b9e288cc1bfd583e887f784e38d9c511b43c0c3a


--

___
Python tracker 

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

[issue41205] Documentation Decimal power 0 to the 0 is Nan (versus 0 to the 0 which is 1)

2020-07-03 Thread JD-Veiga


New submission from JD-Veiga :

Hi,

I would like to propose a minor addition to `decimal` package documentation 
page (https://docs.python.org/3/library/decimal.html). I think that we should 
add a paragraph in `context.power(x, y, modulo=None)` stating that `Decimal(0) 
** Decimal(0)` returns `Decimal('NaN')` instead of `1` --as `0 ** 0` does-- or 
`1.0` --in case of `0.0 ** 0.0`.

Indeed, `0 ** 0` is `NaN` is mentioned as example of operations raising 
`InvalidOperation` exceptions.

However, I think that this is not enough to indicate the different behaviour of 
decimal versus int and float numbers.

Moreover, in the case of `%` and `//` operators, there are clear remarks on 
these differences (See: “There are some small differences between arithmetic on 
Decimal objects and arithmetic on integers and floats [...]” in the page).

Thank you and sorry for the inconvenience.

--
assignee: docs@python
components: Documentation
messages: 372969
nosy: JD-Veiga, docs@python
priority: normal
severity: normal
status: open
title: Documentation Decimal power 0 to the 0 is Nan (versus 0 to the 0 which 
is 1)
type: enhancement
versions: Python 3.10, 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

[issue41173] Windows ARM buildbots cannot upload results



Change by Steve Dower :


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

___
Python tracker 

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

[issue21222] Mock create_autospec with name argument fails



Steve Dower  added the comment:


New changeset 941117aaa32bf8b02c739ad848ac727292f75b05 by Steve Dower in branch 
'3.9':
bpo-21222: Fix improperly merged change so that final hooks are called before 
types are cleared (GH-21304)
https://github.com/python/cpython/commit/941117aaa32bf8b02c739ad848ac727292f75b05


--

___
Python tracker 

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

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath



Change by Steve Dower :


--
pull_requests:  -20454

___
Python tracker 

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

[issue41162] Clear audit hooks after destructors



Change by Steve Dower :


--
pull_requests: +20456
pull_request: https://github.com/python/cpython/pull/21304

___
Python tracker 

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

[issue21222] Mock create_autospec with name argument fails



Change by Steve Dower :


--
nosy: +steve.dower
nosy_count: 3.0 -> 4.0
pull_requests: +20455
pull_request: https://github.com/python/cpython/pull/21304

___
Python tracker 

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

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath



Change by Steve Dower :


--
pull_requests: +20454
pull_request: https://github.com/python/cpython/pull/21304

___
Python tracker 

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

[issue21222] Mock create_autospec with name argument fails



Change by Steve Dower :


--
nosy:  -steve.dower

___
Python tracker 

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

[issue21222] Mock create_autospec with name argument fails



Change by Steve Dower :


--
pull_requests:  -20453

___
Python tracker 

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

Re: New to python - Just a question

2020-07-03 Thread Tim Chase

On 2020-07-03 10:09, Daley Okuwa via Python-list wrote:
> Write an algorithm (choose the language you prefer) that given a
> character string, for instance {‘c’,’a’,’i’,’o’,’p’,’a’}, will
> print out the list of characters appearing at least 2 times. In
> this specific example, it would return {‘a’}. Afterwards, comment
> out the cost in terms of space and time.

What have you tried already?  Where are you having trouble?

Have you written a program that accepts a character string?  Is the
string coming in as a command-line argument or on standard-input?

The example string you give looks more like some sort of
serialization format rather than a string.

Are you having difficulty counting the letters?  Python provides a
"dict()" type that would work well.

Should uppercase letters be counted the same as lowercase letters?
I.e., should "Pop" report that there are 2 "p"s?

If you've counted the duplicates, 

Have you studied space/time complexity and do you know how to
evaluate code for these characteristics?  The problem should be
solvable in roughly O(k) per word.

> Write a bash/python script that takes a directory as an argument
> and output the total lines of code in *.cpp files recursively.

Again, what have you tried?

Have you been able to iterated over a directory? See find(1) or ls(1)
or grep(1) in a shell-script or os.listdir()/os.scandir()/glob.glob()
in Python

Have you been able to open those files?

Can you iterate over the lines in each file?

Do you need to filter out any lines (such as blank lines or comments)?

If you provide what you've tried, folks here on the list are pretty
happy to help.  But most won't do your homework for you.

-tkc

-- 
https://mail.python.org/mailman/listinfo/python-list

[issue41199] Docstring convention not followed for dataclasses documentation page

2020-07-03 Thread Eric V. Smith



Change by Eric V. Smith :


--
keywords: +newcomer friendly -patch

___
Python tracker 

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

[issue41162] Clear audit hooks after destructors



Change by Steve Dower :


--
pull_requests: +20452
pull_request: https://github.com/python/cpython/pull/21303

___
Python tracker 

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

[issue21222] Mock create_autospec with name argument fails



Change by Steve Dower :


--
nosy: +steve.dower
nosy_count: 3.0 -> 4.0
pull_requests: +20453
pull_request: https://github.com/python/cpython/pull/21304

___
Python tracker 

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

[issue33327] Add a method to move messages to IMAPlib

2020-07-03 Thread Matej Cepl



Matej Cepl  added the comment:

Sorry, UIDPLUS capability.

--

___
Python tracker 

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

[issue33327] Add a method to move messages to IMAPlib

2020-07-03 Thread Matej Cepl


Matej Cepl  added the comment:

1. no this has not been included anywhere, just in the unfinished PR on GitHub
2. only thing which I was fighting to get into Python (and I did) was 
https://bugs.python.org/issue6 but that’s another issue (without this whole 
discussion here would not be even possible), it is now part of the upstream 
Python
3. are you certain that the IMAP server in question supports MOVE command? 
(have you noticed all that business with CAPABILITIES and particularly the UID 
one?)

--

___
Python tracker 

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

[issue41162] Clear audit hooks after destructors



Steve Dower  added the comment:


New changeset e1d4fdc53347617bea1aff0d7112471453f65003 by Steve Dower in branch 
'3.9':
bpo-41162: Clear audit hooks later during finalization (GH-21222)
https://github.com/python/cpython/commit/e1d4fdc53347617bea1aff0d7112471453f65003


--

___
Python tracker 

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

[issue41192] Some audit events are undocumented



Steve Dower  added the comment:

Maybe we need to add a page for "undocumented" events? I really don't want to 
document the _ctypes or _winapi modules - those should remain internal-only.

Maybe we can add a section to the end of the audit_events.rst file for "other 
events"? The generation of that page happens in two separate passes, so it 
should be safe enough.

It might even be possible to just provide the events and specify "" instead of 
the anchor to disable the backlink completely? I don't remember whether I coded 
that up or not.

--

___
Python tracker 

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

[issue41204] Use of unitialized variable `fields` along error path in code generated from asdl_c.py

2020-07-03 Thread Brad Larsen



New submission from Brad Larsen :

In commit b1cc6ba73 from earlier today, an error-handling path can now read an 
uninitialized variable.

https://github.com/python/cpython/commit/b1cc6ba73a51d5cc3aeb113b5e7378fb50a0e20a#diff-fa7f27df4c8df1055048e78340f904c4R695-R697

In particular, asdl_c.py is used to generate C source, and when building that 
code with Clang 10, there is the attached warning.

Likely fix: initialize `fields` to `NULL`. Also, perhaps a CI loop that has 
`-Werror=sometimes-uninitialized` would help detect these.

Compiler warning:

Python/Python-ast.c:1147:9: warning: variable 'fields' is used uninitialized 
whenever 'if' condition is true [-Wsometimes-uninitialized]
if (state == NULL) {
^
Python/Python-ast.c:1210:16: note: uninitialized use occurs here
Py_XDECREF(fields);
   ^~
./Include/object.h:520:51: note: expanded from macro 'Py_XDECREF'
#define Py_XDECREF(op) _Py_XDECREF(_PyObject_CAST(op))
  ^~
./Include/object.h:112:41: note: expanded from macro '_PyObject_CAST'
#define _PyObject_CAST(op) ((PyObject*)(op))
^~
Python/Python-ast.c:1147:5: note: remove the 'if' if its condition is always 
false
if (state == NULL) {
^~~~
Python/Python-ast.c:1145:35: note: initialize the variable 'fields' to silence 
this warning
PyObject *key, *value, *fields;
  ^
   = NULL
1 warning generated.

--
components: Interpreter Core
messages: 372963
nosy: blarsen, vstinner
priority: normal
severity: normal
status: open
title: Use of unitialized variable `fields` along error path in code generated 
from asdl_c.py
type: compile error
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

[issue39542] Cleanup object.h header

2020-07-03 Thread Raymond Hettinger


Raymond Hettinger  added the comment:

PyTuple_Check() got slower across the board.  This is problematic because the 
principal use case for PyTuple_Check() is as a guard for various fast paths.

The direct cause of the degradation is that the inlining of PyType_Check() 
didn't go so well — commit 509dd90f4684e40af3105dd3e754fa4b9c1530c1. 

There are two issues.  First, we lost the fast path for an exact type match 
that was present in the 3.8 version of PyType_Check().  Second, functions like 
PyType_Check() cannot be fully inlined if they call other non-inlined functions 
like PyType_GetFlags().

The original unreviewed commit doesn't revert cleanly because subsequent 
changes were made.  Instead, I suggest:

* restore the short-cut for an exact type match, and
* convert PyType_GetFlags() to a macro or an inlined function

That would fix the performance regression while still treating type objects as 
opaque.

--- Incomplete inlines --
--- line 639 in object.h 

static inline int
PyType_HasFeature(PyTypeObject *type, unsigned long feature) {
return ((PyType_GetFlags(type) & feature) != 0);
}
   ^ Non-static function cannot be inlined

#define PyType_FastSubclass(type, flag) PyType_HasFeature(type, flag)

static inline int _PyType_Check(PyObject *op) {
return PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_TYPE_SUBCLASS);
}
#define PyType_Check(op) _PyType_Check(_PyObject_CAST(op))


--- Old Type Check Code -
--- line 646 in object.h 

#define PyObject_TypeCheck(ob, tp) \
(Py_TYPE(ob) == (tp) || PyType_IsSubtype(Py_TYPE(ob), (tp)))
 ^--- Fast path for exact match is now gone


--- Non-static function cannot be inlined --
--- line 2339 in typeobject.c  -

unsigned long
PyType_GetFlags(PyTypeObject *type)
{
return type->tp_flags;
}

--
nosy: +lukasz.langa, petr.viktorin, pitrou, rhettinger
priority: normal -> high
status: closed -> open

___
Python tracker 

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

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath



Steve Dower  added the comment:

Bumping to release blocker and adding RMs. Should definitely get this fix 
merged within the next week, and I don't want the next round of releases to go 
out without it.

--
nosy: +lukasz.langa, ned.deily
priority: normal -> release blocker
versions:  -Python 3.5

___
Python tracker 

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

[issue41162] Clear audit hooks after destructors



Change by Steve Dower :


--
pull_requests: +20451
pull_request: https://github.com/python/cpython/pull/21302

___
Python tracker 

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

[issue41180] marshal load bypass code.new audit event



miss-islington  added the comment:


New changeset 1c776541a8805576c0a4363ca28c1d29423f02f6 by Miss Islington (bot) 
in branch '3.9':
bpo-41180: Audit code.__new__ when unmarshalling (GH-21271)
https://github.com/python/cpython/commit/1c776541a8805576c0a4363ca28c1d29423f02f6


--

___
Python tracker 

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

[issue41192] Some audit events are undocumented

2020-07-03 Thread Christian Heimes



Change by Christian Heimes :


--
nosy: +christian.heimes

___
Python tracker 

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

[issue41180] marshal load bypass code.new audit event



miss-islington  added the comment:


New changeset c1d916595eb6979d4d87cc3e5216e26b3c6fac25 by Miss Islington (bot) 
in branch '3.8':
bpo-41180: Audit code.__new__ when unmarshalling (GH-21271)
https://github.com/python/cpython/commit/c1d916595eb6979d4d87cc3e5216e26b3c6fac25


--

___
Python tracker 

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

[issue41162] Clear audit hooks after destructors



Steve Dower  added the comment:


New changeset daa0fe03a517d335d48e65ace8e5da636e265a8f by Konge in branch 
'master':
bpo-41162: Clear audit hooks later during finalization (GH-21222)
https://github.com/python/cpython/commit/daa0fe03a517d335d48e65ace8e5da636e265a8f


--

___
Python tracker 

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

[issue41180] marshal load bypass code.new audit event



Change by miss-islington :


--
pull_requests: +20450
pull_request: https://github.com/python/cpython/pull/21301

___
Python tracker 

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

[issue41180] marshal load bypass code.new audit event



Steve Dower  added the comment:


New changeset d160e0f8e283d0a8737644588b38e8c6a07c134f by tkmikan in branch 
'master':
bpo-41180: Audit code.__new__ when unmarshalling (GH-21271)
https://github.com/python/cpython/commit/d160e0f8e283d0a8737644588b38e8c6a07c134f


--

___
Python tracker 

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

[issue41180] marshal load bypass code.new audit event



Change by miss-islington :


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

___
Python tracker 

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

[issue41180] marshal load bypass code.new audit event



Steve Dower  added the comment:

Ah, you're right. Thanks for double checking me :)

I'll merge the PR and do the backports. Thanks!

--

___
Python tracker 

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

[issue33327] Add a method to move messages to IMAPlib

2020-07-03 Thread Hans-Peter Jansen



Hans-Peter Jansen  added the comment:

If I'm not mistaken, this is applied to the openSUSE TW version of Python. 
For some reason, this seems to not play well with .uid('move',...)
on a cyrus imap server (v2.4.19). Is that to be expected?

```
2020-07-03 18:04:05  INFO: [imap_reorg] move b'10399' from 2017-01-01 
06:30:35+02:00 to INBOX.2017
Traceback (most recent call last):
  File "./imap_reorg.py", line 431, in 
sys.exit(main())
  File "./imap_reorg.py", line 425, in main
return process()
  File "./imap_reorg.py", line 133, in trace_and_call
result = func(*args, **kwargs)
  File "./imap_reorg.py", line 358, in process
ret |= reorg.run_expr(expr)
  File "./imap_reorg.py", line 345, in run_expr
return method(*args)
  File "./imap_reorg.py", line 328, in yearly
ret = self.imap.uid('move', uid, dest)
  File "/usr/lib64/python3.8/imaplib.py", line 881, in uid
typ, dat = self._simple_command(name, command, *args)
  File "/usr/lib64/python3.8/imaplib.py", line 1205, in _simple_command
return self._command_complete(name, self._command(name, *args))
  File "/usr/lib64/python3.8/imaplib.py", line 1030, in _command_complete
raise self.error('%s command error: %s %s' % (name, typ, data))
imaplib.error: UID command error: BAD [b'Unrecognized UID subcommand']
```

--
nosy: +frispete

___
Python tracker 

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

[issue41198] Round built-in function not shows zeros acording significant figures and calculates different numbers of odd and even

2020-07-03 Thread Tim Peters



Tim Peters  added the comment:

Thanks, Mark! I didn't even know __round__ had become a dunder method.

For the rest, I'll follow StackOverflow - I don't have an instant answer, and 
the instant answers I _had_ didn't survive second thoughts ;-)

--

___
Python tracker 

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

[issue41176] revise Tkinter mainloop dispatching flag behavior

2020-07-03 Thread Richard Sheridan



Change by Richard Sheridan :


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

___
Python tracker 

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

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath



Change by Steve Dower :


--
pull_requests: +20447
pull_request: https://github.com/python/cpython/pull/21298

___
Python tracker 

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

[issue41110] 2to3 reports some files as both not changing and having been modified

2020-07-03 Thread SilentGhost



Change by SilentGhost :


--
nosy: +benjamin.peterson
type:  -> behavior
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

[issue38731] bad input crashes py_compile library

2020-07-03 Thread Hubert Pineault



Hubert Pineault  added the comment:

Thanks Joannah, I confirm this is a duplicate of 
https://bugs.python.org/issue40456

The issue is better tracked in 40456, so you can close here.

--

___
Python tracker 

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

Making and seeing mistakes [was: Formal Question to Steering Council]

2020-07-03 Thread Ethan Furman


On 07/03/2020 11:57 AM, Jon Ribbens via Python-list wrote:

On 2020-07-03, Michael Torrie  wrote:



All you needed to say was, "No, she did not conflate 'White' with race."
  To say "[I] did," is a very odd thing, and certainly inaccurate. I
definitely did not conflate White with race.  Why do you think that?


Because you conflated the name of the author and race in the post
I was responding to.


That is ridiculous.  It is possible to see someone else's mistake without 
making it oneself.

Michael's mistake was assuming that the author had, in fact, conflated the 
names.

Your mistake is to assume that since the author did not make that mistake that 
Michael must have made it.

I'm sure somebody will point out what my mistake was.

Can we now drop this subthread?

--
~Ethan~
--
https://mail.python.org/mailman/listinfo/python-list

[issue41199] Docstring convention not followed for dataclasses documentation page

2020-07-03 Thread Eric V. Smith



Change by Eric V. Smith :


--
pull_requests:  -20437

___
Python tracker 

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

Re: Formal Question to Steering Council (re recent PEP8 changes)

On 2020-07-03, Michael Torrie  wrote:
> On 7/3/20 10:57 AM, Jon Ribbens via Python-list wrote:
>> On 2020-07-03, Ethan Furman  wrote:
>>> On 07/02/2020 07:42 PM, Jon Ribbens via Python-list wrote:
 She didn't - you did.
>>>
>>> Please keep the discourse civil.  Petty taunts are not helpful.
>> 
>> Sorry, I don't understand what you are getting at. My comment was not
>> a "petty taunt", it was an important factual correction, and perfectly
>> civil - more so than the post it was a response to.
>> 
>> (I'll concede my second post repeating it in response to "Come again?"
>> was somewhat facetious though ;-) )
>
> All you needed to say was, "No, she did not conflate 'White' with race."
>  To say "[I] did," is a very odd thing, and certainly inaccurate. I
> definitely did not conflate White with race.  Why do you think that?

Because you conflated the name of the author and race in the post
I was responding to.
-- 
https://mail.python.org/mailman/listinfo/python-list

[issue41198] Round built-in function not shows zeros acording significant figures and calculates different numbers of odd and even

2020-07-03 Thread Mark Dickinson



Mark Dickinson  added the comment:

Just for fun, I posted a Stack Overflow question: 
https://stackoverflow.com/q/62721186/270986

Let's close this here.

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

[issue41203] Replace references to OS X in documentation with macOS

2020-07-03 Thread Patrick Reader



New submission from Patrick Reader :

Since 10.12 (Sierra, released in 2016), macOS is no longer called OS X. 
References to macOS in the documentation should be updated to reflect this. 
This is now especially important because macOS 11 (Big Sur) is now in preview, 
and the X meaning 10 in roman numerals is now completely incorrect (not just 
the wrong name).

--
assignee: docs@python
components: Documentation
messages: 372951
nosy: docs@python, pxeger
priority: normal
severity: normal
status: open
title: Replace references to OS X in documentation with macOS
type: behavior

___
Python tracker 

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

[issue41194] Python 3.9.0b3 crash on compile() in PyAST_Check() when the _ast module is loaded more than once



STINNER Victor  added the comment:

I cannot reproduce msg372859 crash anymore. I tested 3.9 and master branches. I 
close the issue.

Thanks Arcadiy Ivanov for testing beta releases ;-)

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

Re: Formal Question to Steering Council (re recent PEP8 changes)

2020-07-03 Thread Terry Reedy


On 7/2/2020 6:46 PM, Random832 wrote:
 how much of that discussion you've actually read), but the point is 
that the *whole idea* of "standard English" is tied to white supremacy, 
not any particular standard whether via its authors or otherwise.


France has the French Academy to protect the purity of the French 
languages and reject foreign words.  Spain similarly has a Royal Academy 
to regulate what is Castilian (Spanish Spanish).  In ancient Bharata 
(India), about 2000 years ago, a 'cabal' of grammatcians, exemplified by 
Panini, defined Sanskrit.  English is much more fluid and much more open 
to including foreign words and influences, including from 'non-white' 
peoples.



--
Terry Jan Reedy

--
https://mail.python.org/mailman/listinfo/python-list

[issue41194] Python 3.9.0b3 crash on compile() in PyAST_Check() when the _ast module is loaded more than once



STINNER Victor  added the comment:


New changeset b1cc6ba73a51d5cc3aeb113b5e7378fb50a0e20a by Victor Stinner in 
branch 'master':
bpo-41194: Convert _ast extension to PEP 489 (GH-21293)
https://github.com/python/cpython/commit/b1cc6ba73a51d5cc3aeb113b5e7378fb50a0e20a


--

___
Python tracker 

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

Re: Formal Question to Steering Council (re recent PEP8 changes)

2020-07-03 Thread Dieter Maurer

Random832 wrote at 2020-7-2 18:46 -0400:
> ... the *whole idea* of "standard English" is tied to white supremacy, not 
> any particular standard whether via its authors or otherwise.

PEP 8 was initially designed as a style specification for
Python's runtime library. I hope we can agree that
all documentation in Python's runtime library should use
(some) standard English - understandable by any typical English speaker
- and not some English dialect spoken and understood only in some
parts of the world.


PEP 8 has been adopted meanwhile by many external projects.
Those projects might choose a different language and
maybe even an English dialect. However, if the project
want to be international, "standard English" (in contrast
to an English dialect) has its advantages.
-- 
https://mail.python.org/mailman/listinfo/python-list

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath



Change by Steve Dower :


--
keywords: +patch
pull_requests: +20446
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/21297

___
Python tracker 

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

[issue40874] Update to libmpdec-2.5.0



Stefan Krah  added the comment:

How witty!

--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> behavior

___
Python tracker 

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

[issue40874] Update to libmpdec-2.5.0

2020-07-03 Thread Christian Heimes



Christian Heimes  added the comment:

Are you saying that you are not follow advises and guidelines of the developer 
guide?

--

___
Python tracker 

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

Re: Formal Question to Steering Council (re recent PEP8 changes)

2020-07-03 Thread Michael Torrie

On 7/3/20 10:57 AM, Jon Ribbens via Python-list wrote:
> On 2020-07-03, Ethan Furman  wrote:
>> On 07/02/2020 07:42 PM, Jon Ribbens via Python-list wrote:
>>> She didn't - you did.
>>
>> Please keep the discourse civil.  Petty taunts are not helpful.
> 
> Sorry, I don't understand what you are getting at. My comment was not
> a "petty taunt", it was an important factual correction, and perfectly
> civil - more so than the post it was a response to.
> 
> (I'll concede my second post repeating it in response to "Come again?"
> was somewhat facetious though ;-) )

All you needed to say was, "No, she did not conflate 'White' with race."
 To say "[I] did," is a very odd thing, and certainly inaccurate. I
definitely did not conflate White with race.  Why do you think that?  As
others helpfully pointed out, the context for her comments was out of
band (not on this list).  Thus she was not conflating anything.  If we
want to go in circles, sure I did conflate that she conflated.

thanks.
-- 
https://mail.python.org/mailman/listinfo/python-list

[issue40874] Update to libmpdec-2.5.0



Stefan Krah  added the comment:

> Finally, while Raymond and Antoine are welcome to voice their opinions on the 
> matter, your change is landing in 3.9.0b4 which I'm about to announce. So we 
> won't be reverting it. In the future let's make sure we stick to the release 
> calendar to avoid similar heat. If we need to bend a rule or two, that's 
> okay, it happens. Making a fellow core developer stamp your change in such 
> case will increase visibility, and is a good practice regardless, required 
> for example in avionics software.

I've added Antoine, Mark and Raymond because they know the history of
libmpdec, unlike people who came later.

Like for libffi, it is not feasible to get review, because there is
no time.  This would effectively mean that nothing ever changes.

The alternative is to trust that the zero fault situation continues.

Or download *one* of the gigantic test suites, which I have laboriously
updated for this release:

http://www.bytereef.org/software/mpdecimal/releases/mpdecimal-testit-2.5.0.tar.gz

The second one isn't even published.


So again, just clamoring for review (which often is just rubber
stamping) leads to nothing but scoring a few cheap points.

--

___
Python tracker 

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

Re: New to python - Just a question

2020-07-03 Thread Rhodri James

On 03/07/2020 11:09, Daley Okuwa via Python-list wrote:

Please can someone help

Write an algorithm (choose the language you prefer) that given a character
string, for instance {‘c’,’a’,’i’,’o’,’p’,’a’}, will print out the list of
characters appearing at least 2 times. In this specific example, it would
return {‘a’}. Afterwards, comment out the cost in terms of space and time.

The first thing to do with any problem is to break it down into bits.
In the case of Python, writing them out as "pseudo-code" instructions
often helps. In this case you have:

Set up something to count letters with
For each letter in the string:
If we haven't seen this letter before:
Set the counter for the letter to 1
Else:
Add 1 to the counter for the letter

For each counter:
If the count is 2 or more:
Print the letter

Now there are a lot of possible ways to write that, but they mostly come
down to deciding what data structure to use to count letters with. Have
a browse through a tutorial (or the standard library if you are feeling
adventurous) and see what you think might work, then try it.

Write a bash/python script that takes a directory as an argument and output the
total lines of code in *.cpp files recursively.

In bash, what existing commands count things? If you don't know, how
might you find out? Then you have to figure out how to do that for each
*.cpp file in a directory, and add the totals together.

In Python, you can read a file one line at a time, so how to count the
number of lines in a file should be pretty obvious. Figuring out how to
do that for every *.cpp file in a directory will involve looking through
the standard library, or getting a bash script to do it for you :-)

--
Rhodri James *-* Kynesim Ltd
--
https://mail.python.org/mailman/listinfo/python-list

[issue41110] 2to3 reports some files as both not changing and having been modified

2020-07-03 Thread Ashley Whetter



Change by Ashley Whetter :


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

___
Python tracker 

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

Re: Formal Question to Steering Council (re recent PEP8 changes)

On 2020-07-03, Ethan Furman  wrote:
> On 07/02/2020 07:42 PM, Jon Ribbens via Python-list wrote:
>> She didn't - you did.
>
> Please keep the discourse civil.  Petty taunts are not helpful.

Sorry, I don't understand what you are getting at. My comment was not
a "petty taunt", it was an important factual correction, and perfectly
civil - more so than the post it was a response to.

(I'll concede my second post repeating it in response to "Come again?"
was somewhat facetious though ;-) )
-- 
https://mail.python.org/mailman/listinfo/python-list

[issue40874] Update to libmpdec-2.5.0



Stefan Krah  added the comment:

Finally, about the Debian issue, of course you could also link 3.8
against the static lib.

--

___
Python tracker 

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

[issue40874] Update to libmpdec-2.5.0


Stefan Krah  added the comment:

Łukasz, which one is nicer?

> reverting this patch passes all the tests, what's the motivation and why were 
> there no code reviews for this?

or:

> Yeah, I already felt a bit guilty about adding you -- it could be a compiler 
> bug or an actual overflow.  My bet is also that the reordering exposes an 
> existing overflow.  The reordering itself certainly looks correct to me.



I'm always astonished that some of the CoC proponents (and reporters)
have little idea about actual politeness, a fact which is a main source
of friction.


Hint: I'd prefer actual politeness.

--

___
Python tracker 

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

Re: Formal Question to Steering Council (re recent PEP8 changes)

2020-07-03 Thread Ethan Furman


On 07/02/2020 07:42 PM, Jon Ribbens via Python-list wrote:


She didn't - you did.


Please keep the discourse civil.  Petty taunts are not helpful.

--
~Ethan~
Python List Moderator
--
https://mail.python.org/mailman/listinfo/python-list

[issue40874] Update to libmpdec-2.5.0

2020-07-03 Thread Łukasz Langa


Łukasz Langa  added the comment:

> And a release manager who has no libmpdec expertise or authority took the 
> side of the "bug" reporter without much thought.

What is this elusive "authority" you keep bringing up?

> Note that I do not go straight into accusing people, especially in uncertain 
> cases.

Neither did Anthony. He observed breakage in his builds and reported it. He 
noted that the change happened during the beta freeze which is documented to 
only allow bug fixes:

https://devguide.python.org/devcycle/#beta

Anthony's only fault here was depending on the system libmpdec which you claim 
is invalid use. As he explained, he did this to mirror behavior of the official 
Python packages. And it worked for the first three betas. His surprise breakage 
report wasn't unreasonable, let alone "petulant". Compare with your own 
responses which to many of us read unnecessarily defensive.

Nobody is challenging your competence. The problem is entirely with the timing 
and making non-bugfix changes during the beta phase. Bringing up credentials, 
track records, or listing professional networks doesn't change that.

Finally, while Raymond and Antoine are welcome to voice their opinions on the 
matter, your change is landing in 3.9.0b4 which I'm about to announce. So we 
won't be reverting it. In the future let's make sure we stick to the release 
calendar to avoid similar heat. If we need to bend a rule or two, that's okay, 
it happens. Making a fellow core developer stamp your change in such case will 
increase visibility, and is a good practice regardless, required for example in 
avionics software.

--

___
Python tracker 

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

Re: New to python - Just a question

2020-07-03 Thread David Lowry-Duda

Hello!

> Please can someone help
> 
> Write an algorithm (choose the language you prefer) that given a 
> character string, for instance {‘c’,’a’,’i’,’o’,’p’,’a’}, will print 
> out the list of characters appearing at least 2 times. In this 
> specific example, it would return {‘a’}. Afterwards, comment out the 
> cost in terms of space and time.
> 
> Write a bash/python script that takes a directory as an argument and 
> output the total lines of code in *.cpp files recursively.

These are both pretty classical problems. But the way you've presented 
them sounds a bit like a "do my homework for me" style question.

Do you know any python? I recommend that you consider following a book 
or tutorial to get through some of the basics. I like to recommend Think 
Python (available for free from the author).

If you have particular questions that come up while you're trying to 
write a solution, I think more people would be more inclined to help.

Good luck! - DLD

-- 
David Lowry-Duda  
-- 
https://mail.python.org/mailman/listinfo/python-list

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

2020-07-03 Thread Dong-hee Na



Dong-hee Na  added the comment:


New changeset c0b214bc08f0da89e5b2e4b8cc9f07783833d6b8 by Dong-hee Na in branch 
'master':
bpo-1635741: Port faulthandler module to multiphase initialization (GH-21294)
https://github.com/python/cpython/commit/c0b214bc08f0da89e5b2e4b8cc9f07783833d6b8


--

___
Python tracker 

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

Re: Formal Question to Steering Council (re recent PEP8 changes)

2020-07-03 Thread Rhodri James


On 03/07/2020 15:28, Jon Ribbens via Python-list wrote:

On 2020-07-03, Rhodri James  wrote:

On 02/07/2020 23:46, Random832 wrote:

On Thu, Jul 2, 2020, at 18:29, Michael Torrie wrote:

Come again?  I can see no other link in the verbage with the
"relics of white supremacy" that she referred to.  If there are
other links, they should be included in the commit message.  I
agree with Rhodri that an explanation would be interesting.  Far be
it from me to demand one.  So whatever.


It's possible that this wasn't explained clearly enough in the commit
message itself (though I would argue it was definitely adequately
explained in the ensuing on-list discussion, and wonder how much of
that discussion you've actually read), but the point is that the
*whole idea* of "standard English" is tied to white supremacy, not
any particular standard whether via its authors or otherwise.


As I said in my preamble, it doesn't matter whether you believe that is
true or think it's utter bollocks.  I asked the question to get the
Steering Council's opinion, not anyone else's.


You don't get to decide whose opinions are offered.


But I do get to decide whose opinions are solicited.

--
Rhodri James *-* Kynesim Ltd
--
https://mail.python.org/mailman/listinfo/python-list

Re: Formal Question to Steering Council (re recent PEP8 changes)

2020-07-03 Thread Bev In TX

> On Jul 3, 2020, at 10:23 AM, o1bigtenor  wrote:
> 
> I decry the present hypersensitivity to any hint of culture that was
> present some 200 years ago especially when such sensitivity is used
> to block a wider group from participating. IMO such hypersensitive
> individuals might be better served by finding some other soap box
> to scream from if that is to be their primary input into a particular
> conversation.

I have worked In harmony with multinational teams from all over the world.  We 
never needed a writing standard for code changes.  Are current Python code 
changes documented in such a poor way that they are not understandable?  That 
would be the only reason to promote a standard, which would not have to be as 
stringent as Strunk and White.

I don’t like the use of the word “racism” in connection with writing standards, 
which is blatantly not true.  Do the current leaders of Python promote 
political agendas?  That’s what this sounds like.
-- 
https://mail.python.org/mailman/listinfo/python-list

[issue41198] Round built-in function not shows zeros acording significant figures and calculates different numbers of odd and even

2020-07-03 Thread Mark Dickinson



Mark Dickinson  added the comment:

One note: in the original post, not only are the values being tested coming 
from NumPy's arange, but round(x[i],1) is testing *NumPy's* rounding 
functionality, not Python's. x[i] has type np.float64, and while np.float64 
does inherit from Python's float, it also overrides float.__round__ with its 
own implementation (that essentially amounts to scale-by-power-of-ten, 
round-to-nearest-int, unscale, just like Python used to do in the bad old 
days). So errors from arange plus NumPy's non-correctly-rounded round means 
that all bets are off on what happens for values that _look_ as though they're 
ties when shown in decimal, but aren't actually ties thanks to the 
what-you-see-is-not-what-you-get nature of binary floating-point.

On arange in particular, I've never looked closely into the implementation; 
it's never noticeably not been "close enough" (i.e., accurate to within a few 
ulps either way), and I've never needed it or expected it to be perfectly 
correctly rounded. Now that it's been brought up, I'll take a look. (But that 
shouldn't keep this issue open, since that's a pure NumPy issue.)

Honestly, given the usual floating-point imprecision issues, I'm surprised that 
the balance is coming out as evenly as it is in Tim's and Steven's experiments. 
I can see why it might work for a single binade, but I'm at a loss to explain 
why you'd expect a perfect balance across several binades. 

For example: if you're looking at values of the form 0.xx5 in the binade [0.5, 
1.0], and rounding those to two decimal places, you'd expect perfect parity, 
because if you pair the values from [0.5, 0.75] with the reverse of the values 
from [0.75, 1.0], in each pair exactly one of the two values will round up, and 
one down (the paired values always add up to *exactly* 1.5, with no rounding, 
so the errors from the decimal-to-binary rounding will always go in opposite 
directions). For example 0.505 rounds up, and dually 0.995 rounds down. (But 
whether the pair gives (up, down) or (down, up) will depend on exactly which 
way the rounding went when determining the nearest binary64 float, so will be 
essentially unpredictable.)

>>> test_values = [x/1000 for x in range(505, 1000, 10)]
>>> len(test_values)  # total count of values
50
>>> sum(round(val, 2) > val for val in test_values)  # number rounding up
25

But then you need to make a similar argument for the next binade down: [0.25, 
0.5] (which doesn't work at all in this case, because that binade contains an 
odd number of values).

Nevertheless, this *does* seem to work, and I haven't yet found a good 
explanation why. Any offers?

>>> k = 8
>>> test_values = [x/10**(k+1) for x in range(5, 10**(k+1), 10)]
>>> sum(round(val, k) > val for val in test_values)
5000

BTW, yes, I think this issue can be closed.

--

___
Python tracker 

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

Re: Formal Question to Steering Council (re recent PEP8 changes)

On 2020-07-02, Michael Torrie  wrote:
> On 7/2/20 1:26 PM, Jon Ribbens via Python-list wrote:
>> On 2020-07-02, Michael Torrie  wrote:
>>> Agreed. She just needs to fix her commit message to remove the sentence
>>> about the relics of white supremacy.  The fact she would conflate an
>>> author's name with some kind of race-related thing is a bit
>>> embarrassing, frankly.
>> 
>> She didn't - you did.
>
> Come again?

She didn't - you did.
-- 
https://mail.python.org/mailman/listinfo/python-list

New to python - Just a question

2020-07-03 Thread Daley Okuwa via Python-list


Please can someone help

Write an algorithm (choose the language you prefer) that given a character 
string, for instance {‘c’,’a’,’i’,’o’,’p’,’a’}, will print out the list of 
characters appearing at least 2 times. In this specific example, it would 
return {‘a’}. Afterwards, comment out the cost in terms of space and time.


Write a bash/python script that takes a directory as an argument and output the 
total lines of code in *.cpp files recursively.


Thanks Daley
-- 
https://mail.python.org/mailman/listinfo/python-list

[issue37322] test_ssl: test_pha_required_nocert() emits a ResourceWarning

2020-07-03 Thread Matthew Hughes



Matthew Hughes  added the comment:

Whoops, I realise the patch I shared contained a combination of two 
(independent) approaches I tried:

1. Add sleep and perform cleanup
2. Naively patch catch_threading_exception to accept a cleanup routine to be 
run upon exiting but before removing the thread.

--

___
Python tracker 

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

[issue37322] test_ssl: test_pha_required_nocert() emits a ResourceWarning

2020-07-03 Thread Matthew Hughes



Matthew Hughes  added the comment:

I noticed this test was still emitting a "ResourceWarning":
--
$ ./python -m test test_ssl -m TestPostHandshakeAuth 
0:00:00 load avg: 0.74 Run tests sequentially
0:00:00 load avg: 0.74 [1/1] test_ssl
/home/mjh/src/cpython/Lib/test/support/threading_helper.py:209: 
ResourceWarning: unclosed 
  del self.thread
ResourceWarning: Enable tracemalloc to get the object allocation traceback

== Tests result: SUCCESS ==

1 test OK.

Total duration: 1.1 sec
Tests result: SUCCESS
--
and thought I would try silencing it by ensuring the SSL connection handled by 
the separate thread was closed before exiting. My attempt involved checking the 
thread's exception and acting accordingly, but I ran into a race condition 
which (solely as a proof of concept) I resolved by adding a sleep() call (see 
patch).

While I continue to search for a proper resolution I was wondering what 
approach someone with more insight might suggest.

--
nosy: +mhughes
Added file: https://bugs.python.org/file49294/naive_proof_of_concept.patch

___
Python tracker 

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

[issue29778] _Py_CheckPython3 uses uninitialized dllpath when embedder sets module path with Py_SetPath



Change by Steve Dower :


--
assignee:  -> steve.dower

___
Python tracker 

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

Re: Formal Question to Steering Council (re recent PEP8 changes)

2020-07-03 Thread o1bigtenor

On Thu, Jul 2, 2020 at 7:05 PM Michael Torrie  wrote:
>
> On 7/2/20 4:46 PM, Random832 wrote:
> > It's possible that this wasn't explained clearly enough in the commit
> > message itself (though I would argue it was definitely adequately
> > explained in the ensuing on-list discussion, and wonder how much of
> > that discussion you've actually read), but the point is that the
> > *whole idea* of "standard English" is tied to white supremacy, not
> > any particular standard whether via its authors or otherwise.
>
> Good to know.  Nothing at all was explained in the commit message
> justifying that particular sentence, leaving one unfamiliar with the
> background to wonder what she was referring to.
>
> I definitely agree the words "standard English" are pretty meaningless
> to would-be python developers anyway and the new phrase in the PEP 8 is
> much better.
> --

Given that I have had plenteen (sic) years of education all in the English
language including some instructors trained in the UK and also some
periods of technical education in at least one language other than English
and am quite familiar with the said "Stunk and White - -  *The Elements*
* of Style*" perhaps I could offer some background.

Especially in an upper class year academic education Strunk and White is
quite usually inflicted upon at least all Arts and Humanities kind of
students. They advocate for short pithy sentences, including IIRC a
statement something to the effect of a sentence with more than 5 words
is too long. There are many other amorphisms most of which point out
that such a writing style is perhaps the easiest to understand. As far as
that goes their position is somewhat correct but I have come to very much
differ with their quite heavy handed technique. When one is writing about
very complex topics it is useful to be able to craft complex sentences but
then said authors seemed to think that everything was reducible to a
quite elementary level - - - I have not found that to be true.

A little closer to the intent of the question.
In good documentation reasonable sentences make it much easier to
understand a previously unknown topic or idea. So in that way asking
for writers to at least be aware of if not slavishly follow some so called
'standard of style'. Strunk and White and Kate Turabian have both
published works that are quite accepted in the Arts and the Humanities
as I did not do any graduate training in the Sciences I do not know
what the recommended manuals are in such but in reading plenty
of papers most of the authors would be quite assisted in writing to be
understood rather than to impress.

So I can understand a desire to suggest the usage of a 'Manual of
Style' but I would not be comfortable if it were a requirement.
Languages other than English have different strengths and their
users, when faced with writing documentation in a language that,
even though they are quite comfortable with English, they are not
used to producing what may be possible by a writer who is fully
cognisant with the most rigorous aspects of style, may enhance
said documentation even if said documentation is not 'perfectly
correct in style'. (The previous sentence is an example of what is
possible using complex sentence structure - - - grin!)

I decry the present hypersensitivity to any hint of culture that was
present some 200 years ago especially when such sensitivity is used
to block a wider group from participating. IMO such hypersensitive
individuals might be better served by finding some other soap box
to scream from if that is to be their primary input into a particular
conversation.

HTH

Regards
-- 
https://mail.python.org/mailman/listinfo/python-list

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

2020-07-03 Thread tomaszdrozdz



Change by tomaszdrozdz :


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

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

2020-07-03 Thread tomaszdrozdz



Change by tomaszdrozdz :


--
title: Allo to provide custom exception handler to asyncio.run() -> Allow to 
provide custom exception handler to asyncio.run()

___
Python tracker 

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

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



STINNER Victor  added the comment:


New changeset 3549ca313a6103a3adb281ef3a849298b7d7f72c by Victor Stinner in 
branch 'master':
bpo-1635741: Fix unicode_dealloc() for mortal interned string (GH-21270)
https://github.com/python/cpython/commit/3549ca313a6103a3adb281ef3a849298b7d7f72c


--

___
Python tracker 

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

[issue41194] Python 3.9.0b3 crash on compile() in PyAST_Check() when the _ast module is loaded more than once



STINNER Victor  added the comment:


New changeset f8599279b6ac8c44538b608fd08c13ccf674f497 by Victor Stinner in 
branch '3.9':
[3.9] bpo-41194: The _ast module cannot be loaded more than once (GH-21290) 
(GH-21292)
https://github.com/python/cpython/commit/f8599279b6ac8c44538b608fd08c13ccf674f497


--

___
Python tracker 

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

[issue41196] APPDATA directory is different in store installed python



Steve Dower  added the comment:

> A crude workaround is to script PowerShell or CMD in a child process.

I mean, that's not a *terrible* workaround:

>>> import os
>>> p1 = os.path.expandvars("%APPDATA%\\test.txt")
>>> p1
'C:\\Users\\steve\\AppData\\Roaming\\test.txt'
>>> open(p1, "w").close()
>>> os.system(f'copy "{os.path.realpath(p1)}" "{p1}"')
1 file(s) copied.
0
>>>

But yeah, definitely crude :)

--

___
Python tracker 

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

[issue40874] Update to libmpdec-2.5.0



Stefan Krah  added the comment:

> both 3.8 and 3.9 have to be available on the systems for the transition 
> period.

If sonames can be incremented for libraries even if they are ABI compatible, 
how about using up as many as you need for the Debian
package?  Next time when I release mpdecimal, I'll ask you about
the highest version that's in use at Debian and increment it by
one.

--

___
Python tracker 

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

Re: Formal Question to Steering Council (re recent PEP8 changes)