Re: [Python-Dev] [Python-3000] Documentation switch imminent
On 8/15/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Brett Cannon schrieb:
> > On 8/14/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> >> Now that the converted documentation is fairly bug-free, I want to
> >> make the switch.
> >>
> >> I will replace the old Doc/ trees in the trunk and py3k branches
> >> tomorrow, moving over the reST ones found at
> >> svn+ssh://svn.python.org/doctools/Doc-{26,3k}.
> >
> > First, that address is wrong; missing a 'trunk' in there.
>
> Sorry again.
>
Not a problem. I also noticed, though, that the user (pythondev) is
missing as well. =)
> > Second, are we going to keep the docs in a separate tree forever, or
> > is this just for now?
>
> They will be moved (in a few minutes...) to the location where the
> Latex docs are now.
>
Yep, just did an update.
> > I am not thinking so much about the tools, but
> > whether we will need to do two separate commits in order to make code
> > changes *and* change the docs? Or are you going to add an externals
> > dependency in the trees to their respective doc directories?
>
> No separate commits will be needed to commit changes to the docs.
> However, the tool to build the docs will not be in the tree under Doc/,
> but continue to be maintained in the doctools/ toplevel project.
>
OK.
> I spoke with Martin about including them as externals, but we agreed that
> they are not needed and cost too much time on every "svn up". Instead,
> the Doc/ makefile checks out the tools in a separate directory and runs
> them from there. (The Doc/README.txt file explains this in more detail.)
Seems simple enough! Thanks again for doing this, Georg (and the doc SIG)!
-Brett
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Documentation switch imminent
> Okay, I made the switch. I tagged the state of both Python branches
> before the switch as tags/py{26,3k}-before-rstdocs/.
Update instructions:
1. svn diff Doc; any pending changes will need to be redone
2. svn up; this will remove the tex sources, and then likely
fail if there were still other files present in Doc, e.g.
from building the documentation
3. review any files left in Doc
4. rm -rf Doc
5. svn up
If you are certain there is nothing of interest in your sandbox
copy of Doc, you can start with step 4.
Regards,
Martin
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Documentation switch imminent
On 8/15/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Okay, I made the switch. I tagged the state of both Python branches
> > before the switch as tags/py{26,3k}-before-rstdocs/.
>
> Update instructions:
>
> 1. svn diff Doc; any pending changes will need to be redone
> 2. svn up; this will remove the tex sources, and then likely
>fail if there were still other files present in Doc, e.g.
>from building the documentation
> 3. review any files left in Doc
> 4. rm -rf Doc
> 5. svn up
>
> If you are certain there is nothing of interest in your sandbox
> copy of Doc, you can start with step 4.
Why the 'rm' call? When I did ``svn update`` it deleted the files for
me. Is this to ditch some metadata?
-Brett
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Documentation switch imminent
>> 1. svn diff Doc; any pending changes will need to be redone >> 2. svn up; this will remove the tex sources, and then likely >>fail if there were still other files present in Doc, e.g. >>from building the documentation >> 3. review any files left in Doc >> 4. rm -rf Doc >> 5. svn up >> >> If you are certain there is nothing of interest in your sandbox >> copy of Doc, you can start with step 4. > > Why the 'rm' call? When I did ``svn update`` it deleted the files for > me. Is this to ditch some metadata? No, it's to delete any files in this tree not under version control, see step 2. If you had any such files, step 2 would abort with an error message svn: Konnte Verzeichnis »Doc« nicht hinzufügen: ein Objekt mit demselben Namen existiert bereits (or some such) Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Python 3000 Sprint @ Google
I'd really like an excuse to implement server-side SSL support one of these days. Could that be a sprint activity? Probably against 2.6 (I doubt the Modules/_ssl.c file will change much for 3K). The idea is that if you call socket.ssl() on a socket that's bound to an address, the socket is assumed to be server-side, the cert passed in is assumed to be a server-side cert, and the SSLObject returned has a couple of extra methods, listen() and accept(). Calling accept() does the SSL dance with the remote side, and returns an SSLObject. Does this need a PEP? Bill ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Python 3000 Sprint @ Google
Sounds like a good plan. I'm not a great coach though since I didn't write _ssl.c and I've never used openssl directly. But I can help you with the Python stuff of course! --Guido On 8/15/07, Bill Janssen <[EMAIL PROTECTED]> wrote: > I'd really like an excuse to implement server-side SSL support one of > these days. Could that be a sprint activity? Probably against 2.6 (I > doubt the Modules/_ssl.c file will change much for 3K). > > The idea is that if you call socket.ssl() on a socket that's bound to > an address, the socket is assumed to be server-side, the cert passed > in is assumed to be a server-side cert, and the SSLObject returned has > a couple of extra methods, listen() and accept(). Calling accept() does > the SSL dance with the remote side, and returns an SSLObject. > > Does this need a PEP? > > Bill > -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Python 3000 Sprint @ Google
> Sounds like a good plan. I'm not a great coach though since I didn't > write _ssl.c and I've never used openssl directly. But I can help you > with the Python stuff of course! Thanks (though I think I can handle the Python end of it, too :-). It's been a while since I wrote any Python C code, though -- are there better tools these days for debugging reference counting? Anyone know? Bill ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Python 3000 Sprint @ Google
On 8/15/07, Bill Janssen <[EMAIL PROTECTED]> wrote: > > Sounds like a good plan. I'm not a great coach though since I didn't > > write _ssl.c and I've never used openssl directly. But I can help you > > with the Python stuff of course! > > Thanks (though I think I can handle the Python end of it, too :-). > > It's been a while since I wrote any Python C code, though -- are there > better tools these days for debugging reference counting? Anyone know? The way I typically do it is to configure --with-pydebug. That shows the ref count in the interpreter and allows running tests with the -R flag to regrtest. When regrtest reports leaks, narrow down the (Python) code which causes a leak using bisection, find the C code which corresponds, and visually inspect the C code. Most leaks are pretty obvious this way. With good tests, this doesn't take much time. For pure memory leaks, valgrind works pretty well. n ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Python 3000 Sprint @ Google
On Aug 15, 2007, at 9:29 PM, Bill Janssen wrote: > I'd really like an excuse to implement server-side SSL support one of > these days. Could that be a sprint activity? Probably against 2.6 (I > doubt the Modules/_ssl.c file will change much for 3K). > > The idea is that if you call socket.ssl() on a socket that's bound to > an address, the socket is assumed to be server-side, the cert passed > in is assumed to be a server-side cert, and the SSLObject returned has > a couple of extra methods, listen() and accept(). Calling accept() > does > the SSL dance with the remote side, and returns an SSLObject. > > Does this need a PEP? Maybe one of the three existing Python/SSL libraries should be stdlib- ified instead of starting another new one from scratch? Just a thought... James ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Documentation switch imminent
On 8/15/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Georg Brandl schrieb:
> >
> > Neal will change his build scripts, so that the 2.6 and 3.0 devel
> > documentation pages at docs.python.org will be built from these new
> > trees soon.
>
> Okay, I made the switch. I tagged the state of both Python branches
> before the switch as tags/py{26,3k}-before-rstdocs/.
http://docs.python.org/dev/
http://docs.python.org/dev/3.0/
The upgrade went smoothly. Below are all the issues I noticed. I had
to install a version of python 2.5 since that is a minimum
requirement. I had to change from a plain 'make' in the Doc directory
to 'make html'. The output is in build/html rather than html/ now.
2.6 output:
trying to load pickled env... failed: [Errno 2] No such file or
directory: 'build/doctrees/environment.pickle'
writing output...
... library/contextlib.rst:3: Warning: 'with' will become a
reserved keyword in Python 2.6
tutorial/errors.rst:1: Warning: 'with' will become a reserved
keyword in Python
3.0 output:
Traceback (most recent call last):
File "tools/sphinx-build.py", line 13, in
from sphinx import main
File "/home/neal/python/py3k/Doc/tools/sphinx/__init__.py", line 16,
in
from .builder import builders
File "/home/neal/python/py3k/Doc/tools/sphinx/builder.py", line 35,
in
from .environment import BuildEnvironment
File "/home/neal/python/py3k/Doc/tools/sphinx/environment.py", line
34, in
from docutils.parsers.rst.states import Body
File "/home/neal/python/py3k/Doc/tools/docutils/parsers/rst/__init__.py",
line 77, in
from docutils.parsers.rst import states
File "/home/neal/python/py3k/Doc/tools/docutils/parsers/rst/states.py",
line 110, in
import roman
ImportError: No module named roman
After this error, I just linked my tools directory to the one in 2.6
(trunk) and that worked. I'm not sure if this will create problems in
the future.
trying to load pickled env... failed: [Errno 2] No such file or
directory: 'build/doctrees/environment.pickle'
writing output...
... library/contextlib.rst:3: Warning: 'with' will become a
reserved keyword in Python 2.6
library/shutil.rst:17: Warning: 'as' will become a reserved
keyword in Python 2.6
library/subprocess.rst:7: Warning: 'as' will become a reserved
keyword in Python 2.6
tutorial/errors.rst:1: Warning: 'with' will become a reserved
keyword in Python 2.6
I realize none of these are a big deal. However, it would be nice if
it was cleaned up so that people unfamiliar with building the docs
aren't surprised.
n
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Python 3000 Sprint @ Google
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 15, 2007, at 10:45 PM, Bill Janssen wrote: > > It's been a while since I wrote any Python C code, though -- are there > better tools these days for debugging reference counting? Anyone > know? No, but /that/ would make an awesome sprint topic . - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRsPVQnEjvBPtnXfVAQIp9QP/Y9DCqvBdbDdVvTQp8gt4so2HW/AqRyZU IF3SI/rrzMneslZRbU9PBlKbhq7oE/zwThpPss73W+64CoF2Z7N2dEGJJZncp+RK bo1jyzG2bituz1ZqXRFW8t373XAWLrMusABXNAD5Ypfd1PfbmziFaa6ttyu2jl5O 4QWxPaw4qU0= =+Zfi -END PGP SIGNATURE- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] Documentation switch imminent
Neal Norwitz schrieb:
> On 8/15/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
>> Georg Brandl schrieb:
>> >
>> > Neal will change his build scripts, so that the 2.6 and 3.0 devel
>> > documentation pages at docs.python.org will be built from these new
>> > trees soon.
>>
>> Okay, I made the switch. I tagged the state of both Python branches
>> before the switch as tags/py{26,3k}-before-rstdocs/.
>
> http://docs.python.org/dev/
> http://docs.python.org/dev/3.0/
Great!
> 3.0 output:
> Traceback (most recent call last):
> File "tools/sphinx-build.py", line 13, in
> from sphinx import main
> File "/home/neal/python/py3k/Doc/tools/sphinx/__init__.py", line 16,
> in
> from .builder import builders
> File "/home/neal/python/py3k/Doc/tools/sphinx/builder.py", line 35,
> in
> from .environment import BuildEnvironment
> File "/home/neal/python/py3k/Doc/tools/sphinx/environment.py", line
> 34, in
> from docutils.parsers.rst.states import Body
> File "/home/neal/python/py3k/Doc/tools/docutils/parsers/rst/__init__.py",
> line 77, in
> from docutils.parsers.rst import states
> File "/home/neal/python/py3k/Doc/tools/docutils/parsers/rst/states.py",
> line 110, in
> import roman
> ImportError: No module named roman
>
> After this error, I just linked my tools directory to the one in 2.6
> (trunk) and that worked. I'm not sure if this will create problems in
> the future.
No, it shouldn't. I added roman.py in trunk, but didn't
touch py3k since I don't want to disturb svnmerge more than necessary.
> trying to load pickled env... failed: [Errno 2] No such file or
> directory: 'build/doctrees/environment.pickle'
That is expected.
> writing output...
> ... library/contextlib.rst:3: Warning: 'with' will become a
> reserved keyword in Python 2.6
> library/shutil.rst:17: Warning: 'as' will become a reserved
> keyword in Python 2.6
> library/subprocess.rst:7: Warning: 'as' will become a reserved
> keyword in Python 2.6
> tutorial/errors.rst:1: Warning: 'with' will become a reserved
> keyword in Python 2.6
>
> I realize none of these are a big deal. However, it would be nice if
> it was cleaned up so that people unfamiliar with building the docs
> aren't surprised.
I'll have the with/as problem fixed soon, it should be nothing more than
setting the future flag for the call to compile().
Thanks,
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
