-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix new (lib) gap on py3 #26992
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
reducing the number of words in that string:
still the same
this is different, more sane - this is treated as a single statement, at least.
looks OK. |
comment:3
And with python2 one gets the intended (roughly, what GAP reports):
|
comment:4
The error comes from the new-style-formatted string in
And indeed, this looks very dangerous coding style, as |
comment:5
No, actually, it's merely GAP producing a string that needs extra sanitation (in Python3).
then all the tests on this file pass. So, somehow, Python3 cannot correctly do search/replace/strip here, while Python2 can. |
Branch: u/embray/ticket-26992 |
comment:7
The main issue here (which I've encountered before in other contexts) is that in Python 3 a lot of the interpreter and core types and modules are much stricter about checking whether or not an exception is already pending before trying to go down various code paths (without this you can end up in strange situations where built-in methods get called even after an exception has been raised). In this case, the code in the error handler which manipulates the exception message (using Python) could break if the error handler was entered recursively, so it had to be reorganized slightly to account for this possibility. I also added New commits:
|
Author: Erik Bray |
Commit: |
comment:8
looks good to me - on py3 docbuilding (that was the place I saw this bug 1st) still breaks somewhere later, but this (a problem with |
Reviewer: Dima Pasechnik |
comment:9
Retarging tickets optimistically to the next milestone. If you are responsible for this ticket (either its reporter or owner) and don't believe you are likely to complete this ticket before the next release (8.7) please retarget this ticket's milestone to sage-pending or sage-wishlist. |
comment:10
Merge conflict |
comment:11
A mystery merge conflict. |
comment:12
Well, the pull request here is stalled.. |
Changed branch from u/embray/ticket-26992 to public/ticket/26992 |
comment:13
trivial conflict fixed New commits:
|
comment:14
Follow-up ticket: #27155 |
comment:15
Note that this usage of |
comment:16
I'm getting a quite consistent error (with or without 27155)
|
Changed branch from public/ticket/26992 to |
There are py3-specific bugs in the new lib gap, as of #22626.
Some of them stem from error handler not being fully string/bytes clean.
CC: @fchapoton @embray @jdemeyer
Component: python3
Author: Erik Bray
Branch/Commit:
369fade
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/26992
The text was updated successfully, but these errors were encountered: