Skip to content
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

also remove latex_envs nbconvert_support things #802

Merged
merged 3 commits into from
Nov 27, 2016

Conversation

jcb91
Copy link
Member

@jcb91 jcb91 commented Nov 27, 2016

@jfbercher any thoughts on whether we ought to import relevant classes into nbconvvert_support from latex_envs, as I've done so far? It seems neat for back-compatibility, but will probably get to be a pain keeping them in sync eventually, so I think maybe it's be better to just remove them altogether, and let people use latex_envs's classes directly when they want to...

@@ -48,8 +48,6 @@ http://nbconvert.readthedocs.io/en/latest/api/exporters.html

.. autoclass:: LenvsHTMLExporter
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that LenvsHTMLExporter can be removed too (exporter from latex_envs to HTML)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, true, but this has actually already been removed in #794, so doesn't need doing again here

@@ -2,7 +2,8 @@

import os

from .latex_envs import LenvsHTMLExporter, LenvsLatexExporter
from latex_envs.latex_envs import LenvsHTMLExporter, LenvsLatexExporter
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure that we have to keep these two imports since the entry points are defined in the latex_envs.py module.

Copy link
Member Author

@jcb91 jcb91 Nov 27, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep, ok, I'll update shortly

 - templates
 - fix conda env import tests
@jfbercher
Copy link
Member

@jcb91 yes, I agree that it would be be better and simpler to let people use latex_envs's classes directly. I will update the documentation to reflect that.

@jcb91 jcb91 merged commit ea0eb67 into ipython-contrib:master Nov 27, 2016
@jcb91 jcb91 deleted the latex_envs branch November 28, 2016 01:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants