-
-
Notifications
You must be signed in to change notification settings - Fork 491
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 lrcalc to 2.1 #31355
Comments
This comment has been minimized.
This comment has been minimized.
Branch: u/tmonteil/upgrade_lrcalc_to_2_0 |
Commit: |
comment:4
I get the following error when doctesting:
New commits:
|
comment:5
This has major API changes. Large parts of lrcalc.pyx needs to be rewritten because the used functions have been removed or modified. |
comment:6
I see, any help welcome ! |
comment:8
The existing spkg-configure.m4 needs to be updated to detect v2.0 (once it actually works), too. |
comment:9
Some information from Anders:
For reference, some pointers:
|
comment:10
The Python bindings are only in the repository and a bit raw, so probably only useful as examples. But I expect they are easier to start from than the .h files. |
Changed branch from u/tmonteil/upgrade_lrcalc_to_2_0 to u/arojas/upgrade_lrcalc_to_2_0 |
comment:12
Replying to @asbuch:
Actually, they are almost equivalent to the current bindings in Sage. The attached branch replaces lrcalc.pyx with a thin wrapper over lrcalc's bindings. It mostly just translates the output from lrcalc to sage notation. The only function of lrcalc.pyx that isn't straghtforward to port is quantum multiplication: I found no way to recover the q-grading from lrcalc's output, so this is reimplemented in the patch. The branch needs an update of lrcalc to include python bindings. New commits:
|
comment:13
Replying to @asbuch:
Since you are here and I can not find a bug tracker for lrcalc: the setup.py is missing metadata, so the egg for lrcalc gets installed as UNKNOWN-0.0.0.0 |
comment:15
If my bindings are used, then that will make it easier to keep things compatible if I make more changes to the C interface. I should be able to keep the Python interface stable, at least up to reordering of output. Quantum function: I will add a function mult_quantum_pairs that returns a dict from ((partition),d) to integers, you can switch to that if you want. setup.py: Does the following include the tags you are looking for? Suggestions welcome!
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:17
Replying to @asbuch:
That works, thanks. Also, although maybe it is a little bit too late for that, it would be good to bump the soversion of the C shared library since the API changed. |
comment:18
Replying to @antonio-rojas:
I changed the version to "2.0.0" and thought that was in line with this page. Please let me know if I am doing something wrong. |
comment:19
Replying to @asbuch:
You need to change the -version-info in https://bitbucket.org/asbuch/lrcalc/src/master/src/Makefile.am#lines-23 |
comment:20
Replying to @antonio-rojas:
I see, thanks! According to conventions, is that line in Makefile.am independent from this line in configure.am:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:95
Ping. Anything else needed here? |
comment:96
What is the minimum lrcalc version required by lrcalc_python? |
comment:97
lrcalc and lrcalc_python come from the same repo, so I suppose the versions need to match. |
comment:98
A number of distrbutions have system-wide lrcalc installations, some still version 1.*, and those can be picked up by Sage. If these are not compatible they should not be used. |
comment:99
1.* will not be picked up, the |
comment:100
I just have been quite busy. And since @orlitzky has migrated a lot of packages to the main tree, I feel less personal pressure to update. We have 2.0 in the main tree but not 2.1 yet. I will have to see what needs to be done. |
comment:101
|
comment:103
Replying to @dimpase:
Actually Fixed the license too, should be ready to go now. |
comment:104
I have opened a PR for getting 2.1 in Gentoo and I have an ebuild ready for the python bindings for the sage-on-gentoo overlay just waiting for the PR inclusion before going live [because of dependencies requirements, cannot go in until lrcalc-2.1 is present]. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:108
Ping, hope to get this in 9.6 |
Changed branch from u/arojas/upgrade_lrcalc_to_2_0 to u/tscrim/upgrade_lrcalc_2_1-31355 |
This comment has been minimized.
This comment has been minimized.
comment:109
Does Sage's auto-download mechanism automatically rename the tarballs to their appropriate values. I am worried that both tarballs (lib and python) are called I made a few other little tweaks and checked the tests. If my changes are good, then it is a positive review. New commits:
|
Changed reviewer from Matthias Koeppe, ... to Matthias Koeppe, Travis Scrimshaw |
comment:110
Replying to @tscrim:
Yes, it is renamed to the value given in the |
comment:111
Thanks |
Changed branch from u/tscrim/upgrade_lrcalc_2_1-31355 to |
lrcalc 2.1 is out https://bitbucket.org/asbuch/lrcalc/src/master/ChangeLog
Instead of rewriting Sage's Python bindings to support the new API, we replace them with a wrapper around the new upstream provided bindings
Upstream:
lrcalclib-2.1.tar.gz (lrcalc): https://sites.math.rutgers.edu/~asbuch/lrcalc/lrcalc-2.1.tar.gz
lrcalc-2.1.tar.gz (lrcalc_python): https://pypi.io/packages/source/l/lrcalc/lrcalc-2.1.tar.gz
CC: @antonio-rojas @anneschilling @fchapoton @tscrim @thierry-FreeBSD @orlitzky @mkoeppe @kiwifb @asbuch @slel
Component: packages: optional
Keywords: upgrade, lrcalc
Author: Antonio Rojas, Matthias Koeppe
Branch/Commit:
de4fe09
Reviewer: Matthias Koeppe, Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/31355
The text was updated successfully, but these errors were encountered: