-
-
Notifications
You must be signed in to change notification settings - Fork 565
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
Improved Kash interface #25488
Comments
comment:1
In the course of preparing this ticket, I realized that the default Why? Since the default implementation of
Maybe we should open another ticket for that. For Kash, where we have separate boolean and integer types, we need to compare to both New commits:
|
Commit: |
Author: Brent Baccala |
Branch: public/25488 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:4
We are in fact thinking about removing support for |
comment:5
Replying to @dimpase:
Removing The problem is that it's the only thing we've got right now to compute bases for Riemann-Roch spaces over Kwankyu Lee has written some new function field code that can handle Riemann-Roch calculations over finite fields, but even that code is taking forever to move into the released code base. Somebody (maybe me) needs to expand the function field code to handle Although, I admit that next to nobody knows how to use |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
this is missing the optional kash tag:
|
This comment has been minimized.
This comment has been minimized.
comment:11
Moving tickets from the Sage 8.8 milestone that have been actively worked on in the last six months to the next release milestone (optimistically). |
comment:12
Ticket retargeted after milestone closed |
comment:13
Batch modifying tickets that will likely not be ready for 9.1, based on a review of the ticket title, branch/review status, and last modification date. |
comment:14
The patchbot complains about some docstring issues |
comment:16
patchbot is now green |
Reviewer: Dima Pasechnik |
Changed branch from public/25488 to |
The current interface to the optional
kash
package has limited utility. No way is provided to convert Kash expressions to Sage expressions, and Kash names likesage1
might be re-used even if there are outstanding references to subexpressions likesage1.1
(so this is also a bug fix, in addition to an enhancement).This ticket fixes several bugs in the Kash interface, and allows a translation dictionary to be passed to a Kash object's
sage()
method, mapping Kash objects to Sage objects, allowing conversions like this:Also, keyword arguments are now passed correctly to Kash functions.
Component: interfaces: optional
Keywords: kash
Author: Brent Baccala
Branch/Commit:
c8f01e7
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/25488
The text was updated successfully, but these errors were encountered: