Mailman 3 May 2010 - docs

[issue8818] urlsplit and urlparse add extra slash when using scheme
by AdamN May 25, 2010

May 25, 2010

AdamN <adam(a)varud.com> added the comment: I appreciate what you're saying but nobody, I guarantee nobody, is using the '//cnn.com' semantics. Anyway, in RFC 3986 in the Syntax Components section, you'll see that the '://' is not part of scheme or netloc. I could imagine urlsplit() failing if the url was not prepended by '//' or 'scheme://', but why would being prepended with nothing cause urlsplit() to presume it's a path? Can we at least document this? ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8818> _______________________________________

2 1

[issue8818] urlsplit and urlparse add extra slash when using scheme
by AdamN May 25, 2010

May 25, 2010

AdamN <adam(a)varud.com> added the comment: Ok, you're right: >>> urlsplit('cnn.com') SplitResult(scheme='', netloc='', path='cnn.com', query='', fragment='') >>> urlsplit('//cnn.com') SplitResult(scheme='', netloc='cnn.com', path='', query='', fragment='') >>> Although I see that nowhere in the documentation. It seems to me that in the scenario most people are dealing with, where they are getting 'cnn.com' or 'http://cnn.com' but don't know which ahead of time, this will be useless. I don't see who would ever have '//cnn.com' without constructing that string specifically for urlsplit. I would propose that '/whatever' becomes the path because it starts with slash, otherwise, it becomes the netloc and everything after the first slash becomes the path. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8818> _______________________________________

2 1

[issue8818] urlsplit and urlparse add extra slash when using scheme
by R. David Murray May 25, 2010

May 25, 2010

R. David Murray <rdmurray(a)bitdance.com> added the comment: I've added Senthil as nosy to double check me, but my understanding is that the scheme is just the part up to the colon. If you want to have a netloc in the URL, you have to precede it with a '//'. Otherwise there's no netloc. ---------- assignee: docs@python -> nosy: +orsenthil _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8818> _______________________________________

1 0

[issue8818] urlsplit and urlparse add extra slash when using scheme
by AdamN May 25, 2010

May 25, 2010

AdamN <adam(a)varud.com> added the comment: Great, thanks. However urlsplit and urlparse still take what one would expect to be recognized as the netloc and assigns it to the 'path' key. If that is by design perhaps we should at least warn people? ---------- status: closed -> open _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8818> _______________________________________

1 0

[issue8818] urlsplit and urlparse add extra slash when using scheme
by R. David Murray May 25, 2010

May 25, 2010

R. David Murray <rdmurray(a)bitdance.com> added the comment: The keyword in the code is 'scheme'. I've updated the docs accordingly in r81521 and r81522. ---------- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python, r.david.murray resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python 2.7, Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8818> _______________________________________

1 0

[issue8785] findall() and finditer() docs misleading
by Hagen Fürstenau May 22, 2010

May 22, 2010

New submission from Hagen Fürstenau <hfuerstenau(a)gmx.net>: The docs for the RegexpObject methods findall and finditer are misleading: They are said to behave the same way as the respective functions, but in fact the parameter semantics are different. ---------- assignee: docs@python components: Documentation messages: 106286 nosy: docs@python, hagen priority: normal severity: normal status: open title: findall() and finditer() docs misleading versions: Python 2.6, Python 2.7, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8785> _______________________________________

2 1

Incorrect information for multiprocessing.Semaphore
by Mike Hobbs May 21, 2010

May 21, 2010

There's a Note on the documentation for multiprocessing.Semaphore that says that sem_timedwait is unsupported on OS/X and that any timeout argument provided to acquire() will be ignored. I checked the Modules/_multiprocessing/semaphore.c code on the 2.6, 3.0, and 3.1 branches and I see that the module will fallback to sem_timedwait_save() if sem_timedwait is not available. That is, it will not ignore the timeout, but will instead emulate a timed wait using a sleep loop.

2 1

[issue8709] mention explicitly Windows support for os.devnull
by akira May 21, 2010

May 21, 2010

New submission from akira <4kir4.1i(a)gmail.com>: Currently it is not obvious that os.devnull works on Windows. ---------- assignee: docs@python components: Documentation files: doc-os-devnull-windows-r81160.diff keywords: patch messages: 105688 nosy: akira, docs@python priority: normal severity: normal status: open title: mention explicitly Windows support for os.devnull type: feature request Added file: http://bugs.python.org/file17331/doc-os-devnull-windows-r81160.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8709> _______________________________________

4 4

no success in downloading python documentation
by Pietro Perona May 21, 2010

May 21, 2010

I clicked on the download links and got this error message. P. Not Found The requested URL /ftp/python/doc/current/python-2.6.4-docs-pdf-letter.zip was not found on this server. Apache/2.2.9 (Debian) DAV/2 SVN/1.5.1 mod_ssl/2.2.9 OpenSSL/0.9.8g mod_wsgi/2.5 Python/2.5.2 Server at docs.python.org Port 80

2 1

missing documentation on tempfile.NamedTempFile
by Jelte Jansen May 21, 2010

May 21, 2010

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, in the docs for python 3.1.2, the argument list for tempfile.NamedTemporaryFile() is incomplete on http://docs.python.org/py3k/library/tempfile.html It does not mention the encoding and newline arguments. I haven't checked the other functions there but I assume this is not the only one (nor have I checked other versions, sorry). I found this out because I got quite unexpected errors when not using named parameters, which I know I should, but I was trying to find out why something else didn't work for me. On a related note, another nice addition would be to mention that if the prefix parameter is absolute, dir is ignored :) Thanks, Jelte -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvysfwACgkQ4nZCKsdOncX8owCg1wpMi3XSrSiHxWA8zDqvZGqx 5nAAn3kZ8y0vL1Eprh+0yyIgLYRbTb+S =FFMD -----END PGP SIGNATURE-----

2 1