Irmen de Jong wrote:
> I wanted to create a doc patch belonging to my patch #1062060,
> but got this error when trying to build the documentation from CVS:
> [snip]
> I dont really understand that latex stuff (used to, but that
> was a long time ago). What's the problem?
>
Looks like the end tag of
Irmen de Jong wrote:
Looks like the end tag of {description} has disappeared with this
check-in:
[...]
Out of curiousity, how did you find this?
Well, I periodically download daily snapshots, so I compiled TeX
files with them. The snapshot from Dec-11 was OK, but with the one
from Dec-17 I couldn'
[EMAIL PROTECTED] wrote:
> Update of /cvsroot/python/python/dist/src/Doc/ext
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17396
> Index: windows.tex
> ===
> RCS file: /cvsroot/python/python/dist/src/Doc/ext/windows.tex,v
> r
Python 2.5 ships with uuid.py and now I want to ask you
about its backward compatibility.
uuid.py says in its docstring:
This module works with Python 2.3 or higher.
And my question is:
Do we plan to make it 2.3 compatible in future releases?
If so, uuid needs to be listed in PEP 291.
Other
All your replies clarifies what your comment was intended to
mean, especially this one:
> I'd just like people who get their hands on the
> module to know that they can use it with 2.3.
When I first read the comment, I interpretted it too broadly
and took it as a requirement for compatibility. Bu
[EMAIL PROTECTED] wrote:
> Update of /cvsroot/python/python/dist/src/Doc/whatsnew
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29055
>
> Modified Files:
> whatsnew25.tex
> Log Message:
> Write section on PEP 342
>
> Index: whatsnew25.tex
> ===
