Alexey Gorshkov added the comment:
Ok. As
https://docs.python.org/dev/library/ssl.html#notes-on-non-blocking-sockets
says: Calling select() tells you that the OS-level socket can be read from (or
written to), and here is situation: len(select([ssl_socket],[],[], 0.2)[0])
returns 0, but ssl
Alexey Gorshkov added the comment:
Issue #21430: additions to the description of non-blocking SSL sockets
I do not see any mention of .pending() in Your commit.
Is this some personal hate to subject?
Are You going to document this method or not? Documenting it on line of text.
If You
Alexey Gorshkov added the comment:
I don't understand: Why python-config needs to seek realpath? Why
python-config is trying to be smarter than one who starts ./configure script?
As so, the right thing to this, is remove smart parts from python-config. But
as for fast hack
Alexey Gorshkov added the comment:
telnet 127.0.0.1 9000 can be used as testing client
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by Alexey Gorshkov <ani...@wayround.org>:
Removed file: http://bugs.python.org/file40855/s1.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Alexey Gorshkov <ani...@wayround.org>:
Added file: http://bugs.python.org/file40856/s1.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Alexey Gorshkov:
(in continuation to bug https://bugs.python.org/issue25471 )
socket.recv() raises 'BlockingIOError: [Errno 11] Resource temporarily
unavailable' in case, if setblocking(False) on socket returned by non-blocking
socket's .accept() method and client does
New submission from Alexey Gorshkov:
socket created with listening socket set to setblocking(False). gettimeout() of
accept()-returned socket returns 0.0 , but recv() method blocks while client is
connected and not sending any data. If client disconnects, socket returned by
accept() starting
Alexey Gorshkov added the comment:
I'm from Issue 26808. I'd like to see some explanation on: how about
QUERY_STRING value? Why only PATH_INFO is encoded in such a manner, but
QUERY_STRING is passed without any changes and does not requires any latin-1 to
utf-8 recodings?
--
nosy
Alexey Gorshkov added the comment:
also attaching same print output in console
--
Added file: http://bugs.python.org/file42535/Screenshot from 2016-04-20
14-28-03.png
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Alexey Gorshkov added the comment:
take a look at 'pi:' result, please. - attaching screenshot
--
Added file: http://bugs.python.org/file42534/Screenshot from 2016-04-20
14-26-03.png
___
Python tracker <rep...@bugs.python.org>
Changes by Alexey Gorshkov <ani...@wayround.org>:
Removed file: http://bugs.python.org/file42532/t.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Alexey Gorshkov:
example code is in attachment
example URI is (for example): http://127.0.0.1:8005/ัะตัั
--
components: Extension Modules
files: t.py
messages: 263819
nosy: animus
priority: normal
severity: normal
status: open
title: wsgiref.simple_server breaks
Changes by Alexey Gorshkov <ani...@wayround.org>:
Added file: http://bugs.python.org/file42533/t.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
14 matches
Mail list logo
