Change by Stefano Rivera :
--
nosy: +stefanor
___
Python tracker
<https://bugs.python.org/issue5>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefano Rivera :
--
nosy: +stefanor
___
Python tracker
<https://bugs.python.org/issue43976>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefano Rivera :
--
nosy: +stefanor
___
Python tracker
<https://bugs.python.org/issue45413>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefano Rivera :
--
nosy: +stefanor
___
Python tracker
<https://bugs.python.org/issue45428>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Stefano Rivera :
Originally reported against pypy3 in Ubuntu
https://bugs.launchpad.net/ubuntu/+source/pypy3/+bug/1920675
$ ./python
Python 3.10.0a5+ (heads/master:ffa55d21b4, May 23 2021, 08:14:50)
[GCC 10.2.1 20210110] on linux
Type "help", "copyr
Change by Stefano Rivera :
--
nosy: +stefanor
___
Python tracker
<https://bugs.python.org/issue43307>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefano Rivera :
--
nosy: +stefanor
___
Python tracker
<https://bugs.python.org/issue43312>
___
___
Python-bugs-list mailing list
Unsubscribe:
Stefano Rivera added the comment:
On Linux, the reproducer in https://bugs.python.org/issue38501#msg354813 fails
on ac10e0c93218627d1a639db0b7b41714c5f6a883^ and passes on
ac10e0c93218627d1a639db0b7b41714c5f6a883, which is why I say PR 19009 fixes it.
Not sure if there are any special
Stefano Rivera added the comment:
Looks like it was fixed by PR 19009 (bpo-39360)).
--
___
Python tracker
<https://bugs.python.org/issue38501>
___
___
Python-bug
Stefano Rivera added the comment:
This change seems to be causing a deadlock in multiprocessing shut-down:
bpo-38501
--
nosy: +stefanor
___
Python tracker
<https://bugs.python.org/issue35
Stefano Rivera added the comment:
A bisect points at https://github.com/python/cpython/pull/11488 being the
change that introduced this hang (bpo-35493)
--
nosy: +stefanor
___
Python tracker
<https://bugs.python.org/issue38
Stefano Rivera added the comment:
> whether this would confuse users since they will simply get an ImportError
> instead of some other error and thus will they be able to realize why there's
> a problem?
It's the same behaviour we have for any other module on the import path, that
Stefano Rivera added the comment:
I wouldn't say it's *entirely* Debian-specific. It just bites anyone who
actually needs these tags to differentiate between built extensions. (Mostly
Debian)
Yes, changing the tag is a more complete solution. It just seemed that that
option was decided
New submission from Stefano Rivera:
setup.py build for a library using py_limited_api will always generate a stable
ABI tagged shared library, even under the pydebug interpreter.
This means that extensions that are built for a pydebug interpreter may be
accidentally (and brokenly) imported
Changes by Stefano Rivera pyt...@rivera.za.net:
--
nosy: +stefanor
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13508
___
___
Python-bugs-list
Changes by Stefano Rivera pyt...@rivera.za.net:
--
nosy: +stefanor
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3990
___
___
Python-bugs-list
16 matches
Mail list logo