Remove Nbconvert template loading magic

[takluyver]

This specifies the template names in the exporter class, rather than getting them from the module names, which seemed a bit too magical. This continues #4724, which I made from my master branch by accident. The problems @damianavila noted there are fixed.

Also, the latex templates got renamed from latex/latex_foo.tplx to latex/foo.tplx.

At present, when specifying a template to use, you have to specify the full template name, e.g. html_basic, not just basic. We may want to think more about this.

[damianavila]

LGTM now... thanks!

At present, when specifying a template to use, you have to specify the full template name, e.g. html_basic, not just basic. We may want to think more about this.

Regarding this one... I don't have strong feelings about this issue but I think I am +0 for the full name: for people using the command line UI, I think that a more explicit name as html_basic or html_full is more informative about what they are asking for...

[minrk]

I think it's a little unfortunate to add back the redundancy of --to html --template html_basic, but the explicitness of the code is definitely an improvement. @ellisonbg @Carreau?

[Carreau]

I think it is ok to make the command line tool a little more complicated,
for 1.0 nbconvert was ment to be a technical preview, I'm not sure it will
be stable for 2.0. As long as the library improve then it is easier to
build command line wrapper around it. Also I was never a big fan of --to
[format] anyway. I'm also considering moving more toward dotted object name
in the long run so that peoples could install full blow templates with pip
and refer to them by Package.templatename.

On Fri, Dec 27, 2013 at 8:42 PM, Min RK notifications@github.com wrote:

I think it's a little unfortunate to add back the redundancy of --to html
--template html_basic, but the explicitness of the code is definitely an
improvement. @ellisonbg https://github.com/ellisonbg @Carreauhttps://github.com/Carreau
?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/4727#issuecomment-31276886
.

[damianavila]

I'm also considering moving more toward dotted object name
in the long run so that peoples could install full blow templates with pip
and refer to them by Package.templatename.

This is a very interesting idea...

[takluyver]

Discussed this with Min, and we've put the HTML templates in a separate directory, like the latex templates already were. We can follow suit with any exporter that has more than one possible template. The exporter defines a default_template_directory, so you can once again do --to html --template basic.

We discussed making default_template_directory a list, so it can look for templates in multiple places (e.g. if there were multiple slides templates, but they inherit from the HTML templates, you'd want both directories listed). But we decided to leave that for another day.

[minrk]

same treatment for template_skeleton_path as default_template_path, probably

[takluyver]

@minrk done & done.

[takluyver]

Weird, it works for me when I run setup.py install locally. Anyway, I tweaked it to *.*.

[takluyver]

And Travis is happy now.

[minrk]

hooray!