Yusuke Oda

OK I will do soon.

I also think that... this change should be included to the "next release," but Travatar has no release tags currently. This change breaks backward compatibility, so we should handle that...

LGTM too.

FWIW, I ran into a similar problem when I tried to bundle `mysqlclient`, which requires several system libraries at installation. Since we needed that package only in the final Docker...

Some features are taken over by other issues. Closes this issue for now.

@chunibyo-wly Thanks! I think we don't need bitset here and it is enough to store individual members for all boolean configs. We basically don't need to care about the efficiency...

I think we can simply define the config class as a dataclass with only nullable members, with the `merge` method that generates a new Config while maintaining the original config...

I think non-elementary functions (`erf`, `erfc`, `gamma`, `lgamma`) should be avoided from this option. Other candidates look fine to me.

I also think our current implementation (#125) naturally solves https://github.com/google/latexify_py/issues/65#issuecomment-1290288048 , as users can choose whether `exp` is expanded or not.

This is generally supported in the current implementation. We'd support individual functions in separate issues (if needed).