Open b0bf1a7b-bfe9-44fe-8236-57b33990cc18 opened 6 years ago
Before I create a branch, I'd like to get feedback on the following:
Does the name %%noparse work, or should I change it to something else?
I was thinking of adding the magic to the end of the class SageMagics in sage/repl/ipython_extension.py . Any objections?
Anything else for a first-time contributor to keep in mind?
I decided to use the name %%nopreparse
instead.
New commits:
773be9e | Add %%nopreparse cell magic |
Branch: u/gh-bryangingechen/nopreparse
Commit: 773be9e
Branch pushed to git repo; I updated commit sha1. New commits:
3f959f4 | Rename to no_preparse |
Branch pushed to git repo; I updated commit sha1. New commits:
b231bca | remove trailing whitespace |
no_preparse seems to be more in line with the accepted Python code style.
Changed author from gh-bryangingechen to Bryan Gin-ge Chen
patchbot failures seem unrelated
Changed keywords from none to ipython magic
I'm opening this ticket because of nbruin's suggestion for my answer https://ask.sagemath.org/question/9277/preparser-state-for-regexs/?answer=42530#post-id-42530
There I shared code for an IPython extension which registers a cell magic which disables the Sage preparser (by toggling the state of the global variable sage.repl.interpreter._do_preparse before and after running the cell).
CC: @nbruin
Component: user interface
Keywords: ipython magic
Author: Bryan Gin-ge Chen
Branch/Commit: u/gh-bryangingechen/nopreparse @
b231bca
Issue created by migration from https://trac.sagemath.org/ticket/25522