-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
Hold context #10035
Comments
comment:1
Can you give a code sample of what you mean? |
comment:2
Replying to @jasongrout:
No, because this is really a followup to another ticket. I'll cc: Burcin in, though he probably already gets it given the component. I imagine something like
as opposed to evaluating it. |
comment:3
I was thinking of something like:
|
comment:4
That would be awesome! |
comment:5
Replying to @jasongrout:
But with such a construction it is not obvious how to simplify 't' without going through Maxima as suggested in #10034
|
comment:6
#11776 seems to be asking for something very similar. |
comment:10
An interesting use case for this showed up at this tex.SX question. |
comment:13
Replying to @jpflori:
You are going through Maxima because the |
comment:14
See pynac/pynac#76 |
comment:16
The construction would look like:
|
comment:17
So we can actually use a global state (e.g. a boolean hold state inside Pynac) and via the Python |
Branch: u/rws/create_hold_context |
Commit: |
Dependencies: pynac-0.7.11 |
Author: Ralf Stephan |
New commits:
|
comment:20
Ordinarily I'd just say well done and leave it at that. But what to do with the "old" hold stuff? Keep, deprecate, side-by-side - should we transform old examples into this one, not, leave that to another ticket that may or may not get attention ... I assume you have thoughts on this so this is just for the purposes of hearing them, I don't have a strong opinion other than that a decision would have to be made, this patch alone wouldn't suffice. THANK YOU for this. |
comment:21
I think the best strategy is to keep the old functionality but replace doctests in tutorials and introductory docstrings (another ticket). As there will be more such contexts a syntax for multiple settings like Please review this whenever pynac-0.7.11 is merged. |
comment:22
Or even |
comment:23
Note however that the Python directive
Maybe we should provide
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed dependencies from pynac-0.7.11 to #23820 |
This comment has been minimized.
This comment has been minimized.
Reviewer: Emmanuel Charpentier |
comment:28
Thanks. |
Changed branch from u/rws/create_hold_context to |
Now that Pynac will support 'hold' of symbolic expressions, like
we might want a 'context' for this.
The ticket enables the following:
Depends on #23820
CC: @burcin @eviatarbach
Component: symbolics
Author: Ralf Stephan
Branch/Commit:
3ad332c
Reviewer: Emmanuel Charpentier
Issue created by migration from https://trac.sagemath.org/ticket/10035
The text was updated successfully, but these errors were encountered: