On 3/20/07, Collin Winter <[EMAIL PROTECTED]> wrote: > I just discovered that the p3yk/ branch can't do a docs build because > almost none of the code in Doc/tools/ is valid Python 3 [1]. How hard > would it be to set up something akin to http://docs.python.org/dev/ > for p3yk (ie, regular, automated builds), if only to catch problems > like this sooner?
This also begs the question of whether there is anything in our docs toolchain we want to change? I have always found it annoying that I have never been able to get the docs to build for myself on my machine. Raymond's texcheck helps a lot to help prevent errors, but it is unfortunate to not be able to build changed docs to catch errors in the LaTeX. -Brett _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
