[issue17576] PyNumber_Index() is not int-subclass friendly (or operator.index() docos lie)

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

> Can we at least switch to PyLong_CheckExact?

This is a behavior change and as such should be preceded by a period of warning.

If we go this way I propose to add a FutureWarning for int subclasses with 
overridden __index__.

As for turning the deprecated behaviour into TypeErrors, we added yet few 
deprecation warnings in 3.8. Would not be better to turn all of them into 
TypeErrors at the same time?

--

___
Python tracker 

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

[issue37132] Add a module for integer related math functions

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Well, then closing this.

--
resolution:  -> rejected
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

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

[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

[issue35814] Syntax quirk with variable annotations

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:


New changeset 8565f6b6db0fa9f65449b532a5056a98bad3dc37 by Pablo Galindo in 
branch 'master':
bpo-35814: Allow unpacking in r.h.s of annotated assignment expressions 
(GH-13760)
https://github.com/python/cpython/commit/8565f6b6db0fa9f65449b532a5056a98bad3dc37


--
nosy: +pablogsal

___
Python tracker 

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

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
pull_requests: +13656
pull_request: https://github.com/python/cpython/pull/13760

___
Python tracker 

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

[issue34155] email.utils.parseaddr mistakenly parse an email

[jpic]

jpic  added the comment:

Thanks for your explanation, but in perspective with other invalid
domains, such as "foo." currently resulting in an empty string too:

>>> email.message_from_string('From: 
>>> a@foo.',policy=email.policy.default)['from'].addresses[0].domain
''

Do you think this should also change the value of domain to "foo." ?

Also yes with parseaddr it seems that domain is an empty string if it
didn't find a valid domain at all, which is pretty safe in case of
malicious injection attempt - if that's what we're trying to save
python programs from, a clarification of the objective of the patch
would be welcome.

--

___
Python tracker 

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

[issue31006] typing.NamedTuple should add annotations to its constructor (__new__) parameters.

[Batuhan]

Batuhan  added the comment:

IMHO this issue can be closed with this commit 
(https://github.com/python/typing/commit/435b29470c7d3e87055531f65681bee9746ab999)

--
nosy: +BTaskaya

___
Python tracker 

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

[issue34763] Python lacks 0x4E17

[林自均]

林自均  added the comment:

"丗" means "30" in Japanese. However, it is a variant Chinese character to "世", 
where "世" means "world" in Chinese.

I'm not sure if this information makes any difference.

--
nosy: +johnlinp

___
Python tracker 

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

[issue37139] Inconsistent behavior of email.header.decode_header

[Louis Abraham]

New submission from Louis Abraham :

Hi,

(this is my first issue btw)

I think 

 has a broken behavior.

It returns a list of `(decoded_string, charset)` pairs. However, 
`decoded_string` can be either a string or bytes.
I have no preference but it should really be of one type.

--
messages: 344392
nosy: louis.abra...@yahoo.fr
priority: normal
severity: normal
status: open
title: Inconsistent behavior of email.header.decode_header

___
Python tracker 

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

[issue34788] ipaddress module fails on rfc4007 scoped IPv6 addresses

[Oleksandr Pavliuk]

Change by Oleksandr Pavliuk :


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

___
Python tracker 

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

[issue32052] Provide access to buffer of asyncio.StreamReader

[Bruce Merry]

Bruce Merry  added the comment:

Ok, I'll open a separate issue to allow a tuple of possible separators.

--
nosy: +bmerry

___
Python tracker 

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

[issue37140] ctypes change made clang fail to build

[Petr Viktorin]

New submission from Petr Viktorin :

Hello,
I haven't investigated this fully yet, and won't be able to find time today. 
I'm forwarding the report here in case someone familiar with the code wants to 
take a look.

On Fedora, "clang" fails to build with Python 3.8, probably due this change 
(which was supposed to be Windows-only):
https://github.com/python/cpython/commit/32119e10b792ad7ee4e5f951a2d89ddbaf111cc5#diff-998bfefaefe2ab83d5f523e18f158fa4R413

According to serge_sans_paille: if ``self->b_ptr`` contains pointer, the 
``memcpy`` creates sharing, and this is dangerous: if a ``__del__`` happens to 
free the original pointer, we end up with a dangling reference in ``new_ptr``. 
As far as I can tell, this is what happens in the clang bindings code.

Fedora discussion with link to logs: 
https://bugzilla.redhat.com/show_bug.cgi?id=1715016

--
components: ctypes
messages: 344394
nosy: petr.viktorin
priority: normal
severity: normal
status: open
title: ctypes change made clang fail to build
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

[issue35947] Update libffi_msvc to current version of libffi

[Petr Viktorin]

Petr Viktorin  added the comment:

Possible regression caused by this change: https://bugs.python.org/issue37140

--
nosy: +petr.viktorin

___
Python tracker 

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

[issue37139] Inconsistent behavior of email.header.decode_header

[SilentGhost]

SilentGhost  added the comment:

This seem like a duplicate of #24797. I hope the answer given there applies.

--
components: +email
nosy: +SilentGhost, barry, r.david.murray
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> email.header.decode_header return type is not consistent
type:  -> behavior

___
Python tracker 

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

[issue37141] Allow multiple separators in StreamReader.readuntil

[Bruce Merry]

New submission from Bruce Merry :

Text-based protocols sometimes allow a choice of newline separator - I work 
with one that allows either \r or \n. Unfortunately that doesn't work with 
StreamReader.readuntil, which only accepts a single separator, so I've had to 
do some hacky things to obtain lines without having to 

>From discussion in issue 32052, it sounded like extending 
>StreamReader.readuntil to support a tuple of separators would be feasible.

--
components: asyncio
messages: 344397
nosy: asvetlov, bmerry, yselivanov
priority: normal
severity: normal
status: open
title: Allow multiple separators in StreamReader.readuntil
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

[issue37141] Allow multiple separators in StreamReader.readuntil

[Andrew Svetlov]

Andrew Svetlov  added the comment:

Would you make a PR?
I guess to modify Stream.readuntil() 
StreamReader is deprecated, I'm not sure if we should add new functionality to 
this class.

--

___
Python tracker 

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

[issue37140] ctypes change made clang fail to build

[serge-sans-paille]

Change by serge-sans-paille :


--
nosy: +serge-sans-paille

___
Python tracker 

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

[issue36656] Race conditions due to os.link and os.symlink POSIX specification

[Tom Hale]

Change by Tom Hale :


--
title: Allow os.symlink(src, target, force=True) to prevent race conditions -> 
Race conditions due to os.link and os.symlink POSIX specification

___
Python tracker 

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

[issue37141] Allow multiple separators in StreamReader.readuntil

[Bruce Merry]

Bruce Merry  added the comment:

I wasn't aware of that deprecation - it doesn't seem to be mentioned at 
https://docs.python.org/3.8/library/asyncio-stream.html. What is the 
replacement?

--

___
Python tracker 

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

[issue37139] Inconsistent behavior of email.header.decode_header

[Louis Abraham]

Louis Abraham  added the comment:

Indeed, this is exactly the same (I should have researched more, my bad).

The problem is that I'm using mailbox.Maildir which uses the Compat32 API.

Do you think I should create an issue for Maildir to support the new 
EmailMessage API?

--

___
Python tracker 

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

[issue34467] No mechanism to abort created coroutine or suppress not-awaited warning

[Andrew Svetlov]

Andrew Svetlov  added the comment:

Could you consider passing (async_func, args, kwargs) tuple instead 
async_func(*args, **kwargs) coroutine?

Looks like it solves your problem and doesn't require asyncio changes

--

___
Python tracker 

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

[issue36231] no "proper" header files on macOS 10.14 Mojave

[Ned Deily]

Change by Ned Deily :


--
pull_requests: +13658
pull_request: https://github.com/python/cpython/pull/13773

___
Python tracker 

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

[issue37134] [EASY] Use PEP570 syntax in the documentation

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

Thank you, Raymond, for sharing your concerns regarding this. I am sorry you 
disagree with this change.

I would want to expose the reasons I think this is important and justified, but 
please, don't read this
as a way of dismissing your concerns; I really respect your opinion and 
judgment (as an example, I am waiting
until you are happy with the API in issue17005 even if that meant waiting 2 
years until the next release).

1) The docstrings for these functions already show the "/". As Matthias 
Bussonnier from IPython and Jupyter has expressed
multiple times, there are a ton of users that do not read html documentation 
and rely solely on the output from help (either
in Jupyter, IPython or CPython). These users find very strange that the 
signatures of the docstrings differ when they actually
check the html docs. Some examples of the docstrings:

>>> help(zlib.decompress)
decompress(data, /, wbits=15, bufsize=16384)
Returns a bytes object containing the uncompressed data.

>> help(codecs.register)
register(search_function, /)
Register a codec search function.

2) This communicates the users more explicitly how to call the function and 
what to expect when this happens,
which is the purpose of documenting signatures in the documentation. We are 
already documenting keyword-only
parameters for the same reasons.

3) This PR is not changing any of the signatures, is just documenting and 
informing users what the signature is
and how it will behave. Is just expressing information. The documentation must 
be user-friendly, but also needs to
be technical.

4) We are already documenting positional-only arguments in multiple other 
functions in the documentation. This PR just
continues doing that. Some examples of the many cases:

https://docs.python.org/3.8/library/functools.html#functools.partialmethod
https://docs.python.org/3.8/library/threading.html#threading.excepthook
https://docs.python.org/3.8/library/inspect.html#inspect.getcallargs
...

5) I give training sessions to different levels (people that are starting to 
program, Juniors and Seniors) and they are always
confused when the signature of the function in the documentation does not match 
the docstring or the actual way of calling the function.
This also includes when we use constructs like f(x, ...), f(x, [y=None,]), f(K) 
-> V or similar because they are not valid Python
signatures and they do not appear elsewhere. In general, my experience is that 
people want the signature documented as close as possible
to the real signature in the technical documentation.

I wished we could have iterate over this together having a good discussion 
before involving the steering council, and I am sorry
if you were afraid that your concerns would have not been listened to. Sadly, I 
have not answered before because it was 1:26 in the morning
here when you posted your message. I have left the PR open and opened an issue 
because is the normal workflow and because this allows people
to express here their opinion. 

I think this change is important, but I also think of working together and 
respecting and understanding everyone's point of view
is much more important. If you think me pushing for this change will impact 
somehow our ability to work together I will close the PR
and the issue.

For now, I won't do anything before the steering council decides what to do.

I apologize to everyone or the wall of text.

--

___
Python tracker 

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

[issue36048] Deprecate implicit truncating when convert Python numbers to C integers: use __index__, not __int__

[Mark Dickinson]

Change by Mark Dickinson :


--
pull_requests: +13659
pull_request: https://github.com/python/cpython/pull/13740

___
Python tracker 

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

[issue37141] Allow multiple separators in StreamReader.readuntil

[Andrew Svetlov]

Andrew Svetlov  added the comment:

Docs will be updated soon.
The change has landed a week ago, I had no time for docs update before 3.8 
beta. Sorry for that.

The idea is: StreamReader and StreamWriter are merged into just Stream, 
open_connection() is replaced with connect() etc.

--

___
Python tracker 

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

[issue37141] Allow multiple separators in StreamReader.readuntil

[Bruce Merry]

Bruce Merry  added the comment:

Ok. Does the new Stream still have a similar interface for readuntil i.e. is 
this still a relevant request against the new API? I'm happy to let deprecated 
APIs stay as-is.

--

___
Python tracker 

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

[issue37141] Allow multiple separators in StreamReader.readuntil

[Andrew Svetlov]

Andrew Svetlov  added the comment:

Yes, Stream supports all StreamReader and StreamWriter methods

--

___
Python tracker 

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

[issue17576] PyNumber_Index() is not int-subclass friendly (or operator.index() docos lie)

[Mark Dickinson]

Change by Mark Dickinson :


--
nosy:  -mark.dickinson

___
Python tracker 

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

[issue36656] Race conditions due to os.link and os.symlink POSIX specification

[Tom Hale]

Tom Hale  added the comment:

Serhiy wrote

> Detected problem is better than non-detected problem.

I agree. I also assert that no problem (via a shutil wrapper) is better than a 
detected problem which may not be handled.

While it's up to the programmer to handle exceptions, it's only systems 
programmers who will realise that there is a sometimes-occurring exception 
which should be handled.

So most people won't handle it. They don't know that they need to.

The shutil os.link and os.symlink wrappers under discussion on python-ideas 
prevent non-system-programmers from needing to know about the race-condition 
case (and correctly handling it).

If something is difficult to get right, then let's put it in shutil and save 
everyone reinventing the wheel.

3 specific cases in which an atomic link replacement would be useful are listed 
here:

https://code.activestate.com/lists/python-ideas/56195/

--

___
Python tracker 

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

[issue37141] Allow multiple separators in Stream.readuntil

[Bruce Merry]

Bruce Merry  added the comment:

Ok, I've changed the issue title to refer to Stream. Since this would be a new 
feature, I assume it's off the table for 3.8, but I'll see if I get time to 
implement a PR in time for 3.9 (and get someone at work to sign off on the 
contributor agreement, which might be the harder part).

Thanks for the quick and helpful responses.

--
title: Allow multiple separators in StreamReader.readuntil -> Allow multiple 
separators in Stream.readuntil

___
Python tracker 

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

[issue17576] PyNumber_Index() is not int-subclass friendly (or operator.index() docos lie)

[Mark Dickinson]

Mark Dickinson  added the comment:

I've closed the PR. Reassigning back to Ethan.

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

___
Python tracker 

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

[issue36231] no "proper" header files on macOS 10.14 Mojave

[Ned Deily]

Ned Deily  added the comment:


New changeset 0288dd6a5192074fcd5aa0db5d3513c3880209ca by Ned Deily in branch 
'master':
bpo-36231:  Support building on macOS without /usr/include (GH-13773)
https://github.com/python/cpython/commit/0288dd6a5192074fcd5aa0db5d3513c3880209ca


--

___
Python tracker 

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

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

I am unable to reproduce this locally, will post here a backtrace if I manage 
to do so.

--

___
Python tracker 

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

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

[Ned Deily]

Change by Ned Deily :


--
pull_requests: +13660
pull_request: https://github.com/python/cpython/pull/13773

___
Python tracker 

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

[issue37116] Use PEP 570 syntax for positional-only parameters

[STINNER Victor]

STINNER Victor  added the comment:

See also bpo-37134.

--
nosy: +vstinner

___
Python tracker 

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

[issue37134] [EASY] Use PEP570 syntax in the documentation

[STINNER Victor]

STINNER Victor  added the comment:

See also bpo-37116.

--
nosy: +vstinner

___
Python tracker 

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

[issue37116] Use PEP 570 syntax for positional-only parameters

[STINNER Victor]

STINNER Victor  added the comment:

> New changeset 2085bd0877e17ad4d98a4586d5eabb6faecbb190 by Serhiy Storchaka in 
> branch 'master':
> bpo-37116: Use PEP 570 syntax for positional-only parameters. (GH-13700)
> https://github.com/python/cpython/commit/2085bd0877e17ad4d98a4586d5eabb6faecbb190

Oh thanks, this change is really nice! It shows that PEP 570 is really useful!

--

___
Python tracker 

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

[issue35431] Add a function for computing binomial coefficients to the math module

[Steven D'Aprano]

Steven D'Aprano  added the comment:

For what its worth, there are concrete, practical applications for 
binomial coefficients with negative arguments. They are used in 
fractional calculus

https://nrich.maths.org/1365

which in turn has applications in physics, chemistry and other sciences:

https://en.wikipedia.org/wiki/Fractional_calculus#Applications

Take that however you see fit :-)

My own preference is for a comb() function that returns 0 for out of 
bounds values (e.g. "choose 5 items from 4"), and a seperate binomial() 
function that accepts any positive or negative integer values. Even I 
think that fractional and complex arguments are probably a bit too 
exotic for the std lib -- that's Mathematica territory.

And yes, Mathematica does accept fractional and complex arguments to 
the choose() function.

https://www.wolframalpha.com/input/?i=choose%28sqr%28-3.5%29,+sqrt%28-4%2Bi%29%29

--

___
Python tracker 

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

[issue37142] test_asyncio timed out on AMD64 FreeBSD CURRENT Shared 3.x

[STINNER Victor]

New submission from STINNER Victor :

https://buildbot.python.org/all/#/builders/168/builds/1135

running: test_asyncio (23 min 23 sec)
running: test_asyncio (23 min 53 sec)
running: test_asyncio (24 min 23 sec)
running: test_asyncio (24 min 53 sec)
0:38:48 load avg: 0.32 [423/423/1] test_asyncio crashed (Exit code 1)
Timeout (0:25:00)!
Thread 0x000800ac3000 (most recent call first):
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/selectors.py", 
line 558 in select
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/base_events.py",
 line 1808 in _run_once
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/base_events.py",
 line 563 in run_forever
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/base_events.py",
 line 595 in run_until_complete
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/test_asyncio/test_streams.py",
 line 1531 in test_stream_server_abort
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/case.py",
 line 628 in _callTestMethod
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/case.py",
 line 671 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/case.py",
 line 731 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 122 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 84 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 122 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 84 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 122 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 84 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 122 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 84 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 122 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/suite.py",
 line 84 in __call__
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/unittest/runner.py",
 line 176 in run
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/support/__init__.py",
 line 1984 in _run_suite
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/support/__init__.py",
 line 2080 in run_unittest
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest.py",
 line 203 in _test_module
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest.py",
 line 228 in _runtest_inner2
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest.py",
 line 264 in _runtest_inner
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest.py",
 line 135 in _runtest
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest.py",
 line 187 in runtest
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py",
 line 66 in run_tests_worker
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/main.py",
 line 611 in _main
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/main.py",
 line 588 in main
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/main.py",
 line 663 in main
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/regrtest.py",
 line 46 in _main
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/regrtest.py",
 line 50 in 
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/runpy.py", line 
85 in _run_code
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/runpy.py", line 
192 in _run_module_as_main

== Tests result: FAILURE ==


...

==
ERROR: test_stdin_stdout 
(test.test_asyncio.test_subprocess.SubprocessMultiLoopWatcherTests)
--
Traceback (most recent call last):
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/test_asyncio/test_subprocess.py",
 line 130, in test_stdin_stdout
exitcode, stdout = self.loop.run_until_complete(task)
  File 
"/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/asyncio/base_events.py",
 line 608, in run_until_complete
return 

[issue37142] test_asyncio timed out on AMD64 FreeBSD CURRENT Shared 3.x

[STINNER Victor]

Change by STINNER Victor :


--
nosy: +pablogsal

___
Python tracker 

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

[issue37143] multiprocessing crashed with EXCEPTION_ACCESS_VIOLATION on Python on x86 Windows7 3.x

[STINNER Victor]

New submission from STINNER Victor :

Maybe it's related to bpo-33608:
https://bugs.python.org/issue33608#msg340143


https://buildbot.python.org/all/#/builders/58/builds/2558

0:42:36 load avg: 5.63 [299/423/1] test_venv crashed (Exit code 1)
Timeout (0:35:00)!
Thread 0x0e00 (most recent call first):
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\subprocess.py", 
line 1332 in _readerthread
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\threading.py", line 
865 in run
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\threading.py", line 
923 in _bootstrap_inner
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\threading.py", line 
885 in _bootstrap

Thread 0x0150 (most recent call first):
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\subprocess.py", 
line 1332 in _readerthread
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\threading.py", line 
865 in run
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\threading.py", line 
923 in _bootstrap_inner
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\threading.py", line 
885 in _bootstrap

Thread 0x0d40 (most recent call first):
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\threading.py", line 
1015 in _wait_for_tstate_lock
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\threading.py", line 
999 in join
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\subprocess.py", 
line 1361 in _communicate
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\subprocess.py", 
line 999 in communicate
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\test_venv.py", 
line 40 in check_output
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\test_venv.py", 
line 327 in test_multiprocessing
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\case.py", 
line 628 in _callTestMethod
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\case.py", 
line 671 in run
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\case.py", 
line 731 in __call__
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\suite.py", 
line 122 in run
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\suite.py", 
line 84 in __call__
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\suite.py", 
line 122 in run
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\suite.py", 
line 84 in __call__
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\suite.py", 
line 122 in run
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\suite.py", 
line 84 in __call__
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\unittest\runner.py",
 line 176 in run
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\support\__init__.py",
 line 1984 in _run_suite
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\support\__init__.py",
 line 2080 in run_unittest
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\libregrtest\runtest.py",
 line 203 in _test_module
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\libregrtest\runtest.py",
 line 228 in _runtest_inner2
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\libregrtest\runtest.py",
 line 264 in _runtest_inner
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\libregrtest\runtest.py",
 line 135 in _runtest
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\libregrtest\runtest.py",
 line 187 in runtest
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\libregrtest\runtest_mp.py",
 line 66 in run_tests_worker
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\libregrtest\main.py",
 line 611 in _main
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\libregrtest\main.py",
 line 588 in main
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\libregrtest\main.py",
 line 663 in main
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\regrtest.py", 
line 46 in _main
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\regrtest.py", 
line 50 in 
  File "D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\runpy.py", 
line 85 in _run_code
  File "D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\runpy.py", 
line 192 in _run_module_as_main

...

ERROR: test_multiprocessing (test.test_venv.BasicTest)
--
Traceback (most recent call last):
  File 
"D:\cygwin\home\db3l\buildarea\3.x.bolen-windows7\build\lib\test\

[issue37142] test_asyncio timed out on AMD64 FreeBSD CURRENT Shared 3.x

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


--
components: +asyncio
nosy: +asvetlov, yselivanov

___
Python tracker 

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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[STINNER Victor]

STINNER Victor  added the comment:

> So far so good. :)  I'll keep an eye on things and if the buildbots are still 
> happy then I'll add back _PyEval_FinishPendingCalls() in _Py_FinalizeEx() in 
> a few days.

Another crash, on Windows:
https://bugs.python.org/issue37143

It sounds like the exactly same bug is back: same crash on same buildbots.

--

___
Python tracker 

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

[issue26219] implement per-opcode cache in ceval

[Inada Naoki]

Inada Naoki  added the comment:


New changeset 91234a16367b56ca03ee289f7c03a34d4cfec4c8 by Inada Naoki in branch 
'master':
bpo-26219: per opcode cache for LOAD_GLOBAL (GH-12884)
https://github.com/python/cpython/commit/91234a16367b56ca03ee289f7c03a34d4cfec4c8


--

___
Python tracker 

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

[issue26219] implement per-opcode cache in ceval

[Inada Naoki]

Inada Naoki  added the comment:

I committed cache only for LOAD_GLOBAL, which is much simpler than
LOAD_ATTR or LOAD_METHOD.

Caches for other instructions will be implemented 3.9 or later.

--

___
Python tracker 

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

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

[Inada Naoki]

Change by Inada Naoki :


--
pull_requests: +13661
pull_request: https://github.com/python/cpython/pull/12884

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11628

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11627

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11626

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11594

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11593

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11249

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11248

___
Python tracker 

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

[issue26219] implement per-opcode cache in ceval

[Inada Naoki]

Change by Inada Naoki :


--
pull_requests: +13662
pull_request: https://github.com/python/cpython/pull/13775

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11595

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11334

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11258

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11335

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11523

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11524

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11587

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11476

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11584

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11583

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -10917

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -10918

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11257

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11586

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11263

___
Python tracker 

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

[issue35537] use os.posix_spawn in subprocess

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests:  -11264

___
Python tracker 

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

[issue35431] Add a function for computing binomial coefficients to the math module

[Mark Dickinson]

Mark Dickinson  added the comment:

Given that (a) we're right up against feature freeze, and (b) the discussions 
about API already happened in plenty of good time some months ago, leading to 
agreement on the initial API, I think we should avoid any last-minute changes 
and stick with what we have for 3.8. Then we can have a more relaxed discussion 
about what, if anything, should be changed for 3.9.

--

___
Python tracker 

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

[issue26219] implement per-opcode cache in ceval

[Inada Naoki]

Inada Naoki  added the comment:


New changeset 395420e2a35937fa9777fc3c8b0086629db95e27 by Inada Naoki in branch 
'master':
bpo-26219: remove unused code (GH-13775)
https://github.com/python/cpython/commit/395420e2a35937fa9777fc3c8b0086629db95e27


--

___
Python tracker 

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

[issue33694] test_asyncio: test_start_tls_server_1() fails on Python on x86 Windows7 3.7 and 3.x

[Inada Naoki]

Change by Inada Naoki :


--
pull_requests: +13663
pull_request: https://github.com/python/cpython/pull/13775

___
Python tracker 

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

[issue37030] Lib/cmd.py: Hide undocumented commands in help and completenames

[Rémi Lapeyre]

Rémi Lapeyre  added the comment:

It will be done automatically after someone validated the 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

[issue37144] tarfile.open: improper handling of path-like object

[DM]

New submission from DM :

According to the documentation, tarfile.open accepts a path-like object since 
Python 3.6

However, it is not the case when writing a compressed gzip (w|gz).
See the attached file for minimal POC

Note 1: tested on 3.6 and 3.7
Note 2: https://docs.python.org/3.6/library/tarfile.html#tarfile.open

--
components: Library (Lib)
files: poc.py
messages: 344423
nosy: dm
priority: normal
severity: normal
status: open
title: tarfile.open: improper handling of path-like object
type: behavior
versions: Python 3.6, Python 3.7
Added file: https://bugs.python.org/file48386/poc.py

___
Python tracker 

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

[issue37143] multiprocessing crashed with EXCEPTION_ACCESS_VIOLATION on Python on x86 Windows7 3.x

[STINNER Victor]

STINNER Victor  added the comment:

On Windows 10, I ran "python -m test test_venv -m test_multiprocessing -F" for 
8 min, and "python -m test test_multiprocessing_spawn" in parallel. I failed to 
reproduce the issue.

--

___
Python tracker 

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

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

[STINNER Victor]

STINNER Victor  added the comment:

https://bugs.python.org/issue33608#msg340075:

> My procedure to reproduce the crash on FreeBSD:
> https://bugs.python.org/issue36114#msg337092

I ran this test for 20 min on the FreeBSD CURRENT buildbot: I failed to 
reproduce the bug.

--

___
Python tracker 

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

[issue37137] test_asyncio: test_cancel_gather_2() dangling thread

[STINNER Victor]

STINNER Victor  added the comment:

https://buildbot.python.org/all/#/builders/167/builds/1188

Variant:

test_cancel_both_task_and_inner_future 
(test.test_asyncio.test_tasks.CTaskSubclass_PyFuture_Tests) ... ok
test_cancel_current_task 
(test.test_asyncio.test_tasks.CTaskSubclass_PyFuture_Tests) ... ok
test_cancel_gather_1 (test.test_asyncio.test_tasks.CTaskSubclass_PyFuture_Tests)
Ensure that a gathering future refuses to be cancelled once all ... Warning -- 
threading_cleanup() failed to cleanup -1 threads (count: 0, dangling: 1)
Dangling thread: <_MainThread(MainThread, started 34389124096)>
ok
test_cancel_gather_2 
(test.test_asyncio.test_tasks.CTaskSubclass_PyFuture_Tests) ... ok
test_cancel_inner_future 
(test.test_asyncio.test_tasks.CTaskSubclass_PyFuture_Tests) ... ok
test_cancel_task_catching 
(test.test_asyncio.test_tasks.CTaskSubclass_PyFuture_Tests) ... ok

--

___
Python tracker 

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

[issue37137] test_asyncio: test_cancel_gather_2() dangling thread

[STINNER Victor]

STINNER Victor  added the comment:

See also bpo-34037: "asyncio: BaseEventLoop.close() shutdowns the executor 
without waiting causing leak of dangling threads".

--

___
Python tracker 

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

[issue37137] test_asyncio: test_cancel_gather_2() dangling thread

[STINNER Victor]

Change by STINNER Victor :


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

___
Python tracker 

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

[issue37135] test_multiprocessing_spawn segfaults on AMD64 FreeBSD CURRENT Shared 3.x

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

Adding the release manager to consider this

--
nosy: +lukasz.langa

___
Python tracker 

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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[STINNER Victor]

Change by STINNER Victor :


--
pull_requests: +13665
pull_request: https://github.com/python/cpython/pull/13780

___
Python tracker 

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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[STINNER Victor]

STINNER Victor  added the comment:

> It sounds like the exactly same bug is back: same crash on same buildbots.

Since it became clear to me that the change broke multiple buildbots and nobody 
is able to investigate the issue, I wrote PR 13780 to revert the change:
https://pythondev.readthedocs.io/ci.html#revert-on-fail

--

___
Python tracker 

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

[issue34763] Treat U+4E17 as a numeric value

[Raymond Hettinger]

Change by Raymond Hettinger :


--
title: Python lacks 0x4E17 -> Treat U+4E17 as a numeric value

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


--
pull_requests: +13666
pull_request: https://github.com/python/cpython/pull/13781

___
Python tracker 

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

[issue37087] Adding native id support for openbsd

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 0b9956e9162d8723c2a30ff316ecc25e54459fb1 by Victor Stinner (David 
Carlier) in branch 'master':
bpo-37087: Adding native ID support for OpenBSD (GH-13654)
https://github.com/python/cpython/commit/0b9956e9162d8723c2a30ff316ecc25e54459fb1


--
nosy: +vstinner

___
Python tracker 

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

[issue34155] email.utils.parseaddr mistakenly parse an email

[Abhilash Raj]

Abhilash Raj  added the comment:

I agree that we currently abandon parsing (raise `HeaderParseError`) when we 
encounter a unexpected token when parsing domain (expected token is 
dot-atom-text).

However, that mechanism is meant to signal the higher level parser that we 
should look for a different type of token. In case of domain, we don't fallback 
to anything.

I believe we should fallback to `get_unstructured` when we do encounter an 
invalid domain (either `foo.` or `foo@exaomple` or `f...@example.com`) and 
register defect. But, the `.domain` attribute on the address class should be 
None if the domain is invalid.

My proposed solution of `get_unstrucutured` is perhaps not a great idea either 
since we would end up parsing more than we should (maybe we should parse until 
`>`?) in case of AddrList or something.

I would love to know what David and Barry think about this one?

--

___
Python tracker 

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

[issue34155] email.utils.parseaddr mistakenly parse an email

[Abhilash Raj]

Abhilash Raj  added the comment:

slight typo in the previous message:

s/fallback to `get_unstructured` /fallback to *something*/g

--

___
Python tracker 

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

[issue37137] test_asyncio: test_cancel_gather_2() dangling thread

[STINNER Victor]

STINNER Victor  added the comment:


New changeset 49a7e347976c9b39149ac7505b11ad6e9e2bdeec by Victor Stinner in 
branch 'master':
bpo-37137: Fix test_asyncio: use TestCase.set_event_loop() (GH-13779)
https://github.com/python/cpython/commit/49a7e347976c9b39149ac7505b11ad6e9e2bdeec


--

___
Python tracker 

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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[Eric Snow]

Eric Snow  added the comment:

Please wait on reverting.  I'm going to investigate.

@koobs, yeah, I'll send you a key.  Thanks! :)

--

___
Python tracker 

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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[Eric Snow]

Eric Snow  added the comment:

FWIW, the failures before were in test_io and test_multiprocessing_spawn, not 
test_asyncio.

--

___
Python tracker 

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

[issue35431] Add a function for computing binomial coefficients to the math module

[Raymond Hettinger]

Raymond Hettinger  added the comment:

I don't have a preference one way or the other (both ways have plausible 
arguments, error checking vs utility beyond simple combinatorics, and both ways 
have ample precedents).

That said, if we're going to ultimately relax the constraints, it would be 
better to do it now before the API is released.  

Even if we were already in feature freeze, it would be okay to change it (the 
purpose of a beta is to elicit end-user feedback which is what David has just 
given).

--

___
Python tracker 

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

[issue37087] Adding native id support for openbsd

[STINNER Victor]

STINNER Victor  added the comment:

Thanks David Carlier :-)

--
resolution:  -> fixed
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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[Eric Snow]

Eric Snow  added the comment:

I had really hoped to get this in for 3.8, as I may need it.  However, 
realistically I doubt it will take just a few minutes to resolve this.  With 
the beta 1 targeted for today it makes sense to revert my change. :(

(I may still try to convince our fearless RM to allow it in beta 2, but we'll 
see.)

--

___
Python tracker 

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

[issue37139] Inconsistent behavior of email.header.decode_header

[SilentGhost]

SilentGhost  added the comment:

There seems to be some work started in #32975. Perhaps, you'd like to revive it 
or contribute otherwise?

--

___
Python tracker 

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

[issue34763] Treat U+4E17 as a numeric value

[Xiang Zhang]

Xiang Zhang  added the comment:

unicode.org doesn't list "丗" as numeric so I think there is nothing we can do.

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

___
Python tracker 

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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[STINNER Victor]

STINNER Victor  added the comment:

> FWIW, the failures before were in test_io and test_multiprocessing_spawn,
not test_asyncio.

I am not aware of a test_asyncio issue related to this issue, only crashes
in multiprocessing. I bet on a similar crash than the previous attempt,
during shutdown.

--

___
Python tracker 

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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[STINNER Victor]

STINNER Victor  added the comment:


New changeset e225bebc1409bcf68db74a35ed3c31222883bf8f by Victor Stinner in 
branch 'master':
Revert "bpo-33608: Factor out a private, per-interpreter _Py_AddPendingCall(). 
(gh-13714)" (GH-13780)
https://github.com/python/cpython/commit/e225bebc1409bcf68db74a35ed3c31222883bf8f


--

___
Python tracker 

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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[STINNER Victor]

STINNER Victor  added the comment:

What annoy me the most in this issue is that I am unable to reproduce it. Even 
directly on the FreeBSD CURRENT buildbot, I failed to reproduce rhe crash even 
when I stressed the buildbot and the test.

On the other side, when the CI runs the test suite, crashes are likely!?

These bugs are the worst.

IMHO we must make multiprocessing more deterministic. Python 3.8 is better, but 
there are still many known issues.
https://pythondev.readthedocs.io/unstable_tests.html

test_venv multiprocessing test misuses the multiprocessing issue, it emirs a 
ResourceWarning.

--

___
Python tracker 

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

[issue33608] Add a cross-interpreter-safe mechanism to indicate that an object may be destroyed.

[STINNER Victor]

STINNER Victor  added the comment:

My bet is that multiprocessing triggers a bug in daemon threads. 
Multiprocessing is using and abusing daemon threads. For example, as I wrote, 
test_venv misuses the multiprocessing API and implicitly let Python release (or 
maybe not!) "resources" where "resources" can be processes and threads, likely 
including daemon threads.

Eric: I would love to give you access to a VM where I can reproduce the bug 
but... I failed to reproduce the bug today :-(

I would suggest to write a stress test for daemon threads:

* spawn daemon threads: 4x times threads than CPU to stress the system
* each thread would sleep a random number of milliseconds and then execute a 
few pure Python instructions
* spawns these threads, wait a random number of milliseconds, and then "exit 
Python"

The race condition is that daemon threads may or maybe run during Python 
finalization depending on the delay.

Maybe you can make the crash more likely by adding a sleep of a few *seconds* 
before the final exit. For example, at the exit of Py_RunMain().

Last time I saw the crash, it was a thread which uses a Python structure 
whereas the memory of the structure was freed (filled with a random pattern by 
debug hooks on memory allocators).

Ah, either use a debug build of Python, or use PYTHONMALLOC=debug, or -X dev 
command line option, to fill freed memory with a specific pattern, to trigger 
the crash.

... Good luck.

--

___
Python tracker 

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