Meador Inge mead...@gmail.com added the comment:
I opened issue13380 for fixing the ctypes regrtest caching problem.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13250
___
New submission from Meador Inge mead...@gmail.com:
While implementing a patch for issue13096 I found a reference leak in 'ctypes'.
I couldn't find the cause immediately, but it can be
reproduced by applying the attached patch and running:
[meadori@motherbrain cpython]$ ./python -m test -R :
Benjamin Peterson benja...@python.org added the comment:
The cause is ctypes caches POINTER types. You have to make sure to clear the
cache.
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13250
Martin v. Löwis mar...@v.loewis.de added the comment:
So it's not a bug at all, right?
--
nosy: +loewis
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13250
Meador Inge mead...@gmail.com added the comment:
Ah, I see now. Thanks Benjamin.
So it's not a bug at all, right?
A bug in regrtest.py maybe. 'dash_R_cleanup' clears various other caches in
between test runs to avoid false positives like this. Perhaps
'ctypes._pointer_type_cache'
should be
