Better / safer parsing of conf.py files about readthedocs.org HOT 5 CLOSED

My first quasi-working solution is here: wapcaplet/readthedocs.org@840ae7a

from readthedocs.org.

Is this issue resolved? It seems to be to me - I've used various bits of python code in conf.py, and don't think I'm whitelisted, and it seems to have worked fine.

from readthedocs.org.

This is not resolved for me. I use autodoc/extlinks in cement.readthedocs.org ... and both are not working right. I also use some magic to auto generate the 'VERSION' and 'RELEASE' in conf.py which appear to not be set in the docs. So for example, the title should be 'Cement v0.8.18 Documentation' and is instead 'Cement v Documentation'. All of the extlinks macros just appear as they do in the source and don't link anywhere like they are suppose to. See:

http://cement.readthedocs.org/en/latest/changes.html

Thanks.

from readthedocs.org.

@wapcaplet: your solution looks good to me, except the solution for the path, which seems a bit too simplistic. Maybe you could add extra treatment for some special variable (e.g. source_path_list) to templates/projects/conf.py.html and add all elements to the sys.path via sys.path.append(os.path.abspath(elem)).

My project is whitelisted now, so I don't really need this any more, but otherwise your solution would have done the job very well (except for the path issue) and is somehow much cleaner. Why don't you add a pull request for this change?

from readthedocs.org.

I'm working on a branch that will remove white listing, closing this in favor of that :)

from readthedocs.org.