[issue35970] no help flag in base64 util

New submission from Robert Kuska : I failed today to print help message for base64 utility without an error: $ python3 -m base64 -help option -h not recognized usage: /usr/local/Cellar/python/3.7.2_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/base64.py [-d|-e|-u|-t] [file

[issue1298835] Add a vendor-packages directory for system-supplied modules

Robert Kuska added the comment: There is ongoing discussion on pip's github tracker [1] about default location where to install user modules. IMO this is something that should be dealt with in Python Interpreter Core [2][3]. I would like to hear some opinion from python devs on this.

[issue1298835] Add a vendor-packages directory for system-supplied modules

Robert Kuska added the comment: Ok, I have started a thread at pypa-devs google group. https://groups.google.com/forum/#!topic/pypa-dev/r6qsAmJl9t0 -- ___ Python tracker <http://bugs.python.org/issue1298

[issue21308] PEP 466: backport ssl changes

Robert Kuska added the comment: Hi everyone, I went ahead and I've applied ssl-backport.diff (alex, 2014-08-07 18:49) patch into Python 2.7.8 on Fedora Rawhide (currently only scratch build). My report: Firstly, I've encountered seg fault, I fixed this with patch from http://bugs.

[issue22638] ssl module: the SSLv3 protocol is vulnerable ("POODLE" attack)

Robert Kuska added the comment: FYI fedora (rawhide) has SSLv3 disabled in SSLv23 method of openssl package. http://pkgs.fedoraproject.org/cgit/openssl.git/commit/?id=80b5477597e9f0d9fababd854adfb4988b37efd5 This looks like the same approach as in attached issue22638.diff. -- nosy

[issue20160] broken ctypes calling convention on MSVC / 64-bit Windows (large structs)

Robert Kuska added the comment: This commit (probably) breaks aarch64 python build. See https://bugzilla.redhat.com/show_bug.cgi?id=1174037 Build was done with libffi 3.1.6, I have also tried with latest upstream libffi version with same result. (gdb) b ReturnRect Function "ReturnRect

[issue20160] broken ctypes calling convention on MSVC / 64-bit Windows (large structs)

Robert Kuska added the comment: FYI The bug was found in libffi. I have tried and rebuilt python also with *bundled libffi* with the *same result* (=test failure). There is more info in the bugzilla mentioned in my previous post along with the libffi patch

[issue23249] test_win32 fails on aarch64

New submission from Robert Kuska: Original bug report at https://bugzilla.redhat.com/show_bug.cgi?id=1174037 Additional informations at Issue #20160 Note that this was reproduced not only with separate libffi package but also with libffi bundled in python. Reproduced with Python 2.7.9 but same

[issue23249] test_win32 fails on aarch64

Changes by Robert Kuska : -- keywords: +patch Added file: http://bugs.python.org/file37724/libffi-mattip.patch ___ Python tracker <http://bugs.python.org/issue23

[issue20160] broken ctypes calling convention on MSVC / 64-bit Windows (large structs)

Robert Kuska added the comment: I have created #23249. -- ___ Python tracker <http://bugs.python.org/issue20160> ___ ___ Python-bugs-list mailing list Unsub

[issue23249] test_win32 fails on aarch64

Robert Kuska added the comment: Sorry for the late answer, I forgot about this issue. 3.2.1 doesn't contain required fix(sorry for the misleading suggestion 'or update bundled libffi' from report) but master branch at upstream repo (https://github.com/atgre

[issue23420] python -m cProfile -s fails with non informative message

New submission from Robert Kuska: Originaly reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1160640 I've forgotten to add the sort value to the -s option of cProfile which results in a traceback instead of user friendly error message. In the example below hello.py just pri

[issue23420] python -m cProfile -s fails with non informative message

Changes by Robert Kuska : Added file: http://bugs.python.org/file38054/sort-choices.patch ___ Python tracker <http://bugs.python.org/issue23420> ___ ___ Python-bugs-list m

[issue23420] python -m cProfile -s fails with non informative message

Changes by Robert Kuska : Added file: http://bugs.python.org/file38055/sort-choices.patch ___ Python tracker <http://bugs.python.org/issue23420> ___ ___ Python-bugs-list m

[issue22032] Use __qualname__ together with __module__

Robert Kuska added the comment: FYI This also broke nosetests tests which relies on exact output. https://github.com/nose-devs/nose/issues/928 -- nosy: +rkuska ___ Python tracker <http://bugs.python.org/issue22

[issue22032] Use __qualname__ together with __module__

Robert Kuska added the comment: I agree with you Victor that tests shouldn't rely on the exact representation and I also understand why such change was introduced therefore I don't think there is any bug to report, my comment was just pure 'FYI' for anyone who will come

[issue19527] Test failures with COUNT_ALLOCS

Robert Kuska added the comment: With Python-3.5 and COUNT_ALLOCS enabled following new tests fail also: FAIL: test_is_finalizing (test.test_sys.SysModuleTest) -- Traceback (most recent call last): File "/builddir/build/

[issue19527] Test failures with COUNT_ALLOCS

Robert Kuska added the comment: FYI There is also issue23034 where is proposed "-X showalloccount" option to suppress the output, we use (custom patch) environment variable to filter out the verbose output in Fedora. -- ___ Python trac

[issue23857] Make default HTTPS certificate verification setting configurable

Robert Kuska added the comment: If test fail it will print out non-telling message which make debugging a little bit hard: FAIL: test__https_verify_envvar (test.test_ssl.ContextTests

[issue26661] python fails to locate system libffi

New submission from Robert Kuska: Python fails to locate system version of ffi when building. We delete bundled version of ffi and build process fail with following error: error: [Errno 2] No such file or directory: '/builddir/build/BUILD/Python-3.5.1/Modules/_ctypes/libffi' This

[issue23769] valgrind reports leaks for test_zipimport

New submission from Robert Kuska: Leaks happen only when both testDoctestFile and testDoctestSuite are run. Run with Python 3.4.2 and 3.4.1 with same result. I have extracted those two tests into `leak.py` (attached). > $ valgrind --suppressions=/../cpython/Misc/valgrind-python.supp pyth

[issue23769] valgrind reports leaks for test_zipimport

Changes by Robert Kuska : Added file: http://bugs.python.org/file38673/report ___ Python tracker <http://bugs.python.org/issue23769> ___ ___ Python-bugs-list mailin

[issue23769] valgrind reports leaks for test_zipimport

Robert Kuska added the comment: Summary for valgrind python3 test_zipimport.py ==18608== ==18608== HEAP SUMMARY: ==18608== in use at exit: 1,596,390 bytes in 11,536 blocks ==18608== total heap usage: 343,849 allocs, 332,313 frees, 59,355,776 bytes allocated ==18608== ==18608== LEAK

[issue23769] valgrind reports leaks for test_zipimport

Robert Kuska added the comment: I tried leak2.py with valgrind, I've uncommented the lines you mentioned. > $ valgrind python3

[issue23857] [RFE] Make certificate verification optionable

New submission from Robert Kuska: Proposed patch adds possibility to opt-out certificate verification. Disclaimer: it is just proof of concept as the config value is hard-coded. How it works? This patch depends on existence of config file which holds information about the protocol settings

[issue23857] [RFE] Make certificate verification optionable

Changes by Robert Kuska : -- nosy: +bkabrda ___ Python tracker <http://bugs.python.org/issue23857> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23857] [RFE] Make certificate verification optionable

Robert Kuska added the comment: 1) patch attached, dunno how I missed it, thank you. 3) I work for Red Hat additional interest for example here http://seclists.org/oss-sec/2015/q1/785 2) It exists but it is not system wide, I would like to provide users option to opt-in or opt-out without

[issue23857] [RFE] Make certificate verification optionable

Robert Kuska added the comment: If you mean hack site.py to be sitecustomize I don't find it as a sufficient solution because users may use their own sitecustomize and this way we would replace theirs. Sslcustomize solution could be another option how to handle this but the config

[issue23857] [RFE] Make certificate verification optionable

Robert Kuska added the comment: ( ^ I was replying to Victor) -- ___ Python tracker <http://bugs.python.org/issue23857> ___ ___ Python-bugs-list mailing list Unsub

[issue23857] Make default HTTPS certificate verification setting configurable via global ini file

Robert Kuska added the comment: >Le 06/04/2015 13:29, Nick Coghlan a écrit : >> >> So while this isn't a feature upstream itself needs, it's one potentially needed by multiple *downstreams*, so in my view it makes sense for us to work with upstream to come up with