Vincent Pelletier plr.vinc...@gmail.com added the comment:
This change causes the following behaviour:
import inspect
class B(object):
... def f(self):
... pass
...
inspect.getmembers(B, inspect.ismethod)
[]
While I would expect the result to contain f:
inspect.ismethod(B.f)
True
Vincent Pelletier plr.vinc...@gmail.com added the comment:
Sorry, I forgot to mention I'm using python2.7 .
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1785
New submission from Vincent Pelletier plr.vinc...@gmail.com:
ctypes.create_string_buffer documentation[1] says init_or_size parameter should
accept a string. As of 3.2, it raises:
import ctypes
ctypes.create_string_buffer('foo')
Traceback (most recent call last):
File stdin, line 1
Vincent Pelletier plr.vinc...@gmail.com added the comment:
Thanks for the quick reply.
FWIW, in 2.7 doc ctype.create_string_buffer is said to accept unicode objects
as parameter. I don't use this personally, so I don't mind 3.x only working on
bytes - and already fixed my code accordingly
New submission from Vincent Pelletier plr.vinc...@gmail.com:
When storing a ctype function pointer in a ctype structure field, a reference
remains even when that field is overwritten with some values:
- None
- None cast into a function pointer
But the reference is somehow removed when
Vincent Pelletier plr.vinc...@gmail.com added the comment:
Trying to generate a graph on several python and several uncommented lines, I
see that my test case is incomplete. Time to review my copy.
--
resolution: - invalid
status: open - closed
New submission from Vincent Pelletier plr.vinc...@gmail.com:
SafeTransport class supports a 2-tuple as uri, in order to pass x509 parameters
to httplib.HTTPSConnection .
xmlrpclib.ServerProxy.__init__ fails when given such tuple, because it calls:
urllib.splittype(uri)
without checking uri
Vincent Pelletier plr.vinc...@gmail.com added the comment:
Then I guess SafeTransport should be cleaned to remove its dead code (tuple
host handling), and the class you link to should be included (in spirit if not
verbatim) in xmlrpclib.
Also, sorry, I realized after posting that this bug
New submission from Vincent Pelletier:
Quoting a github gist[1] (not mine, I found it while googling for this error)
clearly illustrating the issue:
# Python 2
>>> b = bytearray(8)
>>> v = memoryview(b)
>>> v[0] = 42
Traceback (most recent call last):
File &quo
Vincent Pelletier added the comment:
My original point of view was that:
- python3 is right to only accept integers, consistently with "str != bytes"
- python2 is rather right to accept str, consistently with "str == bytes"
- maybe the bug is that python2 should not rej
Change by Vincent Pelletier :
--
assignee: -> christian.heimes
components: +Library (Lib), SSL
nosy: +christian.heimes
___
Python tracker
<https://bugs.python.org/issu
Vincent Pelletier added the comment:
The reason which led me into this is server certificate renewal: my service
crashed on that setter 2 months after starting, when it received a new
certificate.
I toyed with the idea of closing the listening sockets, but without closing
would be even
New submission from Vincent Pelletier :
>From ssl.py, both on 2.7.15 and 3.6.6:
class SSLSocket(...):
...
@context.setter
def context(self, ctx):
self._context = ctx
self._sslobj.context = ctx
_sslobj is only set when socket is connected. While this is not a big is
Vincent Pelletier added the comment:
Added: affects Python 3.9
This bug is still preventing (...or shall I say "discourages", as the setter is
effective but raises) server-side SSL certificate reloading on long-running
services.
This codepath on listening sockets is necessary fo
14 matches
Mail list logo
