[issue20762] SSLSocket.read() not documented

2017-09-05 Thread Christian Heimes
Christian Heimes added the comment: I'll deprecate read() and write() in my upcoming PEP. -- resolution: -> later stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue20762] SSLSocket.read() not documented

2016-09-15 Thread Christian Heimes
Changes by Christian Heimes : -- components: +SSL ___ Python tracker ___ ___

[issue20762] SSLSocket.read() not documented

2016-09-08 Thread Martin Panter
Martin Panter added the comment: In the meantime, full documentation for the read() and write() methods was added for Python 3 in revision 61e52fda1006. The Python 2 documentation only mentions read() indirectly, in passing and in example code, and does not mention write(). But deprecating

[issue20762] SSLSocket.read() not documented

2016-09-08 Thread Christian Heimes
Christian Heimes added the comment: Sounds good, let's deprecate them with #28022. -- superseder: -> SSL releated deprecation for 3.6 versions: +Python 3.6, Python 3.7 -Python 3.5 ___ Python tracker

[issue20762] SSLSocket.read() not documented

2014-02-24 Thread Enrico Bianchi
New submission from Enrico Bianchi: although exists, read() method isn't reported in the SSLSocket documentation. Please, fix it -- assignee: docs@python components: Documentation messages: 212115 nosy: docs@python, ebianchi priority: normal severity: normal status: open title:

[issue20762] SSLSocket.read() not documented

2014-02-24 Thread R. David Murray
R. David Murray added the comment: That's because SSLSocket is a wrapper around a regular socket, and the read method is documented in the Socket documentation. You will notice that *only* SSL specific methods are documented in the SSLSocket documentation. -- nosy: +r.david.murray

[issue20762] SSLSocket.read() not documented

2014-02-24 Thread R. David Murray
R. David Murray added the comment: Oops. My mistake. It's been too long since I did any socket programming :( -- resolution: invalid - stage: committed/rejected - needs patch status: closed - open ___ Python tracker rep...@bugs.python.org

[issue20762] SSLSocket.read() not documented

2014-02-24 Thread Antoine Pitrou
Antoine Pitrou added the comment: Hmm, yeah, this is actually intended. The read() and write() methods on SSLSocket are not intended to be a public API: you should call send() or recv() instead. Ideally we would deprecate the read() and write() methods and rename the internal helpers to

[issue20762] SSLSocket.read() not documented

2014-02-24 Thread Ezio Melotti
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20762 ___ ___