[issue34218] test_xml_etree_c leaked [68, 68, 74] references, sum=210

New submission from Pablo Galindo Salgado : Builder x86 Gentoo Refleaks 3.x reports that test_xml_etree_c is potentially leaking references and blocks: https://buildbot.python.org/all/#builders/1/builds/295 -- Ran 148 tests

[issue12743] C API marshalling doc contains XXX

Change by Berker Peksag : -- pull_requests: +7981 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28009] core logic of uuid.getnode() is broken for AIX - all versions

Michael Felt added the comment: @pitrou: re: Is nohup required in the example you just posted or is that a red herring? I just use nohup to merge stdout and stderr when grepping for messages - and to, ideally, have the stdout and stderr messages properly synced in the output stream. So, I

[issue34194] test_ssl, AIX, and defaults for _ssl connections

Michael Felt added the comment: update: went back to check what worked, did not work without the environment variable set. I am going to guess that pip(3) is able to make use of the environment variable SSL_CERT_FILE as pip download fails (in some cases) without it, but succeeds with it.

[issue34170] Py_Initialize(): computing path configuration must not have side effect (PEP 432)

STINNER Victor added the comment: New changeset d3b191992e0f3c1eb27cb68478b875d60e859976 by Victor Stinner in branch 'master': bpo-34170: Cleanup pymain_run_python() (GH-8455) https://github.com/python/cpython/commit/d3b191992e0f3c1eb27cb68478b875d60e859976 --

[issue34194] test_ssl, AIX, and defaults for _ssl connections

Michael Felt added the comment: Any comments re: environment variables - even if the answer is None! -- versions: +Python 2.7, Python 3.8 ___ Python tracker ___

[issue34167] Standard library docs: prev/next skip right over 16.11

Change by INADA Naoki : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue34192] FunctionType.__new__ can generate functions that immediately crash

Karthikeyan Singaravelan added the comment: The assertion also fails on master. I did some manual git blame work. The assertion passes with commit 7324b5ce8e7c031a0a3832a6a8d7c639111ae0ff. It fails with the next commit 078f1814f1a4413a2a0fdb8cf4490ee0fc98ef34

<    1   2