Steve Dower added the comment:
Thanks!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Steve Stagg added the comment:
Looks like it was introduced by
https://github.com/python/cpython/commit/7ea143ae795a9fd57eaccf490d316bdc13ee9065:
bpo-29469: Move constant folding to AST optimizer (GH-2858)
--
nosy: +stestagg
___
Python tracker
Steve Stagg added the comment:
In python 3.7/8, It's a stack overflow in the constant folding code.
On master, the overflow seems to come out of validate_expr.c.
* thread #1, name = 'python3', stop reason = signal SIGSEGV: invalid address
(fault address: 0x7f7feff
Steve Stagg added the comment:
It looks like the segfault was fixed in
https://github.com/python/cpython/commit/88c2cfd9ffbcfc43fd1364f2984852a819547d43
as part of https://bugs.python.org/issue41832.
The code in this area of typeobject.c looks a bit different, now, but the
backport seems
Steve Dower added the comment:
Replicating also requires installing Java (I got as far as the build failing),
which is going to have to wait until I have time to spin up a throwaway machine
:)
That exception is a normal part of the import process and should be being
handled. It's no
Steve Dower added the comment:
This has been blocking it:
https://discuss.python.org/t/pep-641-using-an-underscore-in-the-version-portion-of-python-3-10-compatibility-tags/5513
Pablo (PEP delegate) has just posted his rejection though, so it will be fixed
when packaging changes back to &quo
Steve Dower added the comment:
Sorry, I haven't had a chance to set up a test machine with all the
requirements.
It's almost certainly something in jpype, to be clear. Most likely it loads a
DLL that hasn't been loaded yet, but does it under conditions where it won't
lo
Steve Dower added the comment:
Monkeypatching native types looks suspect as anything, but probably not the
cause here. Good luck :)
So I checked some of our code around dynamic loads and it's got to be caused by
the loader in our LoadLibrary call, not when we call your module init fun
Steve Dower added the comment:
You'll find it leads up to a LoadLibraryExW call in Python/dynload_win.c that
is failing with ERROR_DLL_INIT_FAILED (1114) in GetLastError(). From that point
on, it's looking solely at _jpype.pyd and its dependencies, and it could be any
of them
Steve Stagg added the comment:
Confirmed that bpo-42500 fixes this traceback, in commit 4e7a69bdb6
Parent commit:
user@obsidian ~/t/f/cpython (master)> git checkout 93a0ef7
Note: switching to '93a0ef7'.
HEAD is now at 93a0ef7647 Correct return type in
Modules/_ssl.c::sslmodu
Steve Stagg added the comment:
Sorry, previous should have read "Fixes the abort"
--
___
Python tracker
<https://bugs.python.org/issue42651>
___
___
Steve Stagg added the comment:
This was also fixed by bpo-42500, in commit 4e7a69bdb6
===
user@obsidian ~/t/f/cpython ((93a0ef76…))> git checkout 4e7a69bd^
HEAD is now at 93a0ef7647 Correct return type in
Modules/_ssl.c::sslmodule_legacy (GH-23609)
+ make distclean
+ CFLAGS=-O0
+ ./config
Steve Dower added the comment:
> Everything succeeds, then we get an extra successful request for FlsFree then
> it immediately returns with a fail.
That makes it sound like the CRT is uninitialising itself, so this may be a
conflict between statically linked vcruntime140.d
Steve Dower added the comment:
Looking at the winapi_thunks.cpp source file from the CRT, it may be that
LCIDToLocaleName is failing to be loaded for some reason. That's the one that
comes after LCMapStringEx, so if it's failing, that could abort the whole
process.
Alt
Steve Dower added the comment:
> I recommend first doing a capture of these functions first
I don't think that'll be necessary - the logging output ought to be enough.
Capturing or redirecting those functions would be great if the debugger was
working, but since that spoils
Steve Dower added the comment:
It sounds like you need administrative permissions on your device.
Can I suggest searching the Microsoft Store for Python 3.9 and getting it that
way? That installer shouldn't have this issue.
--
___
Python tr
Steve Dower added the comment:
I doubt there's anything more we can do about Windows swallowing an access
violation and turning it into a generic error. There's a very low chance you'd
have found any notes about it in the docs, so this bug will probably stand as
the best avai
Steve Stagg added the comment:
Likely duplicate of Issue42609, Probably fixed by bpo-42609
--
nosy: +stestagg
___
Python tracker
<https://bugs.python.org/issue42
Steve Stagg added the comment:
Confirmed fixed by https://github.com/python/cpython/pull/23744:
Traceback (most recent call last):
File "/home/sstagg/tmp/fuzztest/cpython/../test.py", line 4, in
print(ast.literal_eval("mylist"+"+mylist"*n))
File "/
Steve Stagg added the comment:
PR: https://github.com/python/cpython/pull/23744 stops this from segfaulting.
It does however raise a RecursionError:
RecursionError: maximum recursion depth exceeded during compilation
As per https://bugs.python.org/issue42609#msg382910, Serhiy implies that
Steve Stagg added the comment:
As with the other issues, the underlying segfault is fixed in
PR: https://github.com/python/cpython/pull/23744. It does however raise a
RecursionError:
RecursionError: maximum recursion depth exceeded during compilation
As per https://bugs.python.org
Steve Stagg added the comment:
As with the other ones,
PR: https://github.com/python/cpython/pull/23744 stops this from segfaulting.
It does however raise a RecursionError:
RecursionError: maximum recursion depth exceeded during compilation
As per https://bugs.python.org/issue42609
Steve Stagg added the comment:
Minimal test case:
import sys, threading
def run():
for i in range(1000):
sys.stderr.write(' =.= ')
if __name__ == '__main__':
threading.Thread(target=run, daemon=True).start()
===
I think this is expected beha
Steve Stagg added the comment:
fyi, Issue42712, Issue42712, Issue42714, Issue42715, Issue42716 all seem to be
variants of the same underlying problem
--
___
Python tracker
<https://bugs.python.org/issue42
Steve Merritt added the comment:
Thank you!
On Fri, Dec 25, 2020 at 11:05 AM Batuhan Taskaya
wrote:
>
> Change by Batuhan Taskaya :
>
>
> --
> resolution: -> fixed
> stage: patch review -> resolved
> status: open -> closed
>
> _
Steve Stagg added the comment:
I think the problem here is that the issue can only really be detected late on
during interpreter shutdown.
This makes recovery very hard to do. Plus the thread termination has left
shared state in an unmanaged condition, so it's super dangerous to re-
Steve Stagg added the comment:
Looks like a duplicate of issue42717.
Causing a daemonic thread to terminate while doing IO will trigger the above
abort
--
nosy: +stestagg
___
Python tracker
<https://bugs.python.org/issue42
Steve Stagg added the comment:
Behaviour was changed in this commit:
---
commit ae3087c6382011c47db82fea4d05f8bbf514265d
Author: Mark Shannon
Date: Sun Oct 22 22:41:51 2017 +0100
Move exc state to generator. Fixes bpo-25612 (#1773)
Move exception state information from frame
Steve Stagg added the comment:
It's one of those ugly multithreading issues that's really hard to reason about
unfortunately.
In this case, it's not the size of the loop so much as you've discovered a way
to make it very likely that the background thread is doing IO
Steve Stagg added the comment:
If we take your minimal example (that /sometimes/ crashes), and look at what
python is doing:
import threading
t = threading.Thread(target=1, daemon=True).start()
---
The main thread does the following:
M1. Startup interpreter, parse code
M2. Import
Steve Stagg added the comment:
I'm sorry, I did get a bit confused earlier, I'd mentally switched to context
managers.
I agree this is a bug, and a kinda weird one!
I've narrowed it down to this:
If an exception causes flow to exit a for-loop that's powered by a gener
Steve Stagg added the comment:
Ok, so I now understand a bit more, and think it's not a bug! But explaining
it involves some fairly deep thinking about generators.
I'll try to explain my reasoning.
Let's take a simple example:
---
def foo():
try:
y
Steve Stagg added the comment:
That /is/ weird. I tried a few variations, and it looks like something is
being stored on the exception that is stopping the loop behaviour.
"except BaseException:" <- infinite loop
"except BaseException as e:" <- NO loop
Steve Stagg added the comment:
(sorry for spam!)
So, this is a retained reference issue.
If I change the script to be this:
---
import gc
DEPTH = 100
def foo():
global DEPTH
try:
yield
except BaseException as e:
DEPTH -= 1
if DEPTH <
Steve Stagg added the comment:
This is fixed by https://github.com/python/cpython/pull/23744
--
nosy: +stestagg
___
Python tracker
<https://bugs.python.org/issue42
Steve Dower added the comment:
Honestly, keeping a CI run alive is more work than just doing the extract and
push myself. I know this means it feels like you can't do as much yourself to
speed up the integration, but it really isn't going to slow it down that much.
FWIW, any co
Steve Dower added the comment:
If we can solve it, that would be better.
The access denied error looks a bit like a build process (or previous Python
build?) is still running that has locked one of the files. Restarting the PC is
the easiest way to make sure nothing is using them, or you
Change by Steve Dower :
--
pull_requests: +22955
pull_request: https://github.com/python/cpython/pull/24125
___
Python tracker
<https://bugs.python.org/issue41
Steve Dower added the comment:
New changeset afb71443788a7b20f9104243b3d8d37e3d12cfe2 by Steve Dower in branch
'master':
bpo-41837: Updated Windows installer to include OpenSSL 1.1.1i (GH-24125)
https://github.com/python/cpython/commit/afb71443788a7b20f9104243b3d8d3
Change by Steve Dower :
--
pull_requests: +22957
pull_request: https://github.com/python/cpython/pull/24127
___
Python tracker
<https://bugs.python.org/issue41
Steve Dower added the comment:
New changeset dd74c01d3bd2833f72ffe400a1d10b8583c0ba6a by Erlend Egeberg
Aasland in branch 'master':
bpo-42584: Update Windows installer to use SQLite 3.34.0 (GH-23675)
https://github.com/python/cpython/commit/dd74c01d3bd2833f72ffe400a1d10b
Steve Dower added the comment:
New changeset c8333931434389ae72da9eb0471054f4393249db by Steve Dower in branch
'3.9':
bpo-41837: Updated Windows installer to include OpenSSL 1.1.1i (GH-24125)
https://github.com/python/cpython/commit/c8333931434389ae72da9eb0471054
Change by Steve Dower :
--
pull_requests: +22961
pull_request: https://github.com/python/cpython/pull/24131
___
Python tracker
<https://bugs.python.org/issue41
Change by Steve Dower :
--
pull_requests: +22962
pull_request: https://github.com/python/cpython/pull/24132
___
Python tracker
<https://bugs.python.org/issue42
Steve Dower added the comment:
> Steve Dower, do you mind if I create backports for the Windows build as well?
Sorry, I've been doing it. They're just slow because I'm getting OpenSSL done
at the same time and they both keep causi
Steve Dower added the comment:
New changeset 86b1207dbb9201d1259d1ec7603e720e29ba9042 by Steve Dower in branch
'3.8':
bpo-41837: Updated Windows installer to include OpenSSL 1.1.1i (GH-24125)
https://github.com/python/cpython/commit/86b1207dbb9201d1259d1ec7603e72
Steve Dower added the comment:
New changeset 77d54710506b67e48b50bb1758fb31fc33a33c83 by Steve Dower in branch
'3.9':
bpo-42584: Update Windows installer to use SQLite 3.34.0 (GH-23675)
https://github.com/python/cpython/commit/77d54710506b67e48b50bb1758fb31
Change by Steve Dower :
--
pull_requests: +22963
pull_request: https://github.com/python/cpython/pull/24133
___
Python tracker
<https://bugs.python.org/issue42
Steve Dower added the comment:
I believe this is all done now.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Steve Dower :
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue42584>
___
___
Pyth
Steve Dower added the comment:
New changeset db91714faa6d3ede59003cdcc719a758160f3970 by Steve Dower in branch
'3.8':
bpo-42584: Update Windows installer to use SQLite 3.34.0 (GH-23675)
https://github.com/python/cpython/commit/db91714faa6d3ede59003cdcc719a7
Steve Dower added the comment:
Yeah, I think saying "return True if it provably exists and False if existence
cannot be proven (and never raise)" is a good general rule for
boolean-returning functions.
This definitely raises some edge cases where we can infer from certain error
Steve Dower added the comment:
I'm afraid not, at least not without breaking everyone who has hardcoded the
paths already. And I'm pretty sure that include directory is never used
anymore, either (at least not by distutils, and not by default).
The sysconfig module provides the pr
Steve Dower added the comment:
> From the perspective of the overall system, I think it would simplify
> integration and reduce complexity if we normalize folder structures across
> platforms instead of having different folder structures.
I agree. But from the perspective of not
Steve Dower added the comment:
That's the same patch that I'd write, and I agree, we should hook this.
If the fields are documented anywhere, we should add the audit event data to
get them into the table in the docs. Otherwise, that patch looks
New submission from Steve Stagg :
This was raised by Mats Wichmann on the python-dev list.
Commit : c71581c7a4192e6ba9a79eccc583aaadab300efa
bpo-42615: Delete redundant jump instructions that only bypass empty blocks
(GH-23733)
appears to have changed the behaviour of the following code
Steve Stagg added the comment:
Apologies, script should have read:
class B:
def __bool__(self):
print("bool(B)")
raise AttributeError("don't do that!")
b = B()
try:
if b:
pass
except AttributeError:
print("GOT ERROR")
Steve Stagg added the comment:
I don't believe this is a bug.
You've discovered a nasty corner-case, but I think it's expected behaviour.
There is a PEP open to make this behaviour a bit nicer:
https://www.python.org/dev/peps/pep-0533/
The fact that older Python 3.5/6 ver
Steve Stagg added the comment:
To be super pedantic, as per my understanding of:
"6.11 ... The expression x and y first evaluates x; if x is false, its value is
returned; otherwise, y is evaluated and the resulting value is returned."
The only corner that was previously cut is th
Steve Stagg added the comment:
I got my and/or logic inverted, but believe the point still stands
--
___
Python tracker
<https://bugs.python.org/issue42
Steve Stagg added the comment:
Hi Sachit
I see you raised this issue with the numba library here:
https://github.com/numba/numba/issues/6630
I would recommend sticking with the numba issue unless they can confirm there
is an issue with core python
--
nosy: +stestagg
Steve Stagg added the comment:
I re-read the change that introduced this, and the situation is slightly more
complex.
While the wording is understandably slightly ambiguous, the change talks about
the following example:
if a:
pass
else:
In this scenario, the compiler is trying to
Steve Stagg added the comment:
Oops, sorry, didn't realise there were such rules.
The reasoning for me making the change to the title is that that the original
PR didn't mention skipping actual condition logic, but does mention skipping
unreachable blocks, with the example
Steve Stagg added the comment:
Sounds great to me (with my approximately zero optimizer experience)
At risk of taking this too far, you /could/ add something like:
"skip any boolean test of a value _immediately_ following another boolean test,
when it has no ..."
to this spe
Steve Arnold added the comment:
I can't seem to find a usable answer for a user on Sierra with a (supposedly)
working python 3.6 install. From what I can tell all the related bugs are
closed except this one, and this one doesn't include python 3.6. Running the
install_certificat
Change by Steve Dower :
--
keywords: +patch
pull_requests: +23122
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/23142
___
Python tracker
<https://bugs.python.org/issu
Steve Dower added the comment:
I agree with Eryk (unsurprisingly, we discussed this change *a lot* back when
it was made ~3 years ago).
os.readlink is the lowest-level API that gives a reliable result.
os.path.realpath is the high-level API that probably does what most users want
most of
Steve Dower added the comment:
I'm fine with either approach, though adding the READ_RESTRICTED flag would
also be fine.
The audit trailing leading to a bypass is very important, and traversing frames
to find functions in their locals or closures is very useful.
This is nothing l
Steve Dower added the comment:
> I think it could make sense to:
> 1. Alias READ_RESTRICTED to a new READ_AUDIT flag and use the latter instead,
> as it is more clear.
> 2. Update the newtype docs to mention READ_AUDIT and remove documentation for
> the the unused RESTRI
Steve Dower added the comment:
> I wonder whether it would be worth having a section in the docs somewhere
> explaining how to do this, or more generally what the "best practices" are
> for embedding?
Yes, it would be great. I think there are a few pieces in Doc/using/w
Change by Steve Dower :
--
pull_requests: +23178
pull_request: https://github.com/python/cpython/pull/24355
___
Python tracker
<https://bugs.python.org/issue41
Steve Dower added the comment:
That PR is just to add the import warning and update docs. I want to make sure
that's in asap so we don't miss the release.
Is there anywhere else in the docs that needs a note? Distutils has been marked
as deprecated for years already, so it
Steve Dower added the comment:
This is better reported at https://github.com/pypa/pip, as it will be fixed out
of their repository and then updated into here.
Seems like the failed install did not roll back properly. Those directories are
the backup of the uninstallation so that if it fails
Steve Dower added the comment:
New changeset 62949f697fdefbf0c8bbba7a8354b9376afa35ba by Steve Dower in branch
'master':
bpo-41282: Add deprecation warning and docs for distutils (PEP 632) (GH-24355)
https://github.com/python/cpython/commit/62949f697fdefbf0c8bbba7a8354b9
Steve Dower added the comment:
requests is a third-party library that has no obligation to use urllib's
functionality.
If you can show the same behaviour with urllib alone, we can treat it as an
issue here. Otherwise, you'll need to report it t
Steve Dower added the comment:
On Windows it should only affect non-exported functions. Comparing "dumpbin
/exports" output will tell you whether anything has changed there.
The bigger concern is if it merges identical functions that are compared by
function pointer. I know we
Steve Dower added the comment:
I closed the PR. Jason's fix deals with it, so this is now resolved.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Steve Dower added the comment:
Do you know whether aiohttp has released updated packages for the later alphas
yet? Or have you rebuilt it from source as well?
Alphas are not backwards compatible with each other, so extension modules need
to be rebuilt for each update (and I'm pretty
Steve Dower added the comment:
Christian covered it sufficiently: there are no new releases for Python 3.6,
and the installer bundle is what it is.
The last build released from python.org was 3.6.8:
https://www.python.org/downloads/release/python-368/
If you need a newer build, you'll
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
New submission from Steve Dower :
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
Steve Dower added the comment:
Distutils is now deprecated (see PEP 632) and all tagged issues are being
closed. From now until removal, only release blocking issues will be considered
for distutils.
If this issue does not relate to distutils, please remove the component and
reopen it. If
1801 - 1900 of 6138 matches
Mail list logo