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
feat: add custom cell magic parser #213
Commits on Aug 28, 2020
Commits on Sep 2, 2020
-
Generalize valid option values
The parser should accept as wide a range of values as possible and let the code that delas with the semantics to decide whether the values are good or not.
-
Fix recognizing --params option in state 3
The --params option spec must be followed by a non-alphanumeric character, otherwise it's a different option spec (e.g. --paramsX).
-
-
Commits on Sep 3, 2020
Commits on Sep 4, 2020
-
Preserve the cell magic context's import path
The context still needs to be importable from the old path
-
Commits on Sep 9, 2020
-
-
-
Simplify string literal in a single line
Apparently black just places all implicitly concatenated string literals in a single line when short enough without replacing them with a single string literal.
-
-
-
Pass pos as a positional arg to finditer()
This is necessary to retain Python 2 compatibility.
-
Resolve coverage complaint about a code path
The tokens are designed in a way that the scanner *always* returns some match, even if just UNKNOWN or EOL. The "no matches" code path can thus never be taken, but the coverage check can't know that.