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
Kenzo interface is broken #27554
Comments
comment:1
It doesn't even install for me:
|
comment:2
seems like the problem is in copying between partitions, and this has already been fixed for Maxima on #8645 |
comment:3
Perhaps Nils knows how to do this properly, as no traces of the fix from #8645 can be found, and the fix itself does not seem to work - perhaps it's outdated. |
comment:4
I think this should fix the doctest, but I don't know about Dima's installation problem. diff --git a/src/sage/interfaces/kenzo.py b/src/sage/interfaces/kenzo.py
index cc24ed3f0c..f0b4a1aafb 100644
--- a/src/sage/interfaces/kenzo.py
+++ b/src/sage/interfaces/kenzo.py
@@ -36,6 +36,7 @@ from sage.structure.sage_object import SageObject
from sage.homology.homology_group import HomologyGroup
from sage.rings.integer_ring import ZZ
from sage.groups.additive_abelian.additive_abelian_group import AdditiveAbelianGroup
+from sage.categories.commutative_additive_groups import CommutativeAdditiveGroups
from sage.libs.ecl import EclObject, ecl_eval, EclListIterator
|
Upstream: Reported upstream. No feedback yet. |
comment:5
The following patch makes it work for me --- a/compile.lisp
+++ b/compile.lisp
@@ -5,6 +5,7 @@
(require :asdf)
+(asdf:disable-output-translations)
(push #P"./" asdf:*central-registry*)
(require :kenzo)
(asdf:make-build :kenzo :type :fasl :monolithic t :move-here #P".") (yes, I RTFM'd for a bit... :-) I've opened miguelmarco/kenzo#1 to put this fix upstream |
comment:6
I did a new upstream release with Dima's patch: |
comment:7
I'm a bit unsure whether, given that Kenzo is now a Sage package, about Kenzo examples in Should there at least be a script (or Lisp code) available there to re-create these files? |
comment:8
Replying to @dimpase:
Our plan with Ana Romero and her student is to keep working on a more complete interface between Kenzo and Sage. The long term idea is to be able to seamlessly translate simplicial sets back and forth. That includes writing some specific Kenzo code to be able to create simplicial sets from the kind of information that Sage uses to define them, and to output the kind of information that Sage would need. Considering that, I would wait until we have that ready to redesign the interface used in those examples. |
comment:10
I added the missing import, and also made a version bump of the kenzo package, to include Dima's patch (tarball is in https://github.com/miguelmarco/kenzo/archive/1.1.7-r2.tar.gz ). Can you please test it? New commits:
|
Commit: |
comment:11
OK, this works. You can create a slimmed down tarball and add to the release. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:13
Replying to @dimpase:
Done! The tarball is at https://github.com/miguelmarco/kenzo/archive/1.1.7-r3.tar.gz |
comment:14
The tarball for Sage need not be the same as what you automatically get from github. On the releases page there is "Edit" button to the right of each release, clicking on it allows you to add more "assets", e.g. a tarball - properly named, so that one can just wget it without a need to rename. |
comment:15
Replying to @dimpase:
I know, but that kind of goes against the idea of version control. I do prefear to have everything fully synced. |
comment:16
Well, in fact sometimes we do have issues with automatically created, by github, tarballs, as they are not stable, they may be affected by changes in the git repo! |
comment:17
I'd rather use something like git submodules/subtrees/subwhatever for source Sage packages, in fact. This is IMHO safer than tarballs, generally speaking. |
comment:18
But the tarballs corresponding to releases shouldn't change at all, right? |
comment:19
Replying to @miguelmarco:
I am trying to say that the automatically generated by github tarballs are not stable, they may change overtime, and should be avoided. On the other hand, if you add to a github release an "asset" tarball, it will stay intact. |
comment:20
just to explain, I did the following, as an example: there you see https://github.com/dimpase/kenzo/releases/download/test/kenzo-test.tar.gz |
comment:21
I see, thanks for the hint. I just added that to the release. The link is now https://github.com/miguelmarco/kenzo/releases/download/1.1.7-r3/kenzo-1.1.7-r3.tar.gz |
comment:22
OK, can you update the branch to reflect this - or do checksum remain the same? |
comment:23
The checksums have not changed |
comment:24
Ok, please provide a link to the tarballs in the ticket description, as we always do for package updates. |
This comment has been minimized.
This comment has been minimized.
Reviewer: Dima Pasechnik |
comment:26
feel free to set it to positive review, and provide author name. |
Author: Miguel Marco |
Changed branch from u/mmarco/kenzo_interface_is_broken to |
Seems like a missing import...
A problem with the instalation using different partitions has been solved upstream. We include a new version of the package here. The new tarball is in https://github.com/miguelmarco/kenzo/releases/download/1.1.7-r3/kenzo-1.1.7-r3.tar.gz
Upstream: Reported upstream. No feedback yet.
CC: @miguelmarco @nbruin
Component: interfaces: optional
Author: Miguel Marco
Branch/Commit:
4cbeb6f
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/27554
The text was updated successfully, but these errors were encountered: