New submission from zodalahtathi:
This is probably not the biggest bug ever, but in the doc for
ipaddress.IPv6Network:
An integer packed into a bytes object of length 16, bit-endian
should be changed to:
An integer packed into a bytes object of length 16, big-endian
--
assignee
New submission from zodalahtathi:
socket.socket has a context manager to automatically close the socket with the
`with` statement:
https://hg.python.org/cpython/file/d1bf181afa82/Lib/socket.py#l138
However it is not documented, unlike socket.create_connection.
--
assignee: docs
zodalahtathi added the comment:
Thank you
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22959
___
___
Python-bugs-list mailing list
Unsubscribe
zodalahtathi added the comment:
I think it does, when passing a context with ssl_context.verify_mode !=
ss.CERT_NONE, and when not setting the check_hostname parameter:
1. will_verify will be True
(https://hg.python.org/cpython/file/3.4/Lib/http/client.py#l1207)
2. check_hostname will be True
zodalahtathi added the comment:
Thank you
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22960
___
___
Python-bugs-list mailing list
Unsubscribe
zodalahtathi added the comment:
I agree that changing a default to something less secure is not something to do
lightly, however I think forcing a check that is explicitly disabled is a bug
and can be counter productive security wise.
People who don't have time to look at the stdlib code
New submission from zodalahtathi:
http.client.HTTPSConnection has both a check_hostname parameter, and a context
parameter to pass an already setup SSL context.
When check_hostname is not set and thus is None, and when passing a SSL context
set to NOT check hostnames, ie:
import http.client
New submission from zodalahtathi:
When using xmlrpc.server it is possible (despite being intrusive) to use a
custom SSL context, ie:
import ssl
import xmlrpc.server
rpc_server = xmlrpc.server.SimpleXMLRPCServer(...)
ssl_context = ssl.SSLContext()
# setup the context ...
rpc_server.socket
New submission from zodalahtathi:
Python 3.4 added a 'input' argument to the subprocess.check_output function to
send bytes to stdin, but it was surprisingly not added to other subprocess
helpers.
The same functionality should be added to subprocess.check_call and
subprocess.call
zodalahtathi added the comment:
I think the 'stdin argument can be any file like or stream for all subprocess
functions' approach would be the best solution, because it is misleading to
differentiate behavior based on internal implementation details (the use of
communicate), when the function
New submission from zodalahtathi:
shutil.move sometimes fail when the underlining filesystem has limitations.
Here is a part of a stacktrace I'm getting :
File /usr/local/lib/python3.3/shutil.py, line 534, in move
copy2(src, real_dst)
File /usr/local/lib/python3.3/shutil.py, line 244
zodalahtathi m8r-a70...@mailinator.com added the comment:
Thank you for the explanation
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14539
New submission from zodalahtathi m8r-a70...@mailinator.com:
The logging module does not print logging message when the logging level is set
to a level inferior to the default level.
I can reproduce it using the Python3 (3.2.2) package from Ubuntu 12.04 beta2,
or using a hand compiled Python
13 matches
Mail list logo
