Changes by Beda Kosata :
Added file: http://bugs.python.org/file17022/chain.pem
___
Python tracker
<http://bugs.python.org/issue8484>
___
___
Python-bugs-list mailin
New submission from Beda Kosata :
When trying a secure connection to an HTTPS server with server certificate
verification, I get very strange behaviour when the digest used in the signing
certificate is SHA-256 (+RSA).
On Windows with Python 2.6.4 or 2.6.5, I consistently get the following
New submission from Beda Kosata :
The method subprocess.Popen.communicate (more the underlying
_communicate) writes the input to the stdin stream without encoding,
regardless of it being a unicode string. The result is incorrect
behavior of the running program as it receives 4 bytes for each
Beda Kosata added the comment:
I would certainly expect it to return unicode when either the "modified"
string or the replacement are unicode. I don't think that the type of
the replaced string should influence the type of the result.
__
Tracker &l
New submission from Beda Kosata:
While re.sub normally returns unicode strings when processing unicode,
it returns a normal string when dealing with an empty unicode string.
Example:
>>> print type( re.sub( "XX", "", u""))
>>> print type( re.
