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
py3 : bad imports and QQ(string) #24034
Comments
Branch: u/chapoton/24034 |
Commit: |
New commits:
|
comment:2
What's wrong with |
comment:4
well, this screams (in the experimental python3 build that nobody seems to care about) that bytes is expected and str is given. I am just trying to move forward to more serious issues. Maybe the call QQ('string') will need to be fixed, but not now and here. |
comment:5
Replying to @fchapoton:
Then just fix it in your experimental branch instead of an official Sage Trac ticket. |
comment:6
This I did for sure. But the change is so small that I assumed it would meet no objection. |
comment:8
In
to
|
comment:9
Why don't other instances of |
comment:10
I don't mind the QQ changes on this ticket, since it is not changing any doctests and not changing any functionality of Sage, just changing how a few rational numbers are initialized in the Sage code. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
Thanks. This ticket is part of the effort to make sage start when built with python3. It turns out that one of these QQ(string) was sitting on the road. It does not pretend to fix anything else. Ready to go, if patchbots say green ? |
Reviewer: Jeroen Demeyer, John Palmieri |
Changed branch from u/chapoton/24034 to |
as another step
CC: @tscrim @jhpalmieri @a-andre @kiwifb
Component: python3
Author: Frédéric Chapoton
Branch/Commit:
d75000d
Reviewer: Jeroen Demeyer, John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/24034
The text was updated successfully, but these errors were encountered: