Add a switch for processing function names #35
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #31 .
A few descriptions of this change:
self.raw_func_name
. If it'sFalse
, treat all underlines in function name as label of subscript (outputf_n
as fn); otherwise treat underline as part of function name (outputf_n
as f_n).defined in
LatexifyVisitor.__init__()
, default isFalse
to keep consistency with default behaviors in previous editions.with_latex
,get_latex
, etc. to(*args,**kwargs)
for future use (and they are already used this time). Might be more and more parameters for decorators, I think collect and process them all atLatexifyVisitor.__init__()
is a kind of makeshift...