I'd suggest your best approach would be to publish it as a standalone
reusable library on something like Github or Bitbucket. This allows
you to publish the source, and allows others to easily use the source
and contribute fixes.
While I have great affection for LaTeX as a language (I wrote both my
theses using LaTeX), I don't think it's appropriate for the core of
Django. Ultimately, Django is a web framework, and HTML/JS are the
focus of web work.
Given that it's easy to distribute a template tag library as a
third-party feature, your library doesn't need to be in the core,
either. By maintaining a set of LaTeX tools as a third-party library,
you are able to:
* keep the development pace independent of Django's release cycle
(particularly important during initial development)
* help distribute the development load outside of the Django core
team (since you aren't dependent on Django's core team to commit
changes)
* help keep the size of Django's core library under control
(end-users are able to choose the extensions and languages they want
to support)
Best of luck with your LaTeX library.
Yours,
Russ Magee %-)