Julien Puydt: > Hi, > > I just pushed to fplll's Debian git repository a tentative 5.1.0-3 which > would fix the recently reported issue with fpylll : I rewrote the patch > for the default strategies path changes. > > I'm a bit at loss on how to check if that really fixes anything : I > tried to build fpylll (success), but then trying to "import fpylll" in > python gave: > RuntimeError: You must get the file local/bin/sage-maxima.lisp > > so I can't really test seriously... >
I can reproduce this, it works if you uninstall sage (but of course we have to fix it properly). The underlying issue is caused by the fact that Sage sets things like SAGE_LOCAL outside of python itself, so that one gets e.g.: $ python -c 'from sage.env import DOT_SAGE, SAGE_SCRIPTS_DIR; print(SAGE_SCRIPTS_DIR)' $SAGE_LOCAL/bin $ sage -c 'from sage.env import DOT_SAGE, SAGE_SCRIPTS_DIR; print(SAGE_SCRIPTS_DIR)' /usr/share/sagemath/bin I would guess that this also affects upstream Sage, but perhaps the issue is hidden somehow (Debian uses a different "sage-env" shell script). X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
