[issue36683] duplicate method definition in Lib/test/test_utf8_mode.py

Change by Xavier de Gaye : -- resolution: fixed -> stage: resolved -> status: closed -> open versions: +Python 3.7 ___ Python tracker <https://bugs.python.or

[issue36678] duplicate method definitions in Lib/test/test_dataclasses.py

Change by Xavier de Gaye : -- resolution: fixed -> stage: resolved -> status: closed -> open versions: +Python 3.7 ___ Python tracker <https://bugs.python.or

[issue19113] duplicate test names in Lib/ctypes/test/test_functions.py

Change by Xavier de Gaye : -- versions: +Python 3.7 ___ Python tracker <https://bugs.python.org/issue19113> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36679] duplicate method definition in Lib/test/test_genericclass.py

Change by Xavier de Gaye : -- resolution: fixed -> stage: resolved -> status: closed -> open versions: +Python 3.7 ___ Python tracker <https://bugs.python.or

[issue16079] list duplicate test names with patchcheck

Xavier de Gaye added the comment: Not sure the unittest module is the right place to implement these checks. The following issues deal with duplicates that are not unittest methods: #19127 #19128 #36711 -- ___ Python tracker <ht

[issue16079] list duplicate test names with patchcheck

Change by Xavier de Gaye : -- pull_requests: +12864 ___ Python tracker <https://bugs.python.org/issue16079> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16079] list duplicate test names with patchcheck

Xavier de Gaye added the comment: List of issues entered for all the current duplicate method definitions in 2.7: #19113 #36711 #36712 #36713 -- ___ Python tracker <https://bugs.python.org/issue16

[issue36713] uplicate method definition in Lib/ctypes/test/test_unicode.py

New submission from Xavier de Gaye : As reported in issue 16079, the following method is a duplicate: Lib/ctypes/test/test_unicode.py:110 StringTestCase.test_ascii_replace -- components: Library (Lib) messages: 340782 nosy: xdegaye priority: normal severity: normal stage: needs patch

[issue19119] duplicate test name in Lib/test/test_heapq.py

Change by Xavier de Gaye : -- versions: +Python 3.8 -Python 3.4, Python 3.5 ___ Python tracker <https://bugs.python.org/issue19119> ___ ___ Python-bugs-list m

[issue19113] duplicate test names in Lib/ctypes/test/test_functions.py

Change by Xavier de Gaye : -- versions: +Python 2.7, Python 3.8 -Python 3.4, Python 3.5 ___ Python tracker <https://bugs.python.org/issue19113> ___ ___ Python-bug

[issue36711] duplicate method definition in Lib/email/feedparser.py

New submission from Xavier de Gaye : As reported in issue 16079, the following method is a duplicate: Lib/email/feedparser.py:140 BufferedSubFile.pushlines -- components: Library (Lib) messages: 340778 nosy: xdegaye priority: normal severity: normal stage: needs patch status: open

[issue36712] duplicate method definition in Lib/email/test/test_email_renamed.py

New submission from Xavier de Gaye : As reported in issue 16079, the following method is a duplicate: Lib/email/test/test_email_renamed.py:521 TestEncoders.test_default_cte -- components: Library (Lib) messages: 340781 nosy: xdegaye priority: normal severity: normal stage: needs patch

[issue16079] list duplicate test names with patchcheck

Xavier de Gaye added the comment: PR 12886 adds a check on duplicate method definitions to the travis() function of patchcheck.py. False positives must be entered to Tools/scripts/duplicates_ignored.txt. The existing duplicates have been entered to this file (with the corresponding bpo

[issue16079] list duplicate test names with patchcheck

Change by Xavier de Gaye : -- pull_requests: +12812 ___ Python tracker <https://bugs.python.org/issue16079> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16079] list duplicate test names with patchcheck

Xavier de Gaye added the comment: List of issues entered for all the current duplicate method definitions: #19113 #19119 #36678 #36679 #36680 #36681 #36682 #36683 -- ___ Python tracker <https://bugs.python.org/issue16

[issue36683] duplicate method definition in Lib/test/test_utf8_mode.py

New submission from Xavier de Gaye : As reported in issue 16079, the following method is a duplicate: Lib/test/test_utf8_mode.py: UTF8ModeTests.test_io_encoding -- components: Library (Lib) messages: 340583 nosy: xdegaye priority: normal severity: normal stage: needs patch status

[issue36682] duplicate method definitions in Lib/test/test_sys_setprofile.py

New submission from Xavier de Gaye : As reported in issue 16079, the following methods are duplicates: Lib/test/test_sys_setprofile.py:354 ProfileSimulatorTestCase.test_unbound_method_no_args Lib/test/test_sys_setprofile.py:363 ProfileSimulatorTestCase.test_unbound_method_invalid_args

[issue36681] duplicate method definition in Lib/test/test_logging.py

New submission from Xavier de Gaye : As reported in issue 16079, the following method is a duplicate: Lib/test/test_logging.py:328 BuiltinLevelsTest.test_regression_29220 -- components: Library (Lib) messages: 340581 nosy: xdegaye priority: normal severity: normal stage: needs patch

[issue36680] duplicate method definition in Lib/test/test_importlib/test_util.py

New submission from Xavier de Gaye : As reported in issue 16079, the following method is a duplicate: Lib/test/test_importlib/test_util.py:755 PEP3147Tests.test_source_from_cache_path_like_arg -- components: Library (Lib) messages: 340580 nosy: xdegaye priority: normal severity

[issue36679] duplicate method definition in Lib/test/test_genericclass.py

New submission from Xavier de Gaye : As reported in issue 16079, the following method is a duplicate: Lib/test/test_genericclass.py:161 TestClassGetitem.test_class_getitem -- components: Library (Lib) messages: 340579 nosy: xdegaye priority: normal severity: normal stage: needs patch

[issue36678] duplicate method definitions in Lib/test/test_dataclasses.py

New submission from Xavier de Gaye : As reported in issue 16079, the following methodes are duplicates: Lib/test/test_dataclasses.py:700 TestCase.test_not_tuple Lib/test/test_dataclasses.py:1406 TestCase.test_helper_asdict_builtin_containers Lib/test/test_dataclasses.py:1579

[issue16079] list duplicate test names with patchcheck

Xavier de Gaye added the comment: Thanks for the link Gregory. I will write a script based on ast and check its output against pylint and against the current script based on tokenize. The travis() function of Tools/scripts/patchcheck.py may be modified to import this script and run it only

[issue16079] list duplicate test names with patchcheck

Xavier de Gaye added the comment: False positives must be added to the 'ignored_duplicates' file in order to have duplicate_code_names.py exit with success. Not sure whether this may be considered as an annoyance by commiters, if TRAVIS would fail when duplicate_code_names.py fails. All

[issue27326] SIGSEV in test_window_funcs of test_curses

Xavier de Gaye added the comment: Cannot reproduce the crash with Python 3.7.3 on ncurses 6.1. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36630] failure of test_colors_funcs in test_curses with ncurses 6.1

New submission from Xavier de Gaye : ncurses version: 6.1 TERM: screen-256color $ ./python -m test -u curses test_curses Run tests sequentially 0:00:00 load avg: 0.55 [1/1] test_curses test test_curses failed -- Traceback (most recent call last): File "/path/to/Lib/test/test_curses.py&q

[issue23768] assert on getting the representation of a thread in atexit function

Change by Xavier de Gaye : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue22991] test_gdb leaves the terminal in raw mode with gdb 7.8.1

Change by Xavier de Gaye : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue16079] list duplicate test names with patchcheck

Xavier de Gaye added the comment: Upgrading the script to account for Python changes. This is now duplicate_code_names_3.py $ ./python ./duplicate_code_names_3.py --ignore ignored_duplicates Lib/test Duplicate method names: Lib/test/test_dataclasses.py:1406

[issue19113] duplicate test names in Lib/ctypes/test/test_functions.py

Xavier de Gaye added the comment: Still fails on Python 3.8.0a3+. -- ___ Python tracker <https://bugs.python.org/issue19113> ___ ___ Python-bugs-list mailin

[issue36537] except statement block incorrectly assumes end of scope(?).

Xavier de Gaye added the comment: > Now, I need to *inconveniently* put some dummy code after the ser_trace call > every time I want to access the exception inside the except block Knowing that pdb stops just before the interpreter executes the line after pdb.set_trace(), what preven

[issue19417] Bdb: add a unittest file (test.test_bdb)

Change by Xavier de Gaye : -- dependencies: -Bdb: add docstrings resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36544] cannot import hashlib when openssl is missing

Xavier de Gaye added the comment: Thanks Victor for the refactoring of setup.py. That was badly needed indeed. -- ___ Python tracker <https://bugs.python.org/issue36

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

Xavier de Gaye added the comment: FWIW PR 12708 has been merged. -- ___ Python tracker <https://bugs.python.org/issue36414> ___ ___ Python-bugs-list mailin

[issue36544] cannot import hashlib when openssl is missing

Change by Xavier de Gaye : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue36559] "import random" should import hashlib on demand (nor load OpenSSL)

Xavier de Gaye added the comment: > You could also use the internal _sha512 module. It's always present This is not true at the moment, the _sha512 module is not present when openssl is missing. This is a bug in setup.py that prevents building the _sha512 module when openssl is missing.

[issue24565] the f_lineno getter is broken

Xavier de Gaye added the comment: Fixed a bug in the implementation of PR 12419 while running the coverage.py test suite: f_lineno must be valid upon 'call' trace events. The confusion stems from the reason why until now we have prevented line jumps from 'call' trace events, see below

[issue36537] except statement block incorrectly assumes end of scope(?).

Xavier de Gaye added the comment: The *** Tracing *** section [1] of Objects/lnotab_notes.txt in the cpython repository provides detailed explanations for when the line trace function is called. [1] https://github.com/python/cpython/blob/9d7b2c0909b78800d1376fd696f73824ea680463/Objects

[issue36544] cannot import hashlib when openssl is missing

Xavier de Gaye added the comment: Check that PR 12708 fixes the bug: Run the ubuntu:bpo-36544 image and enters bash as user pydev $ docker run -it ubuntu:bpo-36544 As user pydev, clone python and fetch PR 12708, build python and import hashlib: pydev@e4cfd6f74c2b:~$ git

[issue36544] cannot import hashlib when openssl is missing

Xavier de Gaye added the comment: Steps to reproduce (requires docker support, about 500 MB and only few minutes): 1. Create the file named 'Dockerfile' whose content is: FROM ubuntu RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get in

[issue36537] except statement block incorrectly assumes end of scope(?).

Xavier de Gaye added the comment: @Saim wrote > https://docs.python.org/3/reference/compound_stmts.html#the-try-statement says This is correct, the disassembly of foo.py below demonstrates that point: BEGIN_FINALLY at bytecode index 36 starts the implementation of the 'finally' cla

[issue36537] except statement block incorrectly assumes end of scope(?).

Xavier de Gaye added the comment: This is not a bug. On the first pdb session from the OP: True --Return-- > (5)()->None -> import pdb; pdb.set_trace() (Pdb) print("err" in locals()) False <-- BUG?? Pdb has stopped on a '--Return--' line event, so

[issue36146] Refactor setup.py

Change by Xavier de Gaye : -- pull_requests: +12633 ___ Python tracker <https://bugs.python.org/issue36146> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36544] cannot import hashlib when openssl is missing

Change by Xavier de Gaye : -- keywords: +patch pull_requests: +12632 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36544] cannot import hashlib when openssl is missing

Xavier de Gaye added the comment: Working on a PR -- ___ Python tracker <https://bugs.python.org/issue36544> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36544] cannot import hashlib when openssl is missing

Xavier de Gaye added the comment: Changeset 5ec33a1c25a586552751ca35c85ab7ecb6b06ec3 appends to the new detect_openssl_hashlib() method, the detection for the _sha256, _sha512, _md5, ... extension modules. These modules were detected unconditionnaly before this change and are not detected

[issue36544] cannot import hashlib when openssl is missing

New submission from Xavier de Gaye : Python is built natively in a docker container (based on ubuntu bionic) that lacks openssl. pydev@979e9e009b08:~/build/python-native$ ./python Python 3.8.0a3+ (heads/master-dirty:d6bf6f2, Apr 6 2019, 14:43:30) [GCC 7.3.0] on linux Type "help",

[issue36342] test_venv failure when executed by test_multiprocessing and the platform lacks a functional sem_open()

Change by Xavier de Gaye : -- keywords: +patch pull_requests: +12464 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36342> ___ ___ Py

[issue36342] test_venv failure when executed by test_multiprocessing and the platform lacks a functional sem_open()

Xavier de Gaye added the comment: Removing the bpo-35978 dependency as changeset 8bba81fd55873148c65b7d0e6a6effbd63048c76 that fixes bpo-35978 only skips test_multiprocessing when test_venv is run from a venv. -- dependencies: -test_venv fails in Travis with GCC

[issue35978] test_venv fails in Travis with GCC

Change by Xavier de Gaye : -- nosy: +xdegaye ___ Python tracker <https://bugs.python.org/issue35978> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36342] test_venv failure when the platform lacks a functional sem_open()

Xavier de Gaye added the comment: It is a test_venv issue related to bpo-32126 and also related to the other issues listed in bpo-32126. Changing the title as it is ambiguous indeed. check_output() in test_venv.py does not print the full stack trace as it is done by test_asyncio in bpo

[issue36361] generate correct pyconfig.h when cross-compiling

Change by Xavier de Gaye : -- keywords: +patch pull_requests: +12383 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36361] generate correct pyconfig.h when cross-compiling

New submission from Xavier de Gaye : 'configure' cache values are set to pessimistic defaults when cross-compiling. One of the most significant, ac_cv_computed_gotos, is set to 'no' in that case. When ac_cv_computed_gotos is set to 'yes' on platforms that support it, it brings a 15-20

[issue24565] the f_lineno getter is broken

Change by Xavier de Gaye : -- pull_requests: +12373 ___ Python tracker <https://bugs.python.org/issue24565> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36351] the ipv6type variable in configure.ac may be set incorrectly when cross-compiling

Change by Xavier de Gaye : -- keywords: +patch pull_requests: +12370 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36351] the ipv6type variable in configure.ac may be set incorrectly when cross-compiling

New submission from Xavier de Gaye : The tests that set the 'ipv6type' variable in configure.ac check the local file system and this may give incorrect values when cross-compiling. For example the /etc/netconfig file exists on Archlinux, and configure sets ipv6type=solaris when cross

[issue36214] AC_RUN_IFELSE macros not used as arguments of AC_CACHE_VAL et al

Change by Xavier de Gaye : -- keywords: +patch pull_requests: +12368 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36342] test_venv fails on Android with clang

Xavier de Gaye added the comment: Too hasty again, remembering now why I linked this failure with sem_open :-( Re-opening this issue as the test does fail because Android lacks a functioning sem_open implementation. And tagging this issue as a dependency of bpo-35978 as we should wait

[issue35066] Inconsistency between dangling '%' handling in time.strftime() and datetime.strftime()

Xavier de Gaye added the comment: The new test added by changeset 454b3d4ea246e8751534e105548d141ed7b0b032 fails on Android: == FAIL: test_strftime_trailing_percent (test.datetimetester.TestDate_Pure

[issue36342] test_venv fails on Android with clang

Xavier de Gaye added the comment: You are right, this is a duplicate of bpo-35978. Closing as duplicate. -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed title: test_multiprocessing fails on platforms lacking a functioning sem_open -> tes

[issue36342] test_multiprocessing fails on platforms lacking a functioning sem_open

New submission from Xavier de Gaye : test_multiprocessing fails on platforms lacking a functioning sem_open (Android for example) with: == ERROR: test_multiprocessing (test.test_venv.BasicTest

[issue36341] bind() on AF_UNIX socket may fail in tests run as non-root

Change by Xavier de Gaye : -- keywords: +patch pull_requests: +12354 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36341] bind() on AF_UNIX socket may fail in tests run as non-root

New submission from Xavier de Gaye : This happens on Android where a SELinux policy prevents a plain user to bind() a pathname AF_UNIX socket (abstract and unnamed sockets are not constrained by this policy). The errors are: test_asyncio

[issue35813] shared memory construct to avoid need for serialization between processes

Xavier de Gaye added the comment: After changeset e895de3e7f3cc2f7213b87621cfe9812ea4343f0, test_all fails on platforms that lack the _posixshmem extension module (Android for example): == FAIL: test_all (test.test___all__

[issue36214] AC_RUN_IFELSE macros not used as arguments of AC_CACHE_VAL et al

New submission from Xavier de Gaye : When the AC_RUN_IFELSE macro is used as the 'COMMANDS-TO-SET-IT' argument of the AC_CACHE_VAL or AC_CACHE_CHECK macros, it is possible to override the last argument of AC_RUN_IFELSE that is used when cross-compiling and set the variable with a cached

[issue36125] Cannot cross-compile to more featureful but same tune

Xavier de Gaye added the comment: Re-opening and setting the stage as 'needs patch': at least the cross-compilation should fail with a clear message when the cross-built libraries names and those of the native interpreter have the same suffix. > Assuming that you can rely on the loa

[issue36125] Cannot cross-compile to more featureful but same tune

Xavier de Gaye added the comment: The cross-compilation rely on the fact that the cross-compiled shared libraries names are constructed using the configure `--host=HOST-TYPE' command line parameter and therefore cannot be loaded by the native compiler that uses a different suffix for those

[issue36125] Cannot cross-compile to more featureful but same tune

Xavier de Gaye added the comment: @Ross > The intention appears to be that the sysconfig.py in the build is used. In > my case that directory is also full of shared libraries that Python happily > loads, and then fails. No, the intention is that the native python finds the sysc

[issue36145] android arm cross compilation fails, config issue

Xavier de Gaye added the comment: Obviously because you do not tell clang where to find those headers. -- ___ Python tracker <https://bugs.python.org/issue36

[issue36145] android arm cross compilation fails, config issue

Change by Xavier de Gaye : -- stage: -> needs patch ___ Python tracker <https://bugs.python.org/issue36145> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue36145] android arm cross compilation fails, config issue

Xavier de Gaye added the comment: There is a bug in the implementation of pymonotonic() in Python/pytime.c: The call to pytime_fromtimespec() is not encapsulated by an #ifdef HAVE_CLOCK_GETTIME. @muhzi It seems that your pyconfig.h is generated with configure failing to find the NDK

[issue36141] configure: error: could not find pthreads on your system during cross compilation

Xavier de Gaye added the comment: This is a different problem. Please create a new issue and attach pyconfig.h. -- ___ Python tracker <https://bugs.python.org/issue36

[issue36141] configure: error: could not find pthreads on your system during cross compilation

Xavier de Gaye added the comment: > The problem extends after the configuration. It's as if the android headers > are not visible to configure. All the macros are undefined in the pyconfig > file too btw. pyconfig.h is generated by configure from pyconfig.h.in. Please attach the n

[issue36141] configure: error: could not find pthreads on your system during cross compilation

Xavier de Gaye added the comment: What is the NDK version ? There is no Android pthread library. It is possible that the failure comes from the fact that the first configure test on pthread_create links with pthread and that the Android linker fails now instead of ignoring this error

[issue35997] ImportError: dlopen failed: cannot locate symbol "PyBool_Type"

Xavier de Gaye added the comment: It is not yet possible to cross-compile python extensions. The reason is that _init_posix() in Lib/sysconfig.py still reads the sysconfigdata module of the native compiler instead of the sysconfigdata of the cross-built one. See the patch in issue #28833

[issue35953] crosscompilation fails with clang on android

Xavier de Gaye added the comment: This problem has been fixed in python 3.7. Most of the changes made to fix the problems of cross-building python for android have been done on python 3.7. -- ___ Python tracker <https://bugs.python.

[issue35952] test.pythoninfo prints a stack trace and exits with 1 when the compiler does not exist

New submission from Xavier de Gaye : The call to subprocess.Popen() in collect_cc() of Lib/test/pythoninfo.py raises an exception when the compiler that has been used to build python is not present on the host running python. In that case pythoninfo prints a stack trace and exits

[issue34814] makesetup: must link C extensions to libpython when compiled in shared mode

Change by Xavier de Gaye : -- nosy: -xdegaye ___ Python tracker <https://bugs.python.org/issue34814> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34814] makesetup: must link C extensions to libpython when compiled in shared mode

Change by Xavier de Gaye : -- Removed message: https://bugs.python.org/msg326509 ___ Python tracker <https://bugs.python.org/issue34814> ___ ___ Python-bug

[issue34814] makesetup: must link C extensions to libpython when compiled in shared mode

Xavier de Gaye added the comment: > Downstream (RHEL) issue: > https://bugzilla.redhat.com/show_bug.cgi?id=1585201 Not sure that this is a bug. As Petr Viktorin points out in Comment #4, the reproducer is not expected to work because of the semantics of RTLD_LOCAL. So the current bpo

[issue33757] Failed separate test_pdb_next_command_in_generator_for_loop in test_pdb

Change by Xavier de Gaye : -- keywords: +patch pull_requests: +7195 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33757> ___ ___ Py

[issue33757] Failed separate test_pdb_next_command_in_generator_for_loop in test_pdb

Xavier de Gaye added the comment: This is fixed with: diff --git a/Lib/test/test_pdb.py b/Lib/test/test_pdb.py index 4f9d28afd3..7b3624fb99 100644 --- a/Lib/test/test_pdb.py +++ b/Lib/test/test_pdb.py @@ -1045,7 +1045,7 @@ def test_pdb_next_command_in_generator_for_loop

[issue13886] readline-related test_builtin failure

Xavier de Gaye added the comment: All checks have passed on PR 7133, even on macOs, and the PR is ready to be reviewed :-) -- ___ Python tracker <https://bugs.python.org/issue13

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Xavier de Gaye <xdeg...@gmail.com> added the comment: > There are still quite a few similar warnings on git-master. Do they indicate > the same problem or should I open new issues? This is the same issue, the warning line ends with [-Wcast-f

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Xavier de Gaye <xdeg...@gmail.com> added the comment: > Pedantically the correct way is to cast to a function pointer with no > prototype (empty parentheses) Thanks for raising this point Antti. This is hinted at by the gcc 8 documentation on -Wcast-function-type: "The f

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Xavier de Gaye <xdeg...@gmail.com> added the comment: > But the problem is that additional flags can be used, e.g. METH_CLASS. Right, https://docs.python.org/3/c-api/structures.html says: "The individual flags indicate either a calling convention or a binding convention". Th

[issue13886] readline-related test_builtin failure

Xavier de Gaye <xdeg...@gmail.com> added the comment: As stated in msg285810, issue 28180 removed the need for an Android workaround. After checking this point on the Android API 24 emulator with the current master branch, I have opened PR 7133 which is Martin's input-readline.v3

[issue13886] readline-related test_builtin failure

Change by Xavier de Gaye <xdeg...@gmail.com>: -- pull_requests: +6767 ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue13886> ___ _

[issue33012] Invalid function cast warnings with gcc 8 for METH_NOARGS

Xavier de Gaye <xdeg...@gmail.com> added the comment: I propose to enhance the changes made by PR 6748 and PR 6749 so that gcc 8 triggers a warning when the function type of a PyMethodDef element does not match its flags by using a macro (see below) that casts the function

[issue32392] subprocess.run documentation does not have **kwargs

Xavier de Gaye <xdeg...@gmail.com> added the comment: > Let's add 'env=None' to the signature of subprocess.run(): +1 -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

[issue13044] pdb throws AttributeError at end of debugging session

Xavier de Gaye <xdeg...@gmail.com> added the comment: See also issue 33458 that deals with the same problem when pdb is run as 'python -m pdb some_main.py' instead of by inserting a breakpoint with 'pdb.set_trace()'. -- ___ Python tracke

[issue33458] pdb.run() does not trace destructors of __main__

Xavier de Gaye <xdeg...@gmail.com> added the comment: The following patch fixes the problem when applied applied on top of PR 6730: diff --git a/Lib/bdb.py b/Lib/bdb.py index c6a10359ac..07231ec588 100644 --- a/Lib/bdb.py +++ b/Lib/bdb.py @@ -582,7 +582,7 @@ class Bdb:

[issue33458] pdb.run() does not trace destructors of __main__

New submission from Xavier de Gaye <xdeg...@gmail.com>: This issue is a companion to issue 13044. Running with Python 3.6.5 the following code fails with NameError: 1 class C: 2 def __del__(self): 3 print('deleted') 4 5 c = C() 6 x = 1 $ python -m pdb bar.py > .

[issue13044] pdb throws AttributeError at end of debugging session

Xavier de Gaye <xdeg...@gmail.com> added the comment: Actually the segfault can be avoided by running the garbage collection before _PyState_ClearModules() in PyImport_Cleanup() and one can trace the C destructor with the attached patch global_destructors.diff applied on top of PR

[issue13044] pdb throws AttributeError at end of debugging session

Change by Xavier de Gaye <xdeg...@gmail.com>: Added file: https://bugs.python.org/file47578/lazy_import.diff ___ Python tracker <rep...@bugs.python.org> <https://bugs.python

[issue13044] pdb throws AttributeError at end of debugging session

Change by Xavier de Gaye <xdeg...@gmail.com>: Added file: https://bugs.python.org/file47579/gdb_backtrace.txt ___ Python tracker <rep...@bugs.python.org> <https://bugs.python

[issue13044] pdb throws AttributeError at end of debugging session

Xavier de Gaye <xdeg...@gmail.com> added the comment: Nosying Serhiy as this post attempts to answer one of the questions raised in msg315588 in issue 33328: > Is it good that the debugger is enabled at the shutdown stage? This post has four different sections showing that the s

[issue16653] reference kept in f_locals prevents the tracing/profiling of a destructor

Xavier de Gaye <xdeg...@gmail.com> added the comment: Closing as a duplicate of issue 33446 which has a wider scope and a PR. -- resolution: -> duplicate stage: -> resolved status: open -> closed ___ Python tracker <rep...@bugs.

[issue33446] destructors of local variables are not traced

Xavier de Gaye <xdeg...@gmail.com> added the comment: In both cases the destructor cannot be traced because it is invoked from functions called from [1] call_trace() where tracing is disabled: Case local variable 'a': On line 12, just before executing this line with a pdb step c

[issue33446] destructors of local variables are not traced

Change by Xavier de Gaye <xdeg...@gmail.com>: -- keywords: +patch pull_requests: +6422 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

[issue33446] destructors of local variables are not traced

New submission from Xavier de Gaye <xdeg...@gmail.com>: In the following code, the destructors of objects referenced by the 'a' and 'b' local variables are not traced by the 'step' command of pdb. 1 class C: 2 def __init__(self, name): 3 self.name = name 4 5 def _

<    1   2   3   4   5   6   7   8   9   10   >