-
-
Notifications
You must be signed in to change notification settings - Fork 553
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: failing doctest in graph_database.py with interactive_query #27435
Comments
comment:1
I don't know how to fix it. |
comment:2
Hi, I am Piyush, I am new to sage, I was wondering if I could be of some help here. I am not able to replicate this test. Is there something that I am missing? I am using Ubuntu 16.04
|
comment:3
The problem is with Python 3. We are working hard on the transition from Python 2 to Python 3. |
comment:4
Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually) |
comment:5
I may have managed to fix this error. I don't know anything about the origins of the code but the error arises in in I tried changing the name of the function that gets defined and ran into a different python3-related bug in the I downloaded the source for that package, changed the uses of I'm not sure what to suggest for this ticket, the doctest in question has something to do with the old sage notebook (sagenb). The function If my changes to |
comment:6
Let's ask the author of #22431 if anything was said about Also I don't know if these tools have users. If not, we may simply deprecate the parts involving |
comment:7
Replying to @ed359:
As long as these changes don't break sagenb on python2, it is fine. As to functionality to be removed, I don't know. |
comment:9
Thanks. We may need to think about how to deal with this in the eventual removal of sagenb, as the interact should in principle still be able to work in e.g. Jupyter notebooks, but would have to import from elsewhere. Cc:ing Jeroen as he knows a lot about how that is implemented in Jupyter and where things might need to import from now. New commits:
|
Commit: |
comment:10
Now the error is in sagenb (tested over 8.8.beta6).
|
comment:11
As the Sage-8.8 release milestone is pending, we should delete the sage-8.8 milestone for tickets that are not actively being worked on or that still require significant work to move forward. If you feel that this ticket should be included in the next Sage release at the soonest please set its milestone to the next release milestone (sage-8.9). |
comment:13
If the problem is with sagenb, then can we mark the doctest as "# py2", since my understanding is that sagenb is not compatible with Python 3? That is, keep the proposed changes here, but also tag the doctest as py2 only. |
comment:14
can't we just skip installing sagenb on Python3? |
comment:15
I think that sagenb as a whole does not work with Python 3, but parts of it do, and parts are imported into the Sage library in various places. If we don't install it, some things may break. Some of the imports:
|
comment:16
I agree with the proposal of marking this doctest as |
Author: Ewan Davies, David Coudert |
comment:18
This is fine with me. Anyone else have any comments? Objections to setting to positive review? |
Reviewer: Frédéric Chapoton, John Palmieri |
comment:19
ok.. |
Changed branch from public/graphs/27435_doctest_in_graph_database to |
CC: @dimpase @jdemeyer
Component: graph theory
Author: Ewan Davies, David Coudert
Branch/Commit:
10fd0e8
Reviewer: Frédéric Chapoton, John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/27435
The text was updated successfully, but these errors were encountered: