[issue36985] typing.ForwardRef is undocumented

[Anthony Sottile]

New submission from Anthony Sottile :

- New since 3.7.0
- is exposed by some public apis:
- the `__doc__` attribute of `typing` mentions `ForwardRef`
- `get_type_hints` can expose an instance of it: 
https://bugs.python.org/issue35834

Should this be documented? including in __all__?

--
assignee: docs@python
components: Documentation
messages: 342979
nosy: Anthony Sottile, docs@python
priority: normal
severity: normal
status: open
title: typing.ForwardRef is undocumented
versions: Python 3.7, Python 3.8

___
Python tracker 

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

[issue36984] typing docs "versionadded" is inaccurate for many attributes

[Anthony Sottile]

Change by Anthony Sottile :


--
keywords: +patch
pull_requests: +13366
stage:  -> patch review

___
Python tracker 

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

[issue36984] typing docs "versionadded" is inaccurate for many attributes

[Anthony Sottile]

New submission from Anthony Sottile :

expanding on https://bugs.python.org/issue36983

the docs are also a bit out of date in places

I'm not sure how to document something that appeared in two versions, but I'll 
leave that part to review.

Using data generated / collected in 
https://github.com/asottile/flake8-typing-imports via this script: 
https://github.com/asottile/flake8-typing-imports/blob/master/bin/build-generated

and then analyzed with this script:

from flake8_typing_imports import SYMBOLS

ALL = set().union(*(v for _, v in SYMBOLS))

for k in sorted(ALL):
state = False
for i, (v, ks) in enumerate(SYMBOLS):
if state is False and k in ks:
print(f'{k}: new in {v}')
state = True
elif state is True and k not in ks:
print(f'=> {k}: removed in {v}')
state = False


I've found the following:

$ python3 t.py | grep -v 'new in 3\.5\.0'
AsyncContextManager: new in 3.5.4
=> AsyncContextManager: removed in 3.6.0
AsyncContextManager: new in 3.6.2
AsyncGenerator: new in 3.6.1
AsyncIterable: new in 3.5.2
AsyncIterator: new in 3.5.2
Awaitable: new in 3.5.2
ChainMap: new in 3.5.4
=> ChainMap: removed in 3.6.0
ChainMap: new in 3.6.1
ClassVar: new in 3.5.3
Collection: new in 3.6.0
ContextManager: new in 3.5.4
Coroutine: new in 3.5.3
Counter: new in 3.5.4
=> Counter: removed in 3.6.0
Counter: new in 3.6.1
DefaultDict: new in 3.5.2
Deque: new in 3.5.4
=> Deque: removed in 3.6.0
Deque: new in 3.6.1
ForwardRef: new in 3.7.0
GenericMeta: new in 3.5.4
=> GenericMeta: removed in 3.6.0
GenericMeta: new in 3.6.1
=> GenericMeta: removed in 3.7.0
NewType: new in 3.5.2
NoReturn: new in 3.5.4
=> NoReturn: removed in 3.6.0
NoReturn: new in 3.6.2
OrderedDict: new in 3.7.2
TYPE_CHECKING: new in 3.5.2
Text: new in 3.5.2
Type: new in 3.5.2

--
assignee: docs@python
components: Documentation
messages: 342978
nosy: Anthony Sottile, docs@python
priority: normal
severity: normal
status: open
title: typing docs "versionadded" is inaccurate for many attributes
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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[Eryk Sun]

Eryk Sun  added the comment:

"crtdbg.h" doesn't provide STATUS_CONTROL_C_EXIT, but it should be fine to 
remove it anyway. I think it was left behind by accident in 2007. It was added 
to support a PYTHONNOERRORWINDOW environment variable, but then this idea was 
dropped in favor of extending the msvcrt module:

* https://grokbase.com/t/python/python-3000/078wkax0sd/buildbots
* 
https://github.com/python/cpython/commit/945362cf971fb2e10f8f2a8e71e8ff10516ebe4c#diff-75445bdc3b6b3dd20b005698fa165444
* 
https://github.com/python/cpython/commit/3dc33d18452de871cff98914dda81ff00b4d00f6#diff-75445bdc3b6b3dd20b005698fa165444

I presume STATUS_CONTROL_C_EXIT gets included from "winnt.h" -> "Windows.h" -> 
"Include/internal/pycore_condvar.h" -> "Include/internal/pycore_gil.h" -> 
"Include/internal/pycore_pystate.h".

If [STATUS_]CONTROL_C_EXIT isn't defined, I suggest defining 
WIN32_LEAN_AND_MEAN before including "Windows.h". This reduces the number of 
included headers from about 350 down to about 200. Also, to stay strictly 
within the Windows API, we might want to use CONTROL_C_EXIT (from 
[min]winbase.h) instead of STATUS_CONTROL_C_EXIT (from "winnt.h").

--
nosy: +eryksun

___
Python tracker 

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

[issue36983] typing.__all__ has drifted from actual contents

[Anthony Sottile]

Anthony Sottile  added the comment:

using the same heuristic as the test uses, here's what's been missing from 
__all__ historically

(note: I _manually_ skipped `Final` for 3.5.0-3)

===(3, 5, 0)===
+FrozenSet
+SupportsBytes
+SupportsComplex
===(3, 5, 1)===
+FrozenSet
+SupportsBytes
+SupportsComplex
===(3, 5, 2)===
+FrozenSet
+SupportsBytes
+SupportsComplex
===(3, 5, 3)===
+AsyncIterable
+AsyncIterator
+Awaitable
+Coroutine
+SupportsBytes
+SupportsComplex
===(3, 5, 4)===
+AsyncContextManager
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Coroutine
+NoReturn
===(3, 5, 5)===
+AsyncContextManager
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Coroutine
+NoReturn
===(3, 5, 6)===
+AsyncContextManager
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Coroutine
+NoReturn
===(3, 5, 7)===
+AsyncContextManager
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Coroutine
+NoReturn
===(3, 6, 0)===
+AsyncIterable
+AsyncIterator
+Awaitable
+Collection
+ContextManager
+Coroutine
+SupportsBytes
+SupportsComplex
===(3, 6, 1)===
+AsyncGenerator
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Collection
+ContextManager
+Coroutine
+SupportsBytes
+SupportsComplex
===(3, 6, 2)===
+AsyncContextManager
+AsyncGenerator
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Collection
+Coroutine
+NoReturn
===(3, 6, 3)===
+AsyncContextManager
+AsyncGenerator
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Collection
+Coroutine
+NoReturn
===(3, 6, 4)===
+AsyncContextManager
+AsyncGenerator
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Collection
+Coroutine
+NoReturn
===(3, 6, 5)===
+AsyncContextManager
+AsyncGenerator
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Collection
+Coroutine
+NoReturn
===(3, 6, 6)===
+AsyncContextManager
+AsyncGenerator
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Collection
+Coroutine
+NoReturn
===(3, 6, 7)===
+AsyncContextManager
+AsyncGenerator
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Collection
+Coroutine
+NoReturn
===(3, 6, 8)===
+AsyncContextManager
+AsyncGenerator
+AsyncIterable
+AsyncIterator
+Awaitable
+ChainMap
+Collection
+Coroutine
+NoReturn
===(3, 7, 0)===
+ChainMap
+ForwardRef
===(3, 7, 1)===
+ChainMap
+ForwardRef
===(3, 7, 2)===
+ChainMap
+ForwardRef
+OrderedDict
===(3, 7, 3)===
+ChainMap
+ForwardRef
+OrderedDict

--

___
Python tracker 

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

[issue36983] typing.__all__ has drifted from actual contents

[Anthony Sottile]

Change by Anthony Sottile :


--
keywords: +patch
pull_requests: +13365
stage:  -> patch review

___
Python tracker 

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

[issue36983] typing.__all__ has drifted from actual contents

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
nosy: +gvanrossum, levkivskyi

___
Python tracker 

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

[issue36983] typing.__all__ has drifted from actual contents

[Anthony Sottile]

New submission from Anthony Sottile :

notably it is missing ForwardRef, OrderedDict, ChainMap in python3.8

it is missing others in other versions

I'm going to attempt to write a test which should classify things that should 
belong there

--
components: Library (Lib)
messages: 342975
nosy: Anthony Sottile
priority: normal
severity: normal
status: open
title: typing.__all__ has drifted from actual contents
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

[issue36982] Add support for extended color functions in ncurses 6.1

[Jeffrey Kintscher]

New submission from Jeffrey Kintscher :

ncurses 6.1 adds extended color functions to support terminals with 256 colors 
(e.g. xterm-256color). The extended functions take color pair values that are 
signed integers because the existing functions only take signed 16-bit values.

My goal with this issue is to transparently use the ncurses extended color 
functions when compiling with ncurses 6.1 or newer. This should be 
straightforward and transparent to curses module users because the short int 
restrictions are in the ncurses library and not in the curses module API.

This will fix the problems observed in issue #36630 but is broader, which is 
why I created a separete issue. I will work on this and post a PR whit it is 
ready.

--
components: Library (Lib)
messages: 342974
nosy: websurfer5
priority: normal
severity: normal
status: open
title: Add support for extended color functions in ncurses 6.1
versions: 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

[issue36981] asyncio transport.write() memory out

[viocal]

New submission from viocal :

in asyncio
when  filedata than free memory(hardware) 
will be memory out Or killed by OS

for buf in filedata:
   transport.write(buf)
#to client


I  try it todo:
abort  transporting to protect application be killed by OS
modified selector_events.py

def _write_ready(self):
assert self._buffer, 'Data should not be empty'

if self._conn_lost:
return
try:
n = self._sock.send(self._buffer)
except (BlockingIOError, InterruptedError):
pass
except Exception as exc:
self._loop._remove_writer(self._sock_fd)
self._buffer.clear()
self._fatal_error(exc, 'Fatal write error on socket transport')
if self._empty_waiter is not None:
self._empty_waiter.set_exception(exc)
return
else:
try:
   if n:
   del self._buffer[:n]
   self._maybe_resume_protocol()  # May append to buffer.
   if not self._buffer:
   self._loop._remove_writer(self._sock_fd)
   if self._empty_waiter is not None:
   self._empty_waiter.set_result(None)
   if self._closing:
   self._call_connection_lost(None)
   elif self._eof:
   self._sock.shutdown(socket.SHUT_WR)
except Exception as exc: #(MemoryError)
 self._buffer.clear()
 self._loop._remove_writer(self._sock_fd)
 self._fatal_error(exc, 'Fatal write error on Selector 
SocketTransport write ready')
 if self._empty_waiter is not None:
 self._empty_waiter.set_exception(exc)
 return

--
components: asyncio
messages: 342973
nosy: asvetlov, viocal, yselivanov
priority: normal
severity: normal
status: open
title: asyncio transport.write() memory out
type: resource usage
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

[issue36952] fileinput input's and Fileinput's bufsize=0 marked for removal in 3.8

[Inada Naoki]

Change by Inada Naoki :


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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Matthias Bussonnier]

Matthias Bussonnier  added the comment:

> Oh, please, please, please PLEASE let's not over-sell this! 

Sorry didn't wanted to give you a heart attack. The optimisation has been 
mentioned, and you never know what people get excited on.

> Such constant-folding ...

Well, in here we might get that, but I kind of want to see how this is taught 
or explain, what I want to avoid is tutorial or examples saying that 
`.dedent()` is "as if you hadn't put spaces in front".

> I don't think so, but eventually it might.

Ok, thanks.

Again just being cautious, and I see this is targeted 3.9 so plenty of time.
I believe this will be a net improvement on many codebases.

--

___
Python tracker 

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

[issue31163] Return destination path in Path.rename and Path.replace

[Cheryl Sabella]

Cheryl Sabella  added the comment:

I've closed the original pull request as the Github user account that created 
it no longer exists.

--
keywords: +easy -patch
nosy: +berker.peksag, cheryl.sabella
stage: patch review -> needs patch
versions: +Python 3.8 -Python 3.6

___
Python tracker 

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

[issue36980] pass-by-reference clues

[Josh Rosenberg]

Josh Rosenberg  added the comment:

1. This is a bug tracker for bugs in the Python language spec and the CPython 
interpreter, not a general problem solving site.

2. The ids will differ for changeValue2 if you actually call it (kernel = 
kernel + 2 requires the the old id of kernel differ from the new id, because 
they both exist simultaneously, and are different objects); I'm guessing you're 
calling the wrong function or printing the ids of the wrong variables.

3. "Would it possible for the python interpreter/compiler to let me know when a 
function is going to clobber a variable that is not used in the function or 
passed to the function or returned by the function" Every bit of clobbering 
you're seeing involves a variable passed to the function (and sometimes 
returned by it). CVkernel=myKernel just made two names that bind to the same 
underlying object, so passing either name as an argument to a function that 
modifies its arguments will modify what is seen from both names. That's how 
mutable objects work. This is briefly addressed in the tutorial here: 
https://docs.python.org/3/tutorial/classes.html#a-word-about-names-and-objects 
. As a general rule, Python built-ins *either* modify their arguments in place 
and return nothing (None) *or* return new values leaving the arguments 
unmodified. It's a matter of programmer discipline to adhere to this practice 
in your own code (numpy does make it harder, since it uses views extensively, 
making sli
 cing not an effective way to copy inputs).

All that said, this isn't a bug. It's a longstanding feature of Python alias 
arguments to avoid expensive deep copies by default; the onus is on the 
function writer to copy if needed, or to document the behavior if mutation of 
the arguments is to occur.

--
nosy: +josh.r

___
Python tracker 

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

[issue36980] pass-by-reference clues

[Steven D'Aprano]

Steven D'Aprano  added the comment:

Hi Stefan, and welcome. 

This is not a help desk, you really should ask elsewhere for explanations of 
how Python works. There are no bugs here: what you are seeing is standard 
pass-by-object behaviour.

You are misinterpreting what you are seeing. Python is never pass by reference 
or pass by value.

https://en.wikipedia.org/wiki/Evaluation_strategy

https://www.effbot.org/zone/call-by-object.htm

*All* function objects, whether strings, ints, lists or numpy arrays, are 
passed as objects. If you want to make a copy, you have to explicitly make a 
copy. If you don't, and you mutate the object in place, you will see the 
mutation in both places.


> Shouldn't the id of each variable be different if they are different 
> instances?

Not necessarily: IDs can be reused. Without seeing the actual running code, I 
can't tell if the IDs have been used or if they are the same ID because they 
are the same object.

> Would it possible for the python interpreter/compiler to let me know when a 
> function is going to clobber a variable that is not used in the function or 
> passed to the function or returned by the function

Python never clobbers a variable not used in the function. It may however 
mutate an object which is accessible from both inside and outside a function.

--
nosy: +steven.daprano
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Steven D'Aprano]

Steven D'Aprano  added the comment:

> It might be unclear for the following especially if `.dedent()` get 
> sold as zero-overhead at compile time.

Oh, please, please, please PLEASE let's not over-sell this! There is no 
promise that dedent will be zero-overhead: it is a method, like any 
other method, which is called at runtime. Some implementations *might* 
*sometimes* be able to optimize that at compile-time, just as some 
implementations *might* *sometimes* be able to optimize away long 
complex arithmetic expressions and do them at compile time.

Such constant-folding optimizations can only occur with literals, since 
arbitrary expressions aren't known at compile-time. F-strings aren't 
string literals, they are executable code and can run thngs like this:

f"{'abc' if random.random() > 0.5 else 'xyz'}"

So we don't know how many spaces each line begins with until after the 
f-string is evaluated:

f"""{m:5d}
{n:5d}"""

Unless we over-sell the keyhole optimization part, there shouldn't be 
anything more confusing about dedent than this:

x, X = 'spam', 'eggs'
f"{x}".upper()
# returns 'SPAM' not 'eggs'

> Could it be made clearer with the peephole optimiser (and tested, I 
> don't believe it is now), that dedent applies after-formatting ?

We should certainly make that clear that 

Personally, I think we should soft-sell on the compile-time optimization 
until such time that the Steering Council decides it should be a 
mandatory language feature.

> Alternative modifications/suggestions/notes: 
> 
>- I can also see how having dedent applied **before** formatting 
>with f-string could be useful or less surprising ( a d"" prefix 
>could do that... just wondering what your actual goal is).

I don't see how it will make any difference in the common case. And the 
idea here is to avoid yet another string prefix.

>- Is this a supposed to deprecating textwrap.dedent ? 

I don't think so, but eventually it might.

--

___
Python tracker 

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

[issue36980] pass-by-reference clues

[stefan]

New submission from stefan :

I often get unexpected results when a called function results in  a change in a 
variable because the function gets a pass by reference. For example, consider 
this snippet of code that manipulates the first column of a 3x3 matrix that it 
gets.
~~~
import numpy as np

def changeValue(kernel):
kernel[0,0]=kernel[0,0]+ 2 
kernel[1,0]=kernel[1,0]+ 2 
kernel[2,0]=kernel[2,0]+ 2 
return kernel

myKernel = np.array((
 [0, -1, 0],
 [-1, 5, -1],
 [0, -1, 0]), dtype="int")
CVkernel=myKernel

print(CVkernel)
a=changeValue(myKernel)
print(a)
print(CVkernel)
~~~
I get the following output

[[ 0 -1  0]
 [-1  5 -1]
 [ 0 -1  0]]

[[ 2 -1  0]
 [ 1  5 -1]
 [ 2 -1  0]]

[[ 2 -1  0]
 [ 1  5 -1]
 [ 2 -1  0]]

The value of myKernel clobbers CVkernel. I think there is an unintentional 
call-by-reference (pass-by-reference?) going on but I am not sure why.

If I define the function slightly differently

def changeValue2(kernel):
kernel=kernel + 2 
return kernel

Then CVkernel is left untouched

[[ 0 -1  0]
 [-1  5 -1]
 [ 0 -1  0]]

[[2 1 2]
 [1 7 1]
 [2 1 2]]

[[ 0 -1  0]
 [-1  5 -1]
 [ 0 -1  0]]

What is going on here? 

EDIT Even when I use a 'safe' function call that does not clobber CVkernel, 
like kernel=kernel + 2 , the id of myKernel and CVkernel are the same.

id of myKernel  139994865303344
myKernel 
[[ 0 -1  0]
 [-1  5 -1]
 [ 0 -1  0]]
id of CVKernel  139994865303344
CVKernel 
[[ 0 -1  0]
 [-1  5 -1]
 [ 0 -1  0]]

**call made to changeValue2**

id of myKernel  139994865303344
myKernel 
[[ 0 -1  0]
 [-1  5 -1]
 [ 0 -1  0]]
id of CVKernel  139994865303344
CVKernel 
[[ 0 -1  0]
 [-1  5 -1]
 [ 0 -1  0]]
output a 
[[2 1 2]
 [1 7 1]
 [2 1 2]]

Shouldn't the id of each variable be different if they are different instances?

Would it possible for the python interpreter/compiler to let me know when a 
function is going to clobber a variable that is not used in the function or 
passed to the function or returned by the function

--
messages: 342967
nosy: skypickle
priority: normal
severity: normal
status: open
title: pass-by-reference clues
type: behavior

___
Python tracker 

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

[issue36792] [Windows] time: crash on formatting time with de_DE locale

[Jeremy Kloth]

Jeremy Kloth  added the comment:

> * the experimental UTF-8 support was enabled because "de_DE" is not a
> known Windows locale name - try with "de-DE"
>
> Perhaps it would be easy to do the replacement of underscores with hyphens
> on Windows in this function? I think that's safe enough, yes?
>

Even some well known locale names still use the utf-8 code page.  Most seem
to uncommon, but at least es-BR (Brazil) does and would still fall victim
to these UCRT bugs.

>

--
nosy: +jeremy.kloth

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Matthias Bussonnier]

Matthias Bussonnier  added the comment:

I've tried a bit PR 13455, I find this way nicer than textwrap.dedent(...), 
though I wonder if f-string readability (and expected behavior?) might suffer a 
tiny bit with the order of formatting the f-string vs dedenting. 

In the following it is clear that dedent is after formatting: 

>>> dedent(f"   {stuff}")

It might be unclear for the following especially if `.dedent()` get sold as 
zero-overhead at compile time.

>>> f"   {stuff}".dedent()

Could it be made clearer with the peephole optimiser (and tested, I don't 
believe it is now), that dedent applies after-formatting ?

Alternative modifications/suggestions/notes: 

   - I can also see how having dedent applied  **before** formatting with 
f-string could be useful or less surprising ( a d"" prefix could do that... 
just wondering what your actual goal is). 
   - Is this a supposed to deprecating textwrap.dedent ? Duck-typing and stuff, 
could textwrap.dedent work on non-str things and the current implementation not 
( it assumes the `.dedent()` method exists) and thus be backward-incompatible ?

--

___
Python tracker 

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

[issue22865] Document how to make pty.spawn not copy data

[Geoff Shannon]

Change by Geoff Shannon :


--
pull_requests: +13364

___
Python tracker 

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

[issue36511] Add Windows ARM32 buildbot

[Paul Monson]

Change by Paul Monson :


--
pull_requests: +13363

___
Python tracker 

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

[issue35563] Doc: warnings.rst - add links to references

[Cheryl Sabella]

Cheryl Sabella  added the comment:


New changeset 6220c02e09e9f3a7458d32ad774ada0ba1571cb8 by Cheryl Sabella in 
branch 'master':
bpo-35563: Add reference links to warnings.rst (GH-11289)
https://github.com/python/cpython/commit/6220c02e09e9f3a7458d32ad774ada0ba1571cb8


--

___
Python tracker 

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

[issue35563] Doc: warnings.rst - add links to references

[Cheryl Sabella]

Change by Cheryl Sabella :


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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Gregory P. Smith]

Gregory P. Smith  added the comment:

Agreed, I'm in favor of going forward with this .dedent() optimization approach 
today.

If we were to attempt a default indented multi-line str and bytes literal 
behavior change in the future (a much harder decision to make as it is a 
breaking change), that is its own issue and probably PEP worthy.

--

___
Python tracker 

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

[issue36969] pdb: do_args: display/handle keyword-only arguments

[miss-islington]

miss-islington  added the comment:


New changeset 50b3f205d82d88eec69f18a0ad4bb2440ba73501 by Miss Islington (bot) 
in branch '3.7':
bpo-36969: Make PDB args command display keyword only arguments (GH-13452)
https://github.com/python/cpython/commit/50b3f205d82d88eec69f18a0ad4bb2440ba73501


--
nosy: +miss-islington

___
Python tracker 

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

[issue31779] assertion failures and a crash when using an uninitialized struct.Struct object

[Cheryl Sabella]

Change by Cheryl Sabella :


--
versions:  -Python 3.6

___
Python tracker 

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

[issue36969] pdb: do_args: display/handle keyword-only arguments

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

> Rémi, could you do a PR addressing co_posonlyargcount?
Of course, should I open a new PR or post a patch to be added to a current PR?

--
nosy: +remi.lapeyre

___
Python tracker 

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

[issue36969] pdb: do_args: display/handle keyword-only arguments

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

Rémi, could you do a PR addressing co_posonlyargcount?

--

___
Python tracker 

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

[issue36969] pdb: do_args: display/handle keyword-only arguments

[miss-islington]

Change by miss-islington :


--
pull_requests: +13362

___
Python tracker 

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

[issue36969] pdb: do_args: display/handle keyword-only arguments

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:


New changeset bf457c7d8224179a023957876e757f2a7ffc3d9d by Pablo Galindo (Rémi 
Lapeyre) in branch 'master':
bpo-36969: Make PDB args command display keyword only arguments (GH-13452)
https://github.com/python/cpython/commit/bf457c7d8224179a023957876e757f2a7ffc3d9d


--

___
Python tracker 

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

[issue36969] pdb: do_args: display/handle keyword-only arguments

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

Notice that pdb also does not handle correctly PEP570:

def f1(x,/,arg=None, *, kwonly=None):
breakpoint()

f1(3)
-> breakpoint()
(Pdb) args
x = 3

--
nosy: +pablogsal

___
Python tracker 

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

[issue36979] ncurses extension uses wrong include path

[Chris Hargreaves]

New submission from Chris Hargreaves :

This is similar to: https://bugs.python.org/issue28190

Not cross-compiling, but using a different ncurses version than is provided 
under /usr/include/ncursesw

Specifying CPPFLAGS to have "-I/path/to/ncurses/include" does not override the 
"/usr/include/ncursesw" in setup.py

if curses_library == 'ncursesw':
curses_defines.append(('HAVE_NCURSESW', '1'))
if not cross_compiling:
curses_includes.append('/usr/include/ncursesw')

Python 2.7.x does not have this issue, but 3.6.x and 3.7.x do.  2 and 3 have 
different ways of setting up the include path for curses when building the 
extension.

In my case, removing the curses_include.append from setup.py results in a 
working extension.

It probably makes sense that Extension(include_dirs=) take priority over Python 
build CPPFLAGS, setup.py may need to be more cautious about adding the ncurses 
include path.

Only tested in 2.7, 3.6, 3.7.

--
components: Build, Library (Lib)
messages: 342957
nosy: chargr
priority: normal
severity: normal
status: open
title: ncurses extension uses wrong include path
type: compile error
versions: Python 3.6, Python 3.7

___
Python tracker 

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

[issue36630] failure of test_colors_funcs in test_curses with ncurses 6.1

[Jeffrey Kintscher]

Jeffrey Kintscher  added the comment:

I posted a bug report to the bug-ncurses mailing list:

https://lists.gnu.org/archive/html/bug-ncurses/2019-05/msg00022.html

--

___
Python tracker 

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

[issue36969] pdb: do_args: display/handle keyword-only arguments

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
keywords: +patch
pull_requests: +13361
stage:  -> patch review

___
Python tracker 

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

[issue36978] `python3 -m pip install` has no `--requirement` option on Windows

[Marco Sulla]

New submission from Marco Sulla :

It's really useful and easy to have a requirements.txt. It integrates also with 
Github, that tells you if you're specifying a version of the library with 
security issues.

I don't understand why this flag is missing in Windows builds. It seems to me 
not too much difficult to implement. Please? ^^

--
components: Library (Lib)
messages: 342955
nosy: Marco Sulla
priority: normal
severity: normal
status: open
title: `python3 -m pip install` has no `--requirement` option on Windows
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

[issue36964] `python3 -m venv NAME`: virtualenv is not portable

[Marco Sulla]

Marco Sulla  added the comment:

Well, I didn't know `--copy`. I think I'll use it. :)

What about VIRTUAL_ENV="$(dirname "$(dirname "$(readlink -nf "$0")")")"? In 
`bash` and in `sh` it works.

--

___
Python tracker 

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

[issue36952] fileinput input's and Fileinput's bufsize=0 marked for removal in 3.8

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:


New changeset 1a3faf9d9740a8c7505c61839ef09929a7ff9e35 by Serhiy Storchaka 
(Matthias Bussonnier) in branch 'master':
bpo-36952: Remove the bufsize parameter in fileinput.input(). (GH-13400)
https://github.com/python/cpython/commit/1a3faf9d9740a8c7505c61839ef09929a7ff9e35


--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue23378] argparse.add_argument action parameter should allow value extend

[Guido van Rossum]

Guido van Rossum  added the comment:

I've felt the need for this myself.

--
nosy: +gvanrossum

___
Python tracker 

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

[issue36919] Exception from 'compile' reports a newline char not present in input

[Pavel Koneski]

Pavel Koneski  added the comment:

> I'm assuming the real issue is wanting to make IronPython pass as much of the 
> CPython test suite as possible.

This is indeed the case. The CPython test suite is invaluable in guiding 
IronPython development. Most of the time, the tests are pretty good to gloss 
over implementation artifacts (usually error messages), so that they work for 
IronPython as well, despite some differences between CPython and IronPython.

There are a few cases, however, when the tests expect behavior that is 
implementation-specific and difficult to match in IronPython, or is proper 
Python but impossible to match for IronPython. For all such cases I would like 
to submit patches to the CPython repo, but I am new to this process. Should 
such case first be reported on bpo, python-dev, or just straight a github PR?

Sometimes, by writing additional tests for IronPython we discover what seems as 
possible bugs in CPython. I was planning to submit reports for them on bpo, 
assuming this is the proper place to discuss them, but perhaps python-dev is a 
better place.

> So fixing the tests to allow it either way sounds good.

A github PR is on its way.

--

___
Python tracker 

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

[issue23896] lib2to3 doesn't provide a grammar where exec is a function

[Guido van Rossum]

Guido van Rossum  added the comment:

Thanks Batuhan Taşkaya!

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

[issue23896] lib2to3 doesn't provide a grammar where exec is a function

[Guido van Rossum]

Guido van Rossum  added the comment:


New changeset 4011d865d0572a3dd9988f2935cd835cc8fb792a by Guido van Rossum 
(Batuhan Taşkaya) in branch 'master':
bpo-23896: Add a grammar where exec isn't a stmt (#13272)
https://github.com/python/cpython/commit/4011d865d0572a3dd9988f2935cd835cc8fb792a


--
nosy: +gvanrossum

___
Python tracker 

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

[issue36977] SharedMemoryManager should relase its resources when its parent process dies

[Pierre Glaser]

Change by Pierre Glaser :


--
keywords: +patch
pull_requests: +13360
stage:  -> patch review

___
Python tracker 

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

[issue36977] SharedMemoryManager should relase its resources when its parent process dies

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
nosy: +davin

___
Python tracker 

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

[issue36977] SharedMemoryManager should relase its resources when its parent process dies

[Pierre Glaser]

New submission from Pierre Glaser :

The new multiprocessing.managers.SharedMemoryManager spawns a server that 
delivers memory segments to a parent Python process. If the parent process 
terminates unexpectedly, we should now make the manager process notice this 
termination it using the recent multiprocessing.parent_process object (that 
comes with a sentinel), and shut it down.

--
components: Library (Lib)
messages: 342948
nosy: pierreglaser, pitrou
priority: normal
severity: normal
status: open
title: SharedMemoryManager should relase its resources when its parent process 
dies

___
Python tracker 

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

[issue36919] Exception from 'compile' reports a newline char not present in input

[Guido van Rossum]

Guido van Rossum  added the comment:

I'm assuming the real issue is wanting to make IronPython pass as much of the 
CPython test suite as possible. I am okay with interpretation (B) in this case 
-- I can totally see that other parsing strategies have no use for adding the 
'\n' character to the end of the string. But I don't want to declare that 
CPython is wrong to show the '\n' -- it seems a pretty harmless artifact. So 
fixing the tests to allow it either way sounds good.

--
nosy: +gvanrossum

___
Python tracker 

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

[issue36888] Create a way to check that the parent process is alive for deamonized processes

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Waiting for the next PR now :-)

--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
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

[issue36888] Create a way to check that the parent process is alive for deamonized processes

[Antoine Pitrou]

Antoine Pitrou  added the comment:


New changeset c09a9f56c08d80567454cae6f78f738a89e1ae94 by Antoine Pitrou 
(Thomas Moreau) in branch 'master':
bpo-36888: Add multiprocessing.parent_process() (GH-13247)
https://github.com/python/cpython/commit/c09a9f56c08d80567454cae6f78f738a89e1ae94


--

___
Python tracker 

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

[issue36919] Exception from 'compile' reports a newline char not present in input

[Pavel Koneski]

Change by Pavel Koneski :


--
versions:  -Python 3.5, Python 3.6

___
Python tracker 

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

[issue36919] Exception from 'compile' reports a newline char not present in input

[Pavel Koneski]

Pavel Koneski  added the comment:

If "equivalent input" is acceptable, then it looks like case B: other 
implementations possibly having different forms of equivalent input.

I am going to post this question on python-dev.

--
versions: +Python 3.5, Python 3.6

___
Python tracker 

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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[Erik Janssens]

Erik Janssens  added the comment:

PR has been changed to include "windows.h" ...

--

___
Python tracker 

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

[issue36976] email: AttributeError

[alter-bug-tracer]

alter-bug-tracer  added the comment:

It is actually the exact same bug. At that time we were not sure if it security 
related or not, so we disclosed it privately and discussed it with Mark. We 
were not aware that he has submitted it for us.

--

___
Python tracker 

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

[issue36976] email: AttributeError

[Karthikeyan Singaravelan]

Karthikeyan Singaravelan  added the comment:

See also issue36910 which seems to be similar report on non-ascii 
Content-Transfer-Encoding which is present in the reported file0 file too.

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

___
Python tracker 

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

[issue36976] email: AttributeError

[alter-bug-tracer]

New submission from alter-bug-tracer :

The 'lower' method is called on a Header object when trying to parse the 
attached file.

Code:
import email
import sys
with open(sys.argv[1], "rb") as f:
  msg = email.message_from_binary_file(f)
  print (len(msg))


Traceback:
msg = email.message_from_binary_file(f)
  File "/usr/lib/python3.5/email/__init__.py", line 62, in 
message_from_binary_file
return BytesParser(*args, **kws).parse(fp)
  File "/usr/lib/python3.5/email/parser.py", line 110, in parse
return self.parser.parse(fp, headersonly)
  File "/usr/lib/python3.5/email/parser.py", line 57, in parse
feedparser.feed(data)
  File "/usr/lib/python3.5/email/feedparser.py", line 178, in feed
self._call_parse()
  File "/usr/lib/python3.5/email/feedparser.py", line 182, in _call_parse
self._parse()
  File "/usr/lib/python3.5/email/feedparser.py", line 322, in _parsegen
if (self._cur.get('content-transfer-encoding', '8bit').lower()
AttributeError: 'Header' object has no attribute 'lower'

--
files: file0.zip
messages: 342940
nosy: alter-bug-tracer
priority: normal
severity: normal
status: open
title: email: AttributeError
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file48340/file0.zip

___
Python tracker 

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

[issue36975] csv: undocumented UnicodeDecodeError on malformed file

[alter-bug-tracer]

New submission from alter-bug-tracer :

UnicodeDecodeError is thrown instead of csv.Error when parsing malformed inputs.
Examples:
1. file0
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd5 in position 0: invalid 
continuation byte
Traceback (most recent call last):
  File "csv_parser.py", line 6, in 
for row in reader:
  File "/usr/local/lib/python3.8/csv.py", line 111, in __next__
row = next(self.reader)
  File "/usr/local/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
2. file1
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 51: 
invalid start byte
Traceback (most recent call last):
  File "csv_parser.py", line 6, in 
for row in reader:
  File "/usr/local/lib/python3.8/csv.py", line 110, in __next__
self.fieldnames
  File "/usr/local/lib/python3.8/csv.py", line 97, in fieldnames
self._fieldnames = next(self.reader)
  File "/usr/local/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)

(file0, file1 and csv_parser.py attached)

--
files: csv.zip
messages: 342939
nosy: alter-bug-tracer
priority: normal
severity: normal
status: open
title: csv: undocumented UnicodeDecodeError on malformed file
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file48339/csv.zip

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Steven D'Aprano]

Steven D'Aprano  added the comment:

> While the string method works pretty well, I do not think this is the best 
> way.

Regardless of what we do for literals, a dedent() method will help for 
non-literals, so I think that this feature should go in even if we 
intend to change the default behaviour in the future:

> 3.9. Implement "from __future__ import deindent".
> 3.11. Emit a FutureWarning for multiline literals that will be changed by 
> dedending if "from __future__ import deindent" is not specified.
> 3.13. Make it the default behavior.

And that gives us plenty of time to decide whether or not making it the 
default, rather than an explicit choice, is the right thing to do.

--

___
Python tracker 

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

[issue36974] Implement PEP 590

[Jeroen Demeyer]

Change by Jeroen Demeyer :


--
keywords: +patch
pull_requests: +13359
stage:  -> patch review

___
Python tracker 

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

[issue36974] Implement PEP 590

[Jeroen Demeyer]

Change by Jeroen Demeyer :


--
components: Interpreter Core
nosy: Mark.Shannon, jdemeyer, petr.viktorin
priority: normal
severity: normal
status: open
title: Implement PEP 590
type: enhancement
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

[issue36973] test_json.test_recursion.TestPyRecursion.test_endless_recursion stack overflow in AMD64 Windows8.1 Non-Debug 3.x

[Karthikeyan Singaravelan]

New submission from Karthikeyan Singaravelan :

test_json results in stack overflow after the commit to implement __repr__ for 
weakset. This is very much similar to the one consistently occurring on my 
inspect module PR in Windows tests only for the past two weeks. My change was 
in changing inspect module and more specifically in importing ast at the top of 
inspect module. The relevant commit for buildbot failure is in implementing 
__repr__ for weakset.

Buildbot error : https://buildbot.python.org/all/#/builders/12/builds/2497

Error in my PR that is consistent and same : 
https://ci.appveyor.com/project/python/cpython/builds/24631185#L1547

--
components: Tests
messages: 342937
nosy: steve.dower, vstinner, xtreak
priority: normal
severity: normal
status: open
title: test_json.test_recursion.TestPyRecursion.test_endless_recursion stack 
overflow in AMD64 Windows8.1 Non-Debug 3.x
type: behavior
versions: Python 3.8

___
Python tracker 

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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[Erik Janssens]

Erik Janssens  added the comment:

ok, thank you for the advice, I'll keep it in mind and adapt the PR !

--

___
Python tracker 

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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[Steve Dower]

Steve Dower  added the comment:

Some people say "windows.h" is the only one you're ever supposed to include, so 
if that works best, let's go with that :)

--

___
Python tracker 

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

[issue36972] Add SupportsIndex

[Paul Dagnelie]

Change by Paul Dagnelie :


--
keywords: +patch
pull_requests: +13358
stage:  -> patch review

___
Python tracker 

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

[issue36949] WeakSet.__repr__ and __str__ do not show contents of the set

[Steve Dower]

Change by Steve Dower :


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

[issue36949] WeakSet.__repr__ and __str__ do not show contents of the set

[Steve Dower]

Steve Dower  added the comment:


New changeset 5ae1c84bcd13b766989fc3f1e1c851e7bd4c1faa by Steve Dower (Batuhan 
Taşkaya) in branch 'master':
bpo-36949: Implement __repr__ on WeakSet (GH-13415)
https://github.com/python/cpython/commit/5ae1c84bcd13b766989fc3f1e1c851e7bd4c1faa


--

___
Python tracker 

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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[Erik Janssens]

Erik Janssens  added the comment:

including "winnt.h" gives me compilation problems with other undefined types.

however, simply including "windows.h" instead of both includes compiles just 
fine.

so maybe that is sufficient ??

--

___
Python tracker 

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

[issue36965] use of STATUS_CONTROL_C_EXIT in Modules/main.c breaks compilation with non MSC compilers

[Steve Dower]

Steve Dower  added the comment:

Is including just "winnt.h" sufficient?

It's very hard to tell which Windows headers are "public" vs "internal", but 
winternl.h is certainly one of the internal ones (according to the big warning 
comment at the top of the file)

--

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

While the string method works pretty well, I do not think this is the best way. 
If 98% of multiline string will need deindenting, it is better to do it by 
default. For those 2% that do not need deintentation, it can be prohibited by 
adding the backslash followed by a newline at first position (except the start 
of the string). For example:

smile = '''\

 XX
 XX  X
  X
XXX   X
  X
 XX  X
 XX

\
'''

Yes, this is breaking change. But we have import from __future__ and 
FutureWarning. The plan may be:

3.9. Implement "from __future__ import deindent".
3.11. Emit a FutureWarning for multiline literals that will be changed by 
dedending if "from __future__ import deindent" is not specified.
3.13. Make it the default behavior.

--

___
Python tracker 

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

[issue25988] collections.abc.Indexable

[Matthias Bussonnier]

Matthias Bussonnier  added the comment:

mbussonn: Your new PR looks like it's related to #36953 ("Remove collections 
ABCs?"), not this issue specifically. Can you withdraw/reissue attached to the 
correct issue?

Apologies, I've rebased and updated the issue numbers, not sure how I got the 
wrong one. I've also unlinked from here.

--

___
Python tracker 

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

[issue25988] collections.abc.Indexable

[Matthias Bussonnier]

Change by Matthias Bussonnier :


--
pull_requests:  -13320

___
Python tracker 

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

[issue26467] Add async magic method support to unittest.mock.Mock

[Lisa Roach]

Lisa Roach  added the comment:

Added and AsyncMock class which supports mocking async magic methods.

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

The optimization that can be done in the AST is done in the AST.

--

___
Python tracker 

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

[issue36953] Remove collections ABCs?

[Matthias Bussonnier]

Change by Matthias Bussonnier :


--
keywords: +patch
pull_requests: +13356
stage:  -> patch review

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

Thanks @serhiy.storchaka, it's far easier to do here. I pushed the patch to the 
attached PR. Is there a reason the other optimisations in the Peephole 
optimizer are not done in the AST?

--

___
Python tracker 

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

[issue36770] stdlib - shutil.make_archive - add support for different ZIP compression method

[Roundup Robot]

Change by Roundup Robot :


--
pull_requests: +13355
stage:  -> patch review

___
Python tracker 

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

[issue26467] Add async magic method support to unittest.mock.Mock

[Lisa Roach]

Lisa Roach  added the comment:


New changeset 77b3b7701a34ecf6316469e05b79bb91de2addfa by Lisa Roach in branch 
'master':
bpo-26467: Adds AsyncMock for asyncio Mock library support (GH-9296)
https://github.com/python/cpython/commit/77b3b7701a34ecf6316469e05b79bb91de2addfa


--
nosy: +lisroach

___
Python tracker 

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

[issue36972] Add SupportsIndex

[Paul Dagnelie]

New submission from Paul Dagnelie :

In order to allow hex() oct() and bin() to be used on user-defined classes, and 
to check if they can be used on a class at runtime, a SupportsIndex protocol 
would be useful to integrate.  A PR already exists in the backport repo for 
this issue: https://github.com/python/typing/pull/630

--
components: Library (Lib)
messages: 342925
nosy: pcd1193182
priority: normal
severity: normal
status: open
title: Add SupportsIndex
type: enhancement
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

[issue36792] [Windows] time: crash on formatting time with de_DE locale

[Charlie Clark]

Charlie Clark  added the comment:

I can confirm that using "de-DE" does indeed avoid the crash.

--

___
Python tracker 

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

[issue36792] [Windows] time: crash on formatting time with de_DE locale

[Steve Dower]

Steve Dower  added the comment:

I've received a detailed response from the UCRT team, and there are a few 
pieces here.

* the fact that tzname is cached in ACP is known and will be fixed
* the decoding bug is real, but it's due to the experimental UTF-8 support
* the experimental UTF-8 support was enabled because "de_DE" is not a known 
Windows locale name - try with "de-DE"

Perhaps it would be easy to do the replacement of underscores with hyphens on 
Windows in this function? I think that's safe enough, yes?

--

___
Python tracker 

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

[issue34700] typing.get_type_hints doesn't know about typeshed

[Guido van Rossum]

Guido van Rossum  added the comment:

Yeah, the Sphinx use case is somewhat different from the originally envisioned 
use case for get_type_hints().  Possibly Sphinx could just directly inspect 
__annotations__ rather than calling get_type_hints()?  I'm not sure if there's 
any situation where it would need the things that get_type_hints() is supposed 
to take care of.

--

___
Python tracker 

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

[issue25988] collections.abc.Indexable

[Josh Rosenberg]

Josh Rosenberg  added the comment:

mbussonn: Your new PR looks like it's related to #36953 ("Remove collections 
ABCs?"), not this issue specifically. Can you withdraw/reissue attached to the 
correct issue?

--
nosy: +josh.r, mbussonn

___
Python tracker 

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

[issue36084] Threading: add builtin TID attribute to Thread objects

[STINNER Victor]

STINNER Victor  added the comment:

> So where do we go from here?

I propose to only add attribute if it's supported.

If nobody comes with a fix, I would prefer to remove the feature to repair the 
AIX buildbot.

--

___
Python tracker 

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

[issue26122] Isolated mode doesn't ignore PYTHONHASHSEED

[STINNER Victor]

STINNER Victor  added the comment:

> Is there a way to fix the issue in 3.7 and earlier? We might consider it a 
> security issue.

Hum, Python 3.7 is fixed as well. At least, in the 3.7 dev branch.

Fixed seed:

vstinner@apu$ PYTHONHASHSEED=42 ./python -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 ./python -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 ./python -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 ./python -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}

Random seed:

vstinner@apu$ PYTHONHASHSEED=42 ./python -I -c 'print(set("abcdefgh"))'
{'b', 'e', 'd', 'f', 'g', 'c', 'a', 'h'}
vstinner@apu$ PYTHONHASHSEED=42 ./python -I -c 'print(set("abcdefgh"))'
{'d', 'g', 'e', 'b', 'h', 'f', 'a', 'c'}
vstinner@apu$ PYTHONHASHSEED=42 ./python -I -c 'print(set("abcdefgh"))'
{'e', 'b', 'g', 'c', 'a', 'h', 'f', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 ./python -I -c 'print(set("abcdefgh"))'
{'c', 'd', 'a', 'g', 'f', 'e', 'h', 'b'}

--

Python 3.6 has the bug:

vstinner@apu$ PYTHONHASHSEED=42 python3.6 -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 python3.6 -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 python3.6 -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 python3.6 -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}

vstinner@apu$ PYTHONHASHSEED=42 python3.6 -I -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 python3.6 -I -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 python3.6 -I -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}
vstinner@apu$ PYTHONHASHSEED=42 python3.6 -I -c 'print(set("abcdefgh"))'
{'g', 'e', 'a', 'b', 'c', 'f', 'h', 'd'}

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

> Perform the optimization at the AST level, not in the peepholer.

Thanks, this makes more sense.

--

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

> Serhiy's message crossed with mine.

And mine crossed with yours, sorry. I will update my PR shortly.

--

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Steven D'Aprano]

Steven D'Aprano  added the comment:

Serhiy's message crossed with mine -- you should probably listen to
him over me :-)

--

___
Python tracker 

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

[issue36971] Add subsections in C API "Common Object Structures" page

[Jeroen Demeyer]

Change by Jeroen Demeyer :


--
keywords: +patch
pull_requests: +13354
stage:  -> patch review

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Steven D'Aprano]

Steven D'Aprano  added the comment:

> One issue with it is that in:
> def f():
> return "   foo".dedent()
> f will have both "   foo" and "foo" in its constants even if the first is not 
> used anymore.

That seems to be what happens with other folded constants:

py> def f():
... return 99.0 + 0.9
...
py> f.__code__.co_consts
(None, 99.0, 0.9, 99.9)

so I guess that this is okay for a first draft. One difference is that 
strings tend to be much larger than floats, so this will waste more 
memory. We ought to consider removing unused constants at some point.

(But not me, sorry, I don't have enough C.)

> Removing it requires looping over the code once more while marking 
> the constants seen in a set and I was not sure if this was ok.

That should probably be a new issue.

--

___
Python tracker 

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

[issue35894] Apparent regression in 3.8-dev: 'TypeError: required field "type_ignores" missing from Module'

[Guido van Rossum]

Guido van Rossum  added the comment:

> [T]here's other optional fields in the ast, type ignores don't seem essential 
> to the `Module`, could those be made optional as well?

I think you're referring to the `?` syntax in `Python.asdl`.  But the 
`type_ignores` attribute is already a list (using `*`) and AFAICT you cannot 
combine `?` and `*`.  You have to provide an empty list.

--

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Perform the optimization at the AST level, not in the peepholer.

--
nosy: +serhiy.storchaka

___
Python tracker 

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

[issue36763] Implementation of the PEP 587

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 0f72147ce2b3d65235b41eddc6a57be40237b5c7 by Victor Stinner in 
branch 'master':
bpo-36763: Fix _PyRuntime.preconfig.coerce_c_locale (GH-13444)
https://github.com/python/cpython/commit/0f72147ce2b3d65235b41eddc6a57be40237b5c7


--

___
Python tracker 

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

[issue36971] Add subsections in C API "Common Object Structures" page

[Jeroen Demeyer]

New submission from Jeroen Demeyer :

The page https://docs.python.org/3/c-api/structures.html could be better 
structured by arranging the content in sub-sections.

--
assignee: docs@python
components: Documentation
messages: 342911
nosy: docs@python, jdemeyer
priority: normal
severity: normal
status: open
title: Add subsections in C API "Common Object Structures" page
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

[issue22865] Document how to make pty.spawn not copy data

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 522ccef8690970fc4f78f51a3adb995f2547871a by Victor Stinner (Geoff 
Shannon) in branch 'master':
bpo-22865: Expand on documentation for the pty.spawn function (GH-11980)
https://github.com/python/cpython/commit/522ccef8690970fc4f78f51a3adb995f2547871a


--
nosy: +vstinner

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

Hi @steven.daprano, @gregory.p.smith. I added the first version of my PR for 
review.

One issue with it is that in:

def f():
return "   foo".dedent()

f will have both "   foo" and "foo" in its constants even if the first is not 
used anymore. Removing it requires looping over the code once more while 
marking the constants seen in a set and I was not sure if this was ok.

--

___
Python tracker 

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

[issue36906] Compile time textwrap.dedent() equivalent for str or bytes literals

[Rémi Lapeyre]

Change by Rémi Lapeyre :


--
keywords: +patch
pull_requests: +13353
stage:  -> patch review

___
Python tracker 

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

[issue35814] Syntax quirk with variable annotations

[Guido van Rossum]

Guido van Rossum  added the comment:

> Is PEP the best place for such updates? Maybe we can add a `versionchanged` 
> note in 
> https://docs.python.org/3/reference/simple_stmts.html#annotated-assignment-statements
>  instead?

We should definitely update the docs, with `versionchanged`.

But we should also update the PEP, because the reason this was changed was an 
interpretation issue in the PEP.  This is different from simply changing things 
in a later version because we've come up with a new idea or we've learned that 
something was a bad idea.

Now that the intention of the PEP has been clarified, the PEP itself ought to 
be updated with words expressing the clearer version; but because previously 
the intended syntax wasn't supported, it makes sense to also add a note there 
that this wasn't implemented correctly until 3.8.

--

___
Python tracker 

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

[issue36763] Implementation of the PEP 587

[STINNER Victor]

Change by STINNER Victor :


--
title: PEP 587: Rework initialization API to prepare second version of the PEP 
-> Implementation of the PEP 587

___
Python tracker 

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

[issue36763] PEP 587: Rework initialization API to prepare second version of the PEP

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +13352

___
Python tracker 

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

[issue36763] PEP 587: Rework initialization API to prepare second version of the PEP

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 425717fee1c72df464c9f85b9a8d32b9197d1035 by Victor Stinner in 
branch 'master':
bpo-36763: Fix encoding/locale tests in test_embed (GH-13443)
https://github.com/python/cpython/commit/425717fee1c72df464c9f85b9a8d32b9197d1035


--

___
Python tracker 

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

[issue36763] PEP 587: Rework initialization API to prepare second version of the PEP

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +13351

___
Python tracker 

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

[issue26185] zipfile.ZipInfo slots can raise unexpected AttributeError

[Mickaël Schoentgen]

Change by Mickaël Schoentgen :


--
pull_requests: +13350

___
Python tracker 

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

[issue35721] _UnixSubprocessTransport leaks socket pair if Popen fails

[Andrew Svetlov]

Change by Andrew Svetlov :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
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