[issue42587] memoryview rely on _Bool undefined behavior (test_buffer fails on Python built with GCC 11)

Change by STINNER Victor : -- title: test_buffer fails on Python built with GCC 11 -> memoryview rely on _Bool undefined behavior (test_buffer fails on Python built with GCC 11) ___ Python tracker

[issue42587] test_buffer fails on Python built with GCC 11

STINNER Victor added the comment: See also: Behavior of struct “?” format (native _Bool) https://discuss.python.org/t/behavior-of-struct-format-native-bool/3774 -- ___ Python tracker

[issue42596] aarch64 Fedora Rawhide LTO + PGO 3.8 fails to build Python: /usr/bin/ld: error adding symbols: bad value

New submission from STINNER Victor : aarch64 Fedora Rawhide LTO + PGO 3.8: https://buildbot.python.org/all/#/builders/528/builds/243 /usr/bin/ld: /lib64/libgcc_s.so.1: .gnu.version_r invalid entry /usr/bin/ld: /lib64/libgcc_s.so.1: error adding symbols: bad value collect2: error: ld returned 1

[issue42561] better error reporting in ast

Batuhan Taskaya added the comment: This is a duplicate of issue 28964 -- nosy: +BTaskaya ___ Python tracker ___ ___

[issue42561] better error reporting in ast

Change by Batuhan Taskaya : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42572] Better path handling with argparse

Xavier Morel added the comment: > What exactly do you do with a path argument? Because they mention "convert[ing] the string to a path", I would expect an output of `pathlib.Path`, optionally checked for existence / non-existence and / or kind (file, directory, symlink, ...). Obviously it

<    1   2