way too much of hardcoded functionality (git, "src/source", etc).
Yeah, it would be cool to have such mechanism for literal include, but
I'd rather prefer to have some extension based logic, e.g.:
.. literalinclude:: "example.py"
:resource-type: svn
:resource-location: http://svnserver.org/svnpath,revision=128
default resource access could be current file-based, but through some
extension mechanism users could add their own resource types, like your
suggested Git one or my SVN one. This could very well extend into
http-get and similar stuff.
It would be useful to have a commit option to literalinclude to
specify a specific commit.
Here is a first shot at it.
https://bitbucket.org/agiliq/sphinx/changeset/dfe7328eda2f
--
Viktoras
www.neglostyti.com
--
You received this message because you are subscribed to the Google Groups
"sphinx-dev" group.
To post to this group, send email to sphinx-...@googlegroups.com.
To unsubscribe from this group, send email to
sphinx-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sphinx-dev?hl=en.
