Ah, that was the problem, at least for my current crop of errors - I
was running on 1.0.4, and on 1.0.7 the error messages line numbers
seem to be correct and much more helpful in locating the problem.
Thanks for the fix/improvements - I predict this will save me a fair
amount of time in the future. (thus, sorry for the noise - I guess I
should always be on the latest version before posting this sort of
thing!)

On Jan 24, 11:07 am, Georg Brandl <ge...@python.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am 24.01.2011 20:24, schrieb Erik Tollerud:
>
> > I've been making quite a bit of use of autodoc (specifically,
> > automodule) for documenting a project.  However, as the project has
> > grown, I find it's difficult to tell where warnings are occurring in
> > the source code, because the line numbers the Sphinx warnings output
> > seem to be unrelated to the line numbers in the source documentation.
> > Presumably this is because autodoc produces some kind of internal line-
> > numbering scheme... is there any way to map the autodoc line numbers
> > that the sphinx warnings emit to the actual source code line numbers?
> > Or a way to output intermediate files that match the line numbers that
> > can be cross-matched to the source code?
>
> Hmm, which version of both docutils and Sphinx are you using?  I recently
> fixed a bug in generating line numbers in 1.0.7, and recent docutils
> versions also improved keeping track of not only source files but line 
> numbers.
>
> Basically you should get location info such as "docstring of OBJECT:line in
> that docstring".
>
> Georg
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
>
> iEYEARECAAYFAk09zggACgkQN9GcIYhpnLDAagCfbGmFprd9S9Hsz0i8SsNKtGrW
> m8oAn10xKV3AUtvcw54Vfal3hY7MsrYt
> =973p
> -----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups 
"sphinx-dev" group.
To post to this group, send email to sphinx-dev@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.

Reply via email to