Hello everybody,
I have finished my work on implementing a new 'field-list-table'
directive for the Docutils. The (great!) idea is from 2005. But it
never had been implemented - until now.
Please see the code, documentation, demo, ...:
[Guenter Milde] wrote schrieb:
As the Sphinx config file is Python code, you could try to replicate the
steps otherwise done in a Docutils front-end, i.e. register the directive
with Docutils. I.e. in config.py::
That's a good idea. I didn't think of that. Thanks!
Martin
--
http://mbless.de
Hello everybody,
maybe there is an obvious solution - but I just don't see it.
At the end of 'conf.py' I want to read and parse an additional
'Settings.yml' configuration file and add those settings to what we
already have in 'conf.py'. If present settings from the YAML file
should take
Hello Takayuki,
for k in more:
exec(%s = %r % (k, more[k]))
I see, this works.
index.rst::
Welcome to conf.py test
=
:release: |release|
:version: |version|
That looked very promising at first sight - I was very excited. But
it's restricted to
Hi Sebastian,
Quick and dirty: globals().update(read_my_dict_from_yaml())
Well, looks like it's even the right and clean solution in my case!
Alternativel you can update the settings after Sphinx has parsed conf.py:
def setup(app):
for key, value in read_my_dict_from_yaml():
We have setup an intersphinx_mapping and referencing works great like in
:ref:`api:Introduction`. Thanks a lot.
Q:
Is it possible to just link to another documentation project without
naming a special target? Something like :ref:`api:`?
This would be comparable to the standard Sphinx way to
Hi everybody,
anyone?
We have setup an intersphinx_mapping and referencing works great like in
:ref:`api:Introduction`. Thanks a lot.
Q:
Is it possible to just link to another documentation project without
naming a special target? Something like :ref:`api:`?
This would be comparable to the
