Thermi added the comment:
1) True. That'd mean such functionality would not be usable by such a
workaround though.
2) ANY setting has a default value. The output in the --help message has to, if
any defaults at all are shown, be the same as the actual default values.
Storing the de
Thermi added the comment:
Raymond, then you can't show the defaults in the help message.
--
___
Python tracker
<https://bugs.python.org/issue44748>
___
___
Thermi added the comment:
joker, that is a different issue from the one described here. Please open your
own.
--
___
Python tracker
<https://bugs.python.org/issue44
New submission from Thermi :
It'd be great if as part of the namespace returned by
argparse.ArgumentParser.parse_args(), there was a bool indicating if a specific
argument was encountered.
That could then be used to implement the following behaviour:
With a config file loaded as part o
Thermi added the comment:
PKGBUILD I use to build the python package I need for debugging on Arch.
Only changes to it are the addition of the 3 configure flags mentioned in the
title.
Other than that, it should work fine.
I built the package previously without those changes and that worked
New submission from Thermi :
--
Ran 210 tests in 0.950s
OK (skipped=26)
== Tests result: FAILURE ==
412 tests OK.
1 test failed:
test_posix
10 tests skipped:
test_devpoll test_gdb test_kqueue test_msilib
New submission from Thermi :
With Python 3.6.4 on Arch Linux, on three different hosts (one Skylake CPU, one
i7-3820, one Xeon E5-2680, all running Arch Linux with the same Python
version), the Python 3 interpreter behaves erratically in a script of mine.
The following symptoms occur:
1
