Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Improve, normalise mathjax handling, yapf the file #609
For the future, I'd suggest keeping functional changes separate from code formatting, because it's harder to review changes to the code if they're mixed with changes to the style. As this is already here, though, go for it.
(We've also mostly discouraged large formatting changes, because the changes make things like git blame less useful. But as you're doing most of the work on nbconvert at the moment, I think you get to decide things like that)