You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following code, entered in the command-line interface to Sage, shows the effect:
sage: def foo(x):
....: '''
....: Eh?
Object `Eh` not found.
....: '''
....: return x
....:
The parser appears to act on the '?' right away, rather than wait for the end of the thing being defined (or realizing that '?' in this case is not to be acted on).
The effect shows up with both single- and double- quotes, and with and without the "raw" qualifier (r!''').
The following code, entered in the command-line interface to Sage, shows the effect:
The parser appears to act on the '?' right away, rather than wait for the end of the thing being defined (or realizing that '?' in this case is not to be acted on).
The effect shows up with both single- and double- quotes, and with and without the "raw" qualifier (r!''').
This may be related to Trac#4405.
Depends on #12719
Component: user interface
Reviewer: Keshav Kini
Issue created by migration from https://trac.sagemath.org/ticket/4413
The text was updated successfully, but these errors were encountered: