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
Minimize use of is_package_installed at runtime #20377
Comments
comment:2
Your branch points to the latest beta, did you forget to push or something? |
comment:4
I forgot to commit :( |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
You forget a colon
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
If that's all I forgot that's not a bad score. This particular one was different in sage-on-gentoo because I don't ship this database separately from |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:11
It seems we are working on the same issue ;) It seems to me that my approach is slightly more generic but I am open for discussion. |
This comment has been minimized.
This comment has been minimized.
comment:13
Is this still relevant or should it be closed in the light of #20382? |
This is helpful for sage-on-distributions. Typically sage-on-distribution do not want, or need, to call sage's internal packaging system.
I raised this as part of Sage days 77.
Related tickets:
CC: @slel
Component: packages: optional
Keywords: sagedays 77
Author: François Bissey
Branch/Commit: u/fbissey/is_pkg_installed @
aba00ce
Issue created by migration from https://trac.sagemath.org/ticket/20377
The text was updated successfully, but these errors were encountered: