Senko Rasic added the comment:
Here's a patch that adds checks and ValueError raises to SSLSocket.read and
SSLSocket.write.
My first attempt was to add the check to _checkClosed to mirror the
IOBase._checkClosed, but in SSLSocket its semantics are different (the idea is
for the subcla
Senko Rasic added the comment:
Yep, signed.
--
___
Python tracker
<http://bugs.python.org/issue6386>
___
___
Python-bugs-list mailing list
Unsubscribe:
Senko Rasic added the comment:
Patch for modifying the modules part of tutorial with the changes suggested by
jamadagni (reworded slightly so the note is outside the itemized list).
--
keywords: +patch
nosy: +senko
Added file: http://bugs.python.org/file30822/tutorial-symlink-syspath
Senko Rasic added the comment:
The attached test (issue-17324-test-1) reproduces the issue for me on
3.4.0alpha.
--
nosy: +senko
___
Python tracker
<http://bugs.python.org/issue17
Senko Rasic added the comment:
Checked with 3.4.0 alpha, works fine. Apart from the tests mentioned, I used
the following script to check digest auth:
from urllib import request
url = 'http://httpbin.org/digest-auth/auth/user/passwd'
req = request.R
Senko Rasic added the comment:
The second patch (proposed fix).
--
Added file: http://bugs.python.org/file30809/distutils-symlink-fix.diff
___
Python tracker
<http://bugs.python.org/issue1052
Senko Rasic added the comment:
Here are two patches:
* test against py3k test_sdist.py (should crash without a fix)
* a proposed fix
The proposed fix not only changes lstat, but also changes other relevant paths
to actually include dangling symlinks in the filelists. I've split them into
Senko Rasic added the comment:
I vote for the parse method converting the spaces (and only the spaces)
explicitly, for the following reasons:
* the spaces must be encoded for the server to accept them
* no user-encoded url will ever have spaces in them
* space quoting is idempotent: quote
Senko Rasic added the comment:
Here's a patch just removing the reference.
Although potentially referencing io.IOBase.readline instead would be more
correct, IMHO it'd be just more confusing to users reading the docs.
--
keywords: +patch
nosy: +senko
Added file: http://bugs.