New submission from Philip Rowlands :
Went looking for os.pause() but found nothing in the docs, bpo, or Google.
https://man7.org/linux/man-pages/man2/pause.2.html
Obviously not a popular syscall, but I have a use case for it.
--
components: Library (Lib)
messages: 413554
nosy
Philip Rowlands added the comment:
Status as of 3.9.0a1:
==
test.py above appears fixed, i.e. reasonable error message.
$ ./python test.py
File "/home/bob/pybug/Python-3.9.0a1/test.py", line 2
hello = f"{world)}"
^
SyntaxError: f-string: unmatched &#
Philip Rowlands added the comment:
I went digging through the archives, made more interesting as elementtree was
imported into the standard library.
AFAICT, the FutureWarning for __bool__ (or __nonzero__ in py2) appeared circa
2007-06 in version 1.3a2:
http://svn.effbot.org/public/tags
Philip Rowlands added the comment:
It's easier to justify a change in behaviour if the warning is emitted. With no
legacy concerns, I would be happy for bool() to change, but I'm not the one who
would receive the grumbly tickets.
How about emitting the warning in the next rel
New submission from Philip Rowlands :
Steps to reproduce:
$ python3.7
Python 3.7.2 (default, May 13 2019, 13:52:56)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import xml.etree.Elemen
New submission from Philip Rowlands :
Because error() mentions standard error and exit() does not, I assumed exit()
did not use stderr, but it does.
Please mention standard error in the description of exit().
Relevant code at:
https://github.com/python/cpython/blob/3.7/Lib/argparse.py#L2482
Philip Rowlands added the comment:
Considering the semantics a little more, "cont 99" could be equivalent to
tbreak 99
cont
perhaps with an implicit clear on SIGINT.
This is similar in the simple case to "until 99", except "until" stops on frame
boundaries, re
Philip Rowlands added the comment:
Thanks for the edit. I did try a PR but was defeated by build/doc tool's recent
version requirements (and didn't want to send untested changes, however minor).
The reason for getting rid of "unset" is the confusion of "state&
Philip Rowlands added the comment:
How about
- If tempdir is unset or None at any call to
+ If tempdir is None (the default) at any call to
This avoids headaches over the meaning of "unset", and accurately reflects the
code at:
https://github.com/python/cpython/blob/3.6/Lib/tempfi
New submission from Philip Rowlands :
Quoting https://docs.python.org/3/library/tempfile.html
"""
tempfile.tempdir
When set to a value other than None, this variable defines the default value
for the dir argument to the functions defined in this module.
If tempdir is unset or N
New submission from Philip Rowlands :
Please extend pdb's continue to support an optional argument, identical to
break.
When debugging I frequently want to quickly run to a certain line number then
break. Rather than break / continue / clear (or tbreak / continue), it would be
handy to
11 matches
Mail list logo
