Christoph Haas schrieb: > Dear list... > > I'm on a documentation frenzy now in my current Pylons project. And I'm > using Sphinx for that purpose. All my controllers and helper functions are > documented automatically. Great. Unfortunately Sphinx fails to create > module documentation for my models. I'm staying close to the "Using > SQLAlchemy with Pylons" [0] way as documented on the Pylons wiki. This is > the output on my console:
[...] > Does anyone have an idea what's going wrong? And whether it needs to fixed > in Sphinx, SQLAlchemy (I'm on 0.4.6) or my code? Mike Orr assumed that it > could be that Sphinx loads the module twice to tear out docstrings. I agree that Sphinx is likely importing the module twice. Since it's using Python's standard import mechanism, this shouldn't happen. Problems can arise, however, if the module is imported under different names, e.g. once as "myapp.application" and once as "application". You can try to start sphinx with "python -v /path/to/sphinx-build.py" to see which imports are done. Georg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
