we have our own Makefile in sqlalchemy/doc/build/texinputs which adds the option "-interaction=nonstopmode" to LATEXOPTS:
# Additional LaTeX options LATEXOPTS = -interaction=nonstopmode if I run without this flag, then pdflatex constantly stops to ask for input about things. I'm not sure if readthedocs is using our Makefile or not, though it seems like they are. For some reason, RTD stops on the first pdflatex run and does not continue. When I run locally, it runs both for me as well. I'm not sure what RTD does here, it seems they'd be using our file, or running pdflatex with some other options, not sure. On Feb 17, 2013, at 8:39 PM, Vraj Mohan <r.vrajmo...@gmail.com> wrote: > The TOC is generated correctly for me in 1 pass with invocation of "make > latexpdf" (I verified with "make clean latexpdf"). I've attached my make log. > Google groups is not allowing me to attach the generated PDF file or my make > output. Please let me know how we can proceed to debug this issue. > > --Vraj Mohan > > On Friday, February 15, 2013 11:57:36 PM UTC-5, Michael Bayer wrote: > OK, I've committed this and yes that was a whole new error I wasn't familiar > with, which appears to be why RTD wasn't building at all. Now it's back to > building as you can see via the link here: > http://docs.sqlalchemy.org/en/latest/. > > The PDF though doesn't have the table of contents at the moment, which is due > to the "needs to be built twice" issue. this is still broken because our PDF > build spits out warnings and errors that prevents RTD from running the build > multiple times like it's supposed to. Usually on the next build, the TOC > magically appears, though its been awhile and maybe things aren't working > even that well now. As you can see in their log, they still see the PDF > build as "failing": https://readthedocs.org/builds/sqlalchemy/446592/ even > though it put a file there. Not sure how "failure" and "we copied the .pdf > file successfully" go together, this is what I'd like RTD to improve upon a > bit more. > > Anyway thanks for the patch things are in better shape than they were before > ! > > > > > On Feb 14, 2013, at 11:28 AM, Vraj Mohan <r.vra...@gmail.com> wrote: > > > The attached patch fixes it. The problem is in the dialect_info > > extension. The issue is that sphinx.builders.Builder.get_relative_uri > > may raise NoUri. > > > > Disclaimer: I still do not understand sphinx well enough to know why this > > is so, > > I hope this helps. > > > > --Vraj Mohan > > > > On Wed, Jan 30, 2013 at 9:41 AM, Michael Bayer <mik...@zzzcomputing.com> > > wrote: > >> the PDFS have generated very poorly for quite some time and readthedocs > >> environment is not able to adapt to the many warnings it generates for > >> SQLAlchemy's documentation. I've was n the Sphinx list a few years ago > >> at > >> this point asking for solutions regarding some of these warnings and was > >> not > >> able to get help on them - some of the constructs that Sphinx allows (and > >> which we really need, namely code examples underneath a :param:) aren't > >> compatible with their LaTeX model. I don't have the resources > >> personally > >> to keep banging my head against the immensely antiquated LaTeX tools, not > >> to > >> mention readthedocs not getting around to fixing things either, so I've > >> taken the PDF links off the site. > >> > >> > >> > >> > >> On Jan 30, 2013, at 2:50 AM, Vraj Mohan wrote: > >> > >> Hi, > >> > >> I noticed that documents in PDF for 0.8 and development are not being > >> generated in readthedocs.org. > >> > >> I tried to build these myself with a development snapshot and had the same > >> failures. > >> > >> I then noticed that if a pickled environment was already created, the PDF > >> would be generated fine. In other words, "make pickle", "make html", etc > >> would create a pickled environment which would then cause "make latexpdf" > >> to > >> succeed. > >> > >> I am not an expert on Sphinx - I thought this would be useful information > >> for someone more knowledgeable than me. > >> > >> --Vraj Mohan > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "sqlalchemy" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to sqlalchemy+...@googlegroups.com. > >> To post to this group, send email to sqlal...@googlegroups.com. > >> Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. > >> For more options, visit https://groups.google.com/groups/opt_out. > >> > >> > >> > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "sqlalchemy" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to sqlalchemy+...@googlegroups.com. > >> To post to this group, send email to sqlal...@googlegroups.com. > >> Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. > >> For more options, visit https://groups.google.com/groups/opt_out. > >> > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > > "sqlalchemy" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to sqlalchemy+...@googlegroups.com. > > To post to this group, send email to sqlal...@googlegroups.com. > > Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > <pdf_generation.patch> > > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
