-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
Upgrade to pynac-0.6.8 #21034
Comments
Branch: u/rws/upgrade_to_pynac_0_6_8 |
This comment has been minimized.
This comment has been minimized.
Author: Ralf Stephan |
Commit: |
comment:3
Started from a clean copy of 7.3.beta8
Ran |
Reviewer: Paul Masson |
This comment has been minimized.
This comment has been minimized.
comment:6
Any update on the 7.3.beta5 error message? Something on my end or yours? |
comment:7
Replying to @paulmasson:
How did you "pull in" the changes? BTW, if you do You should also download the pynac tarball and copy it into |
comment:8
Originally did
Can't review until it builds completely. |
comment:9
In comment:5 you write about starting from beta8 but the output shows beta5. Can you please confirm that beta8 develop compiles cleanly? I'm asking because on the sage-devel there are several reports about problems of beta8 on MacOS. |
comment:10
7.3.beta8 develop compiles cleanly on Mac OS X El Capitan |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
beta9 is now merged into the branch and has all recent MacOS fixes. Please either do |
comment:13
Sorry Ralf, but still getting the error. Curiously even though it references "sagelib-7.3.beta5.log" this file hasn't been modified building either beta8 or beta9. Before you ask, 7.3.beta9 develop also compiles cleanly on Mac OS X El Capitan. Looking back to the pynac 0.6.7 upgrade, there is a comment from Travis that looks relevant. This prompted me to see which beta included 0.6.7 and sure enough it was beta5. I'll be the first to admit knowing nothing about building tarballs, but are you sure there isn't a problem there? The tarball for 0.6.8 isn't downloading automatically to the |
comment:14
Paul, Sage cannot download pynac-0.6.8 because this is only possible after this ticket is merged. As a reviewer you need to download manually and copy it into upstream. Note however that the tarball might be deleted again by Sage at some time. So always make sure it's there before compiling this branch. |
comment:15
This time I downloaded the tarball to |
comment:16
In an effort to move this forward, I did |
comment:17
Not a Mac problem after all. I accidentally merged #21006 some time ago which left behind an empty package folder named "prompt_toolkit". Any package following it alphabetically was ignored, including pynac. |
comment:18
Finally built this ticket! Some preliminary questions:
Will do more testing tomorrow. Thanks for putting up with my build issue. |
comment:19
|
This comment has been minimized.
This comment has been minimized.
comment:20
Doctests pass. Documentation builds. Outstanding issues will be addressed on indicated tickets. Good to go. |
comment:21
Typo in ticket description referencing wrong ticket. Positive review stands. |
This comment has been minimized.
This comment has been minimized.
comment:22
Thanks for the review. |
Changed branch from u/rws/upgrade_to_pynac_0_6_8 to |
The new Pynac version does:
_print_latex_()
inGinacFunction
s (Support GinacFunction._print_latex_() customization #20888)ex.coefficients()
ex.combine()
https://github.com/pynac/pynac/releases/download/pynac-0.6.8/pynac-0.6.8.tar.bz2
CC: @paulmasson
Component: packages: standard
Author: Ralf Stephan
Branch/Commit:
0eb21db
Reviewer: Paul Masson
Issue created by migration from https://trac.sagemath.org/ticket/21034
The text was updated successfully, but these errors were encountered: