[issue40620] Range tutorial shorthand could be made clearer

[Chas Belov]

New submission from Chas Belov :

I found 
https://docs.python.org/3.7/tutorial/controlflow.html#the-range-function 
section 4.3 confusing. The range() Function shows the following example:

>>> for i in range(5):
... print(i)
...
0
1
2
3
4

[some instructional text]

range(5, 10)
   5, 6, 7, 8, 9

range(0, 10, 3)
   0, 3, 6, 9

range(-10, -100, -30)
  -10, -40, -70

This appears to be an instruction to type, for example:
range(5, 10)
at the prompt, and that the response will be:
   5, 6, 7, 8, 9

leading to a perceived bug when I type at the prompt:
>>> range(5, 10)
and receive the response
range(5, 10)

I ultimately figured out that the example is a shorthand to substitute
range(5, 10)
for the original 
range(5)

>>> for i in range(5, 10):
... print(i)
...
5
6
7
8
9

It would be less confusing if the example instead read:



Substituting "range(5, 10)" for "range(5)" results in (one number per line)
5, 6, 7, 8, 9

Substituting "range(0, 10, 3)" results in
0, 3, 6, 9

and substituting "range(-10, -100, -30)" results in
-10, -40, -70

---

such that it is clear that the statements are not meant to be taken as literal 
stand-alone entries to be typed at the prompt but are instead substitutions.

--
messages: 368817
nosy: docor...@sonic.net
priority: normal
severity: normal
status: open
title: Range tutorial shorthand could be made clearer
versions: Python 3.7

___
Python tracker 

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

[issue1076955] Tutorial corrections (various issues spaced throughout the document)

[Chas Belov]

Change by Chas Belov :


--
title: Tutorial corrections -> Tutorial corrections (various issues spaced 
throughout the document)

___
Python tracker 

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

[issue11425] Cleanup sample code spacing and block arrangement in tutorial.

[Chas Belov]

Change by Chas Belov :


--
title: Cleanup sample codes in tutorial. -> Cleanup sample code spacing and 
block arrangement in tutorial.

___
Python tracker 

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

[issue3490] Example Code Error in Tutorial Documentation Section 4.4

[Chas Belov]

Change by Chas Belov :


--
title: Example Code Error in Tutorial Documentation -> Example Code Error in 
Tutorial Documentation Section 4.4

___
Python tracker 

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

[issue40275] test.support has way too many imports

[hai shi]

hai shi  added the comment:

Hi, folks.
If there have no other imports should be improved, I suggest to close this bpo 
;)

--

___
Python tracker 

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

[issue40619] compile() passes rest of file as SyntaxError().text when file unreadable

[Guido van Rossum]

New submission from Guido van Rossum :

Example:

>>> compile("pass\n(1+)\npass", "", "exec")
Traceback (most recent call last):
  File "", line 1, in 
  File "", line 2
(1+)
pass
   ^
SyntaxError: invalid syntax
>>> 

Note that the input is

pass
(1+)
pass

The second "pass" (and in fact the entire file) leaks into the SyntaxError 
object's text attribute.

This only happens when the file (here "") cannot be read.

It's not specific to compile(), it seems fundamental in the C-level pegen API.

--
keywords: 3.4regression
messages: 368815
nosy: gvanrossum
priority: normal
severity: normal
stage: needs patch
status: open
title: compile() passes rest of file as SyntaxError().text when file unreadable
type: behavior
versions: Python 3.9

___
Python tracker 

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

[issue40619] compile() passes rest of file as SyntaxError().text when file unreadable

[Guido van Rossum]

Change by Guido van Rossum :


--
nosy: +lys.nikolaou, pablogsal

___
Python tracker 

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

[issue40275] test.support has way too many imports

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 7443d42021d433da0497f8ba651daa47e7dc1991 by Hai Shi in branch 
'master':
bpo-40275: Import locale module lazily in gettext (GH-19905)
https://github.com/python/cpython/commit/7443d42021d433da0497f8ba651daa47e7dc1991


--

___
Python tracker 

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

[issue40217] The garbage collector doesn't take in account that objects of heap allocated types hold a strong reference to their type

[STINNER Victor]

STINNER Victor  added the comment:

The issue has been fixed in the master branch, thanks Pablo! I close the issue.

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

[issue40429] [C API] PyThreadState_GetFrame() and PyFrame_GetCode() should return a strong refrence

[STINNER Victor]

Change by STINNER Victor :


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

[issue40609] _tracemalloc: remove pointer_t type

[STINNER Victor]

STINNER Victor  added the comment:

I modified _Py_hashtable_t to remove key_size and data_size: keys are now 
always "void *" and values are now always "void *".

See also bpo-40602: Move Modules/hashtable.h to 
Include/internal/pycore_hashtable.h.

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

[issue40597] generated email message exceeds RFC-mandated limit of 998 characters

[R. David Murray]

R. David Murray  added the comment:

Thanks, Arkadiusz.

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

[issue40521] Make tuple, dict, frame free lists, unicode interned strings, unicode latin1 singletons per-interpreter

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19389
pull_request: https://github.com/python/cpython/pull/20085

___
Python tracker 

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

[issue40597] generated email message exceeds RFC-mandated limit of 998 characters

[R. David Murray]

R. David Murray  added the comment:


New changeset 6f2f475d5a2cd7675dce844f3af436ba919ef92b by Arkadiusz Hiler in 
branch 'master':
bpo-40597: email: Use CTE if lines are longer than max_line_length consistently 
(gh-20038)
https://github.com/python/cpython/commit/6f2f475d5a2cd7675dce844f3af436ba919ef92b


--

___
Python tracker 

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

[issue40597] generated email message exceeds RFC-mandated limit of 998 characters

[miss-islington]

Change by miss-islington :


--
nosy: +miss-islington
nosy_count: 3.0 -> 4.0
pull_requests: +19388
pull_request: https://github.com/python/cpython/pull/20084

___
Python tracker 

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

[issue40618] PEG Parser: Invalid targets for augassign and except succeed

[Lysandros Nikolaou]

Change by Lysandros Nikolaou :


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

___
Python tracker 

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

[issue40618] PEG Parser: Invalid targets for augassign and except succeed

[Lysandros Nikolaou]

New submission from Lysandros Nikolaou :

Tuples and lists, which are invalid augmented assignment targets, currently get 
successfully parsed, without failing.

➜  cpython git:(targets-fix) ✗ ./python -X oldparser  
Python 3.9.0a6+ (heads/master-dirty:75cd8e48c6, May 14 2020, 03:01:42) 
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> (a, b) += (1, 2)
  File "", line 1
SyntaxError: illegal expression for augmented assignment


➜  cpython git:(pr/20076) ./python 
Python 3.9.0a6+ (heads/pr/20076:bcf5be2772, May 14 2020, 02:15:37) 
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> (a, b) += 1
SystemError: invalid node type (26) for augmented assignment

We also accept arbitrary targets in `except` clauses, while we should only be 
accepting NAME nodes:

➜  cpython git:(master) ./python 
Python 3.9.0a6+ (heads/master:75cd8e48c6, May 14 2020, 03:14:03) 
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> try:
... pass
... except Exception as a.b:
... pass
... 
[1]135956 segmentation fault (core dumped)  ./python

--
assignee: lys.nikolaou
components: Interpreter Core
messages: 368809
nosy: gvanrossum, lys.nikolaou, pablogsal
priority: normal
severity: normal
status: open
title: PEG Parser: Invalid targets for augassign and except succeed
type: behavior
versions: Python 3.9

___
Python tracker 

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

[issue40521] Make tuple, dict, frame free lists, unicode interned strings, unicode latin1 singletons per-interpreter

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 3d17c045b4c3d09b72bbd95ed78af1ae6f0d98d2 by Victor Stinner in 
branch 'master':
bpo-40521: Add PyInterpreterState.unicode (GH-20081)
https://github.com/python/cpython/commit/3d17c045b4c3d09b72bbd95ed78af1ae6f0d98d2


--

___
Python tracker 

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

[issue40521] Make tuple, dict, frame free lists, unicode interned strings, unicode latin1 singletons per-interpreter

[STINNER Victor]

STINNER Victor  added the comment:

I wrote a draft PR to make interned strings per-interpreter. It does crash 
because it requires to make method cache and _PyUnicode_FromId() (bpo-39465) 
compatible with subinterpreters.

--

___
Python tracker 

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

[issue29587] Generator/coroutine 'throw' discards exc_info state, which is bad

[Chris Jerdonek]

Chris Jerdonek  added the comment:


New changeset 75cd8e48c62c97fdb9d9a94fd2335be06084471d by Chris Jerdonek in 
branch 'master':
bpo-29587: Make gen.throw() chain exceptions with yield from (GH-19858)
https://github.com/python/cpython/commit/75cd8e48c62c97fdb9d9a94fd2335be06084471d


--

___
Python tracker 

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

[issue40521] Make tuple, dict, frame free lists, unicode interned strings, unicode latin1 singletons per-interpreter

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19386
pull_request: https://github.com/python/cpython/pull/20082

___
Python tracker 

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

[issue39465] Design a subinterpreter friendly alternative to _Py_IDENTIFIER

[STINNER Victor]

STINNER Victor  added the comment:


New changeset d6fb53fe42d83a10f1372dd92ffaa6a01d2feffb by Victor Stinner in 
branch 'master':
bpo-39465: Remove _PyUnicode_ClearStaticStrings() from C API (GH-20078)
https://github.com/python/cpython/commit/d6fb53fe42d83a10f1372dd92ffaa6a01d2feffb


--

___
Python tracker 

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

[issue40521] Make tuple, dict, frame free lists, unicode interned strings, unicode latin1 singletons per-interpreter

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19385
pull_request: https://github.com/python/cpython/pull/20081

___
Python tracker 

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

[issue39465] Design a subinterpreter friendly alternative to _Py_IDENTIFIER

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19384
pull_request: https://github.com/python/cpython/pull/20078

___
Python tracker 

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

[issue38787] PEP 573: Module State Access from C Extension Methods

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 97e1568325e4d8eff2fc80eeb174b3f3e5d1c350 by Victor Stinner in 
branch 'master':
bpo-38787: Fix Argument Clinic defining_class_converter (GH-20074)
https://github.com/python/cpython/commit/97e1568325e4d8eff2fc80eeb174b3f3e5d1c350


--

___
Python tracker 

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

[issue40602] Move Modules/hashtable.h to Include/internal/pycore_hashtable.h

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19383
pull_request: https://github.com/python/cpython/pull/20077

___
Python tracker 

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

[issue35967] Better platform.processor support

[Jason R. Coombs]

Jason R. Coombs  added the comment:

My bad. I probably could have been more proactive about providing a reproducer. 
The problem, as described above (msg335220) and in the associated cmdix ticket, 
is that invocation of `platform.(anything)` causes shelling out to execute 
"uname", so it's not possible to implement uname on Python unless one can 
guarantee that `platform.(anything)` is not invoked prior to the Python uname 
implementation executing.

Here's a Dockerfile replicating the issue:

```
FROM ubuntu:focal

# Install Python
RUN apt update
RUN apt install -y python3
RUN ln -s /usr/bin/python3 /usr/bin/python

# Simulate something on the system that invokes platform early.
RUN printf 'print(__import__("platform").system())' > sitecustomize.py
ENV PYTHONPATH=/

# Create a stubbed 'uname' command build in Python
ENV PATH=/:$PATH
RUN printf '#!/usr/bin/env python\nprint("getting ready to patch platform", 
flush=True)' > uname
RUN chmod u+x uname

CMD uname
```

As you can see, this reproducer creates a _very_ simple 'uname' implementation. 
All it does is print that it's about to patch the platform module (because 
maybe that will make things work). Unfortunately, that behavior is never 
reached because before that code has a chance to run, `sitecustomize` is 
imported and calls `platform.system()`, which invokes `platform.uname()` which 
attempts to resolve the processor, which attempts to invoke `uname -p` (even on 
Windows), which invokes the stubbed uname command, and infinite recursion 
begins.

The `sitecustomize` might seem a little contrived, except that a very similar 
behavior occurs in a very typical environment:

- pip, when installing a package for editing, invokes setuptools to `develop` 
the package.
- setuptools, when installing a package for developing, creates command-line 
entry points using a routine that imports `pkg_resources` to ensure that the 
relevant packages are present before invoking the command's functionality.
- pkg_resources imports packaging to evaluate markers.
- packaging uses `platform.system()` and other behaviors to evaluate the 
markers.

So ultimately, the same behavior is triggered before the user's code is ever 
executed.

But more importantly, why should "uname -p" be invoked in a subprocess on 
Windows to get "platform.system()"?

--

___
Python tracker 

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

[issue40334] PEP 617: new PEG-based parser

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
pull_requests: +19382
pull_request: https://github.com/python/cpython/pull/20076

___
Python tracker 

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

[issue40549] Convert posixmodule.c to multiphase initialization (PEP 489)

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19381
pull_request: https://github.com/python/cpython/pull/20075

___
Python tracker 

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

[issue38787] PEP 573: Module State Access from C Extension Methods

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +19380
pull_request: https://github.com/python/cpython/pull/20074

___
Python tracker 

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

[issue40474] Code coverage report not entirely accurate

[Lewis Ball]

Lewis Ball  added the comment:

I don't have triage permissions so I don't think I can request a review. 
Although @aeros has requested one.

--

___
Python tracker 

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

[issue40257] Improve the use of __doc__ in pydoc

[Serhiy Storchaka]

Change by Serhiy Storchaka :


--
pull_requests: +19379
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/20073

___
Python tracker 

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

[issue26175] Fully implement IOBase abstract on SpooledTemporaryFile

[Daniel Jewell]

Daniel Jewell  added the comment:

To add something additional here:

The current documentation for tempfile.SpooledTemporaryFile indicates "This 
function operates exactly as TemporaryFile() does, except that data is spooled 
in memory until the file size exceeds max_size[...]" (see 
https://docs.python.org/3/library/tempfile.html)

Except that SpooledTemporaryFile *doesn't* act _exactly_ like TemporaryFile() - 
as documented here. TemporaryFile() returns an "_io.BufferedRandom" which 
implements all of the expected "file-like" goodies - like [.readable, 
.seekable, ...etc]. SpooledTemporaryFile does not.

In comparing to the 2.x docs, the text for SpooledTemporaryFile() appears to be 
identical or nearly identical to the 3.8.x current docs. This goes in line with 
what has already been discussed here.

At a _very minimum_ the documentation should be updated to reflect the current 
differences between TemporaryFile() and SpooledTemporaryFile(). 

Perhaps an easier change would be to extend TemporaryFile() to have a parameter 
that enables functionality similar to SpooledTemporaryFile? Namely, 
*memory-only* storage up to a max_size? Or perhaps there is an alternate 
solution that already exists? 

Ultimately, the functionality that appears to be missing is to be able to 
easily create a file-like object backed primarily by memory for reading/writing 
data ... (i.e. one 100% compatible with 'the usual' file objects returned by 
open()...)

--
nosy: +danieljewell

___
Python tracker 

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

[issue40503] PEP 615: Add zoneinfo module

[Paul Ganssle]

Paul Ganssle  added the comment:

Talked to Steve Dower in a sidebar about the issue with compile-time 
configuration, he is convinced that compile-time configuration is not something 
that would be useful or worth doing on Windows. I am indifferent on the matter, 
so I am fine with calling the compile-time configuration part of this done at 
this point. If anyone building Python for Windows shows up needing support for 
this, we can re-visit the issue — I don't believe it's technically infeasible, 
just that the usage patterns of Python on Windows mean that it's not worth 
doing.

So, once we've got a critical mass of reviews done for zoneinfo, I think this 
feature is done. 🎉

--

___
Python tracker 

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

[issue40536] Addition of a "list of available time zones" function to zoneinfo

[Paul Ganssle]

Paul Ganssle  added the comment:

>From some discussion on the reference implementation PR, it seems that this 
>may be a more complicated feature than I had bargained for: 
>https://github.com/pganssle/zoneinfo/pull/60

The issue is that the current implementation picks up the posix/ and right/ 
directories as well as the posixrules file, none of which is *wrong* — they are 
available time zones, after all — but they're not really canonical zones. In 
`tzdata` we have a list of zones sourced from tzdata's `make zonenames`, which 
does not include the posix/ and right/ directories.

There is `zone1970.tab` and `zone.tab`, but that has *too* strict of a subset — 
it only includes canonical zones associated with a specific country, as far as 
I can tell, and not things like UTC. It also includes, for example, 
America/Nuuk but not America/Godthab (which was the canonical name up until 
2020a).

I'm considering postponing this feature to Python 3.10 so that we can have more 
time to figure out a decent API for this.

Łukasz: Question for you as release manager — would you prefer that we put this 
in for 3.9 with the understanding that before the final release we may end up 
needing to remove it as a nuisance or change what it returns (and possibly 
flags that would be passed to it), or would that be too disruptive in the beta 
period? I'm confident that we can make a final decision before October, just 
not confident that we can make a final decision before Monday.

--
assignee:  -> p-ganssle
nosy: +lukasz.langa

___
Python tracker 

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

[issue40257] Improve the use of __doc__ in pydoc

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

I can just copy the implementation of inspect.getdoc() and related functions in 
pydoc for use in help(), and restore the old code in the  inspect module. Of 
course it will mean that third-party tools will continue to show incorrect 
docstrings in some cases.

--

___
Python tracker 

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

[issue40257] Improve the use of __doc__ in pydoc

[Łukasz Langa]

Łukasz Langa  added the comment:

OK, that was my intuition, too. I will block beta on it then.

--

___
Python tracker 

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

[issue40334] PEP 617: new PEG-based parser

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:


New changeset a15c9b3a0524e5ca0434d2ad11076677824af941 by Lysandros Nikolaou in 
branch 'master':
bpo-40334: Always show the caret on SyntaxErrors (GH-20050)
https://github.com/python/cpython/commit/a15c9b3a0524e5ca0434d2ad11076677824af941


--

___
Python tracker 

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

[issue34790] Deprecate passing coroutine objects to asyncio.wait()

[Yury Selivanov]

Yury Selivanov  added the comment:


New changeset de92769d473d1c0955d36da2fc71462621326f00 by jack1142 in branch 
'master':
bpo-34790: add version of removal of explicit passing of coros to 
`asyncio.wait`'s documentation (#20008)
https://github.com/python/cpython/commit/de92769d473d1c0955d36da2fc71462621326f00


--

___
Python tracker 

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

[issue40617] sqlite3: expose sqlite3_create_window_function

[Ilja Umov]

New submission from Ilja Umov :

Expose sqlite3_create_window_function as sqlite3.create_window_function.

There already exists sqlite3.create_aggregate, which uses 
sqlite3_create_function_v2 and is conceptually similar.

Window functions are available in sqlite starting from 2018-09-15 (3.25.0) 
release.

References:
https://www.sqlite.org/c3ref/create_function.html
https://www.sqlite.org/changes.html

--
components: Library (Lib)
messages: 368794
nosy: Ilja Umov
priority: normal
severity: normal
status: open
title: sqlite3: expose sqlite3_create_window_function
type: enhancement
versions: Python 3.9

___
Python tracker 

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

[issue40607] asyncio.wait_for should reraise future exception even if timeout expires

[Yury Selivanov]

Yury Selivanov  added the comment:

> I think that in case inner task cancelation fails with some error, 
> asyncio.wait_for should reraise it instead of silently losing it.

+1.

--

___
Python tracker 

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

[issue40257] Improve the use of __doc__ in pydoc

[Yury Selivanov]

Change by Yury Selivanov :


--
nosy:  -yselivanov

___
Python tracker 

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

[issue40257] Improve the use of __doc__ in pydoc

[Guido van Rossum]

Guido van Rossum  added the comment:

I feel it should. At the very least, a decision should be made on how to move 
forward.

--

___
Python tracker 

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

[issue39651] Exceptions raised by EventLoop.call_soon_threadsafe

[Łukasz Langa]

Łukasz Langa  added the comment:

This sadly missed 3.8.3 but I want this addressed for 3.8.4.

--

___
Python tracker 

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

[issue40257] Improve the use of __doc__ in pydoc

[Łukasz Langa]

Łukasz Langa  added the comment:

Should this block 3.9.0b1, planned for Monday May 18th?

--
nosy: +lukasz.langa

___
Python tracker 

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

[issue38787] PEP 573: Module State Access from C Extension Methods

[hai shi]

hai shi  added the comment:

> I guess I'll need to clarify the documentation here.
> Call `PyType_GetModule` on the *defining class*, not on type(self).

+1, I didn't notice this detail until I got the error.

> The associated module is not inherited; each class in the MRO can be > 
> defined in a different module.

Thanks, pep have enough info, I need spend sometime to make sure I understand 
it clearly, Lol~.

--

___
Python tracker 

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

[issue40612] Make traceback module's formatting of SyntaxError more similar to system formatting

[Guido van Rossum]

Change by Guido van Rossum :


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

___
Python tracker 

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

[issue40616] Add `asyncio.BufferQueue`

[Serge Matveenko]

New submission from Serge Matveenko :

It looks handy to be able to leverage `collections.deque` ability to be sized 
it `asyncio.Queue`.

This could provide the ability to implement backpressure in the queue or just 
use it as a buffer in messaging systems.

The implementation provided in the linked PR.

--
components: asyncio
messages: 368788
nosy: asvetlov, lig, yselivanov
priority: normal
pull_requests: 19377
severity: normal
status: open
title: Add `asyncio.BufferQueue`

___
Python tracker 

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

[issue32545] Unable to install Python 3.7.0a4 on Windows 10 - Error 0x80070643: Failed to install MSI package.

[Ebraheem Akhter]

Ebraheem Akhter  added the comment:

try this: https://www.zmdrivers.com/

--
nosy: +jugnugee2

___
Python tracker 

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

[issue40551] PRs should be rebased on top of master before running the build/tests

[Filipe Laíns]

Filipe Laíns  added the comment:

> Just like Travis, Github actions also automatically rebases pull requests 
> onto the latest master. As you can see from a recent workflow run, it uses 
> the special ref: "refs/remote/pull/20047/merge" 
> https://github.com/python/cpython/pull/20047/checks?check_run_id=665377507#step:2:898

Thanks for letting me know. I did search through the documentation but I hadn't 
found anything regarding this. Well, I guess [1] hinted it but I did not pay 
enough attention :D

> Unless there's real world examples of ongoing problems with PRs being merged 
> with outdated test runs, I don't think this is worth complicating our CIs for.

Although I understand your point, I think this is one of those cases where 
things can easily get out of hand. And when that happens, it could be very 
difficult to revert unless you catch it right away. There's too much noise for 
me to find examples, sorry.

> As Inada-san mentioned, the occasional slip through will eventually be caught 
> by the buildbots and promptly reverted. Re-triggering the CI for very stale 
> pull requests might be worth doing. I'm kinda opposed to an automated system 
> because this creates an undue burden on our CI providers, Travis graciously 
> provides us with extra time for our coverage builds to finish already. 
> Re-running pull requests that might never be merged is a lot of added work 
> for them.

Well, I was not really proposing that. I suggested to retrigger on approvals 
(and by this I mean approvals from core devs) or have a bot retriggering and 
merging automatically.

> Maybe we can get one of the bots to tag old pull requests and then have some 
> guidance in the core-dev guide to re-run the CIs manually when merging those 
> PRs.

Yes, this seems reasonable, and could be expanded in the future. I think we 
should document this and maybe add a bot command to allow devs to retrigger 
more easily (I was thinking they could just comment with /test).

[1] 
https://github.com/actions/checkout#Checkout-pull-request-HEAD-commit-instead-of-merge-commit

--

___
Python tracker 

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

[issue22598] Add mUTF-7 codec (UTF-7 modified for IMAP)

[Christian KNITTL-FRANK]

Christian KNITTL-FRANK  added the comment:

I just stumbled over this too. Very eager to know if there are any news on the 
state of out-of-box support for the "mUTF-7" codec.

--
nosy: +Christian KNITTL-FRANK

___
Python tracker 

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

[issue40613] gcc 10 emits warning for unused function: _xxsubinterpretersmodule

[Dong-hee Na]

Dong-hee Na  added the comment:

The issue is now fixed.
The PR was tested by me and Victor.

Thanks for the suggestion and review Victor!

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

[issue40613] gcc 10 emits warning for unused function: _xxsubinterpretersmodule

[Dong-hee Na]

Dong-hee Na  added the comment:


New changeset fa0a66e62d087765dbc5c1b89d6149a23ecfb0a6 by Dong-hee Na in branch 
'master':
bpo-40613: Remove compiler warning from _xxsubinterpretersmodule (GH-20069)
https://github.com/python/cpython/commit/fa0a66e62d087765dbc5c1b89d6149a23ecfb0a6


--

___
Python tracker 

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

[issue40331] Increase test coverage for the statistics module

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

>> Perhaps you missed it because you're not in the CODEOWNERS so don't 
>> automatically get notified by GitHub?

> That's quite possible. I can't fix that as Github considers everything 
to do with my computer and browser too old.

I don't think you need to use the Github interface to change this, you can 
update the .github/CODEOWNERS file and push the change in a new commit.

--
nosy: +remi.lapeyre

___
Python tracker 

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

[issue40615] unstable behaviour for options in argparse

[Eric V. Smith]

Eric V. Smith  added the comment:

I wish the abbreviation behavior was opt-in instead of opt-out, but such is 
life.

Closing as not a bug.

--
nosy: +eric.smith
resolution:  -> not a bug
stage:  -> 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

[issue40613] gcc 10 emits warning for unused function: _xxsubinterpretersmodule

[Dong-hee Na]

Change by Dong-hee Na :


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

___
Python tracker 

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

[issue40615] unstable behaviour for options in argparse

[Chris Jerdonek]

Chris Jerdonek  added the comment:

One thing that's interesting is that you don't get the "ambiguous option" error 
if what's provided is an exact match (even if a prefix of both).

For example, if you instead parsed "--clea", it would give the error:

> error: ambiguous option: --clea could match --clear-magic, --clear

--

___
Python tracker 

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

[issue40615] unstable behaviour for options in argparse

[gaborbernat]

gaborbernat  added the comment:

I did not, nm then. Thanks for the link.

--

___
Python tracker 

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

[issue40615] unstable behaviour for options in argparse

[Chris Jerdonek]

Chris Jerdonek  added the comment:

Do you know about this section of the docs?
https://docs.python.org/3/library/argparse.html#argument-abbreviations-prefix-matching

--
nosy: +chris.jerdonek

___
Python tracker 

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

[issue40613] gcc 10 emits warning for unused function: _xxsubinterpretersmodule

[STINNER Victor]

STINNER Victor  added the comment:

The two functions are only used in assertions. They should be surrounded by 
"#ifndef NDEBUG (...) #endif".

--

___
Python tracker 

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

[issue40615] unstable behaviour for options in argparse

[gaborbernat]

Change by gaborbernat :


--
title: argparse -> unstable behaviour for options in argparse

___
Python tracker 

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

[issue40615] argparse

[gaborbernat]

New submission from gaborbernat :

Consider the following code:

from argparse import ArgumentParser

parser = ArgumentParser()
parser.add_argument("--clear-magic", action="store_true")
print(parser.parse_args(["--clear"]))

parser.add_argument("--clear", action="store_true")
print(parser.parse_args(["--clear"]))

This has the following output:

Namespace(clear_magic=True)
Namespace(clear=True, clear_magic=False)

I find it surprising and confusing why the clear magic option is accepted when 
clear is not defined. I'm tempted to say it's a bug. This unstable behaviour is 
very surprising when iteratively building up the parser.  

Discovered with 
https://github.com/pypa/virtualenv/issues/1824#issuecomment-627919033

--
messages: 368776
nosy: gaborbernat
priority: normal
severity: normal
status: open
title: argparse

___
Python tracker 

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

[issue40331] Increase test coverage for the statistics module

[Steven D'Aprano]

Steven D'Aprano  added the comment:

> Perhaps you missed it because you're not in the CODEOWNERS so don't 
> automatically get notified by GitHub?

That's quite possible. I can't fix that as Github considers everything 
to do with my computer and browser too old. Until I can get a new 
computer, I'm effectively unable to use Github, so even if I was 
notified, I probably couldn't have done much.

This wasn't a complaint, I'm grateful for everyone involved. Thanks 
again!

--

___
Python tracker 

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

[issue40331] Increase test coverage for the statistics module

[Tal Einat]

Tal Einat  added the comment:

Steven, the conversation happened in the GitHub PR comments. The PR went 
through multiple iterations of code review, by both Kyle Stanley and myself, 
and I even waited an extra couple of weeks to see if anyone had any more 
comments before merging it...

Perhaps you missed it because you're not in the CODEOWNERS so don't 
automatically get notified by GitHub?

--

___
Python tracker 

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

[issue40331] Increase test coverage for the statistics module

[Steven D'Aprano]

Steven D'Aprano  added the comment:

*blink*

How did I miss this entire thing? Where was the code review?

Thanks Tal for shepherding this through, and thanks Tzanetos for caring 
about the unit tests.

--

___
Python tracker 

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

[issue40331] Increase test coverage for the statistics module

[Tal Einat]

Tal Einat  added the comment:

Tzanetos, thanks for the report, PR, patience iterating through several rounds 
of code review comments, and overall great work!

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

[issue40331] Increase test coverage for the statistics module

[Tal Einat]

Tal Einat  added the comment:


New changeset b809717c1ead26b4e3693b8a5505dd8f8f666f08 by Tzanetos Balitsaris 
in branch 'master':
bpo-40331: Increase test coverage for the statistics module (GH-19608)
https://github.com/python/cpython/commit/b809717c1ead26b4e3693b8a5505dd8f8f666f08


--
nosy: +taleinat

___
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

[Floris]

Floris  added the comment:

I confirm the same issue as Diogo. The provided workaround of unregistering the 
sharedmemory segment in the 'consuming' process, as suggested by Jeff, solves 
the issue where exiting the consuming process causes the tracker to incorrectly 
free the shared memory. Diogo's fix to shared_memory.py#L116 does just that 
(actually it avoids registering it in the first place) and therefor seems ok to 
me.

--
nosy: +fvdnabee

___
Python tracker 

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

[issue40551] PRs should be rebased on top of master before running the build/tests

[Ammar Askar]

Ammar Askar  added the comment:

Just like Travis, Github actions also automatically rebases pull requests onto 
the latest master. As you can see from a recent workflow run, it uses the 
special ref: "refs/remote/pull/20047/merge" 
https://github.com/python/cpython/pull/20047/checks?check_run_id=665377507#step:2:898

What is this ref that Github provides?

https://git-scm.com/book/en/v2/GitHub-Maintaining-a-Project
> There’s also a refs/pull/#/merge ref on the GitHub side,
> which represents the commit that would result if you push
> the “merge” button on the site. This can allow you to test
> the merge before even hitting the button


Unless there's real world examples of ongoing problems with PRs being merged 
with outdated test runs, I don't think this is worth complicating our CIs for.

As Inada-san mentioned, the occasional slip through will eventually be caught 
by the buildbots and promptly reverted. Re-triggering the CI for very stale 
pull requests might be worth doing. I'm kinda opposed to an automated system 
because this creates an undue burden on our CI providers, Travis graciously 
provides us with extra time for our coverage builds to finish already. 
Re-running pull requests that might never be merged is a lot of added work for 
them. Maybe we can get one of the bots to tag old pull requests and then have 
some guidance in the core-dev guide to re-run the CIs manually when merging 
those PRs.

--
nosy: +ammar2

___
Python tracker 

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

[issue38787] PEP 573: Module State Access from C Extension Methods

[Petr Viktorin]

Petr Viktorin  added the comment:

I guess I'll need to clarify the documentation here.
Call `PyType_GetModule` on the *defining class*, not on type(self). See the PEP 
for details.
The associated module is not inherited; each class in the MRO can be defined in 
a different module.

--

___
Python tracker 

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

[issue40543] Tamil locale is using outdated encoding

[Ammar Askar]

Ammar Askar  added the comment:

Hi Muthu, thanks for reporting this! Looks like this is related to issue20087 
whereby the X11 locale data for TA_IN is using TSCII but the glibc supported 
file has the UTF-8 alias.

Pending a resolution to that bug, I think your best course of action would be 
to try to get this corrected upstream in x11, the code is here:

https://gitlab.freedesktop.org/xorg/lib/libx11/-/blob/master/nls/locale.alias.pre#L1078

and their issue tracker is here:

https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues


Assuming that it gets accepted upstream, it should be simple enough to 
regenerate the locale module to use it.

--
nosy: +ammar2

___
Python tracker 

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

[issue40578] Deprecate numeric item access for platform.uname()

[Marc-Andre Lemburg]

Marc-Andre Lemburg  added the comment:

I am closing this issue, since deprecations should really only be used when no 
other means are possible.

The namedtuples returned by platform.uname() do support index access and so any 
implementation change altering this is surprising and backwards incompatible, 
potentially breaking existing code which makes reasonable use of the index 
interface (the namedtuple and processor attribute was introduced in Python 3.3, 
so code written for prior versions may well still use the perfectly reasonable 
index approach).

You are essentially suggesting to change the return type, since you want to 
remove a standard tuple interface.

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

___
Python tracker 

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

[issue35967] Better platform.processor support

[Marc-Andre Lemburg]

Marc-Andre Lemburg  added the comment:

Reopening the ticket, since the implementation makes backwards incompatible 
changes to platform.uname(): see https://bugs.python.org/issue40570 for a 
discussion on a better approach to lazy evaluation of getting the processor 
information.

Before we head on into implementation details, could you please point me to the 
motivation why only the processor detail of uname() needs lazy evaluation ?

Thanks.

--
resolution: fixed -> 
status: closed -> open

___
Python tracker 

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

[issue40570] len(platform.uname()) has changed in Python 3.9

[Marc-Andre Lemburg]

Marc-Andre Lemburg  added the comment:

Hi Jason,

I think I have to review the whole set of changes again to understand what your 
motivation is/was. 

For https://bugs.python.org/issue35967 I had already stated that your use case 
is not special enough to make the platform.py logic more complex.

BTW: Please don't open several different tickets for the same problem. It 
doesn't really help to see what is going on. I'll reopen the issue35967 to 
continue the discussion there.

Thanks.

--

___
Python tracker 

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

[issue40614] ast.parse doesn't respect feature_version for debug f-strings

[Shantanu]

New submission from Shantanu :

```
~master λ python3.8 
Python 3.8.2 (default, Apr 21 2020, 00:39:48) 
[Clang 11.0.0 (clang-1100.0.33.17)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import ast
>>> ast.parse('''f"{x=}"''')  # should work
<_ast.Module object at 0x10f81af40>
>>> ast.parse('''f"{x=}"''', feature_version=(3, 6))  # should fail, but doesn't
<_ast.Module object at 0x10f857d00>
```

--
messages: 368763
nosy: hauntsaninja
priority: normal
severity: normal
status: open
title: ast.parse doesn't respect feature_version for debug f-strings
type: behavior

___
Python tracker 

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