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

2020-12-08 Thread STINNER Victor


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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42587] test_buffer fails on Python built with GCC 11

2020-12-08 Thread STINNER Victor

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2020-12-08 Thread STINNER Victor


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 exit status
make[3]: *** [Makefile:578: python] Error 1
make[3]: *** Waiting for unfinished jobs

Is it another GCC 11 bug when using LTO and/or PGO?

--
components: Build
messages: 382718
nosy: vstinner
priority: normal
severity: normal
status: open
title: aarch64 Fedora Rawhide LTO + PGO 3.8 fails to build Python: /usr/bin/ld: 
error adding symbols: bad value
versions: Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42561] better error reporting in ast

2020-12-08 Thread Batuhan Taskaya


Batuhan Taskaya  added the comment:

This is a duplicate of issue 28964

--
nosy: +BTaskaya

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42561] better error reporting in ast

2020-12-08 Thread Batuhan Taskaya


Change by Batuhan Taskaya :


--
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue42572] Better path handling with argparse

2020-12-08 Thread Xavier Morel


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 is rather easy to bring your own, but OP's expectation is that 
paths input is common enough (especially in smaller standalone scripts I would 
expect) that having a helper in a standard library would be... helpful.

--
nosy: +xmorel

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



<    1   2