New submission from Karl Richter:
The docstring of `sorted` doesn't explain what can be passed to the `cmp` and
`key` argument of `sorted`.
--
assignee: docs@python
components: Documentation
messages: 257505
nosy: docs@python, krichter
priority: normal
severity: normal
status: open
New submission from Karl Richter:
`./configure` both prints `checking for g++... no` and
WARNING:
By default, distutils will build C++ extension modules with "g++".
If this is not intended, then set CXX on the configure command line.
if `/usr/bin/g++`
Karl Richter added the comment:
Please also explain how to deal with process replacement in child processes
(assuming that
http://stackoverflow.com/questions/34059576/how-to-register-a-signal-handler-for-a-subprocess/34065587#34065587
is correct
New submission from Karl Richter:
The [documentation of
subprocess](https://docs.python.org/3.6/library/subprocess.html) doesn't
contain a substantial statement how signals are handled which are send to the
python interpreter. After reading the referenced docs it should be clear
* whether
New submission from Karl Richter:
`gcc` 4.9 is more restictive and recognizes that the empty definition of the
`REQN` macro doesn't use some variables. It's more suitable to wrap the usage
of the macro in the same preprocessor conditionals like the macro definition.
experienced
Karl Richter added the comment:
It's a fatal warning of `gcc 4.9.2`, not an error (my bad) for `int i;` in
`Parser/pgen.c` line 227. It might be ignored as well, but I think my approach
is more elegant and deals with issues sooner than later
New submission from Karl Richter:
I experience the error in the title exclusive when invoking `hg clone` (e.g.
`hg clone https://bitbucket.org/Coin3D/coin` or `hg clone
http://hg.netbeans.org/main-golden/ netbeans-main-golden`) when the target
directory is on a cifs mount.
`gdb` backtrace
Changes by Karl Richter krichter...@aol.de:
--
components: Build
nosy: krichter
priority: normal
severity: normal
status: open
title: Makefile in tarball don't provide make uninstall target
versions: Python 2.7
___
Python tracker rep
New submission from Karl Richter:
The `Formatter` section of the `logging` module at
https://docs.python.org/2/library/logging.html#formatter-objects reads like
it's sufficient to create an instance of `Formatter` with default arguments
(and set it as formatter of the `Handler` of a `Logger
Karl Richter added the comment:
I suspect the complaint might be about the lack of doc string
Exactly. It'd be helpful to figure out the return value and the means of the
function arguments in a more compact form than the referenced website docs and
to have it available in the interpreter
Changes by Karl Richter krichter...@aol.de:
--
assignee: docs@python
components: Documentation
nosy: docs@python, krichter
priority: normal
severity: normal
status: open
title: document urllib.urlretrieve
versions: Python 2.7
___
Python tracker rep
Karl Richter added the comment:
For example, it should be clear why `shelve.open(tempfile.mkstemp()[1])` fails
with the mentioned exception and `shelve.open(/tmp/bla)` fails. I still
haven't figured out the constraints to create a working `shelve.Shelve` at all.
It should be clear why
Karl Richter added the comment:
After checking the code, I think that it'd make more sense to document
`whichdb.py`. It needs to be enhanced with references to criteria for the
determination of the database type. Currently there're only function comments
and the fact that some variables
Karl Richter added the comment:
Sorry, I mean
#!/usr/bin/python
import threading
def debugging():
def __a_thread__():
print(2)
a_thread = threading.Thread(target=__a_thread__)
a_thread.start()
a_thread.join()
print(1
Karl Richter added the comment:
My initial description was imprecise. Clearification: The fact that in
#!/usr/bin/python
import threading
def debugging():
def __a_thread__():
print(2)
a_thread = threading.Thread(target=__a_thread__)
print(1
Karl Richter added the comment:
That's nice, thanks. Considering your last comment, some points
* If the issue can't go into the error message, than the essence of the
discussion here should go into the docs (in 0.5 to 1.5 sentences).
* It'd be nice if it was clear from the error message
Karl Richter added the comment:
Then, let the error message say You are opening a just-created empty file.
The db type of the file cannot, therefore, be determined. which is much
clearer than anydbm.error: db type could not be determined which sounds like
a generic fallback error message
New submission from Karl Richter:
`shelve.open(tempfile.mkstemp()[1])` fails with error anydbm.error: db type
could not be determined which is not explainable with the docs. Traceback is
Traceback (most recent call last):
File ./cudaminer_param_checker.py, line 720, in module
Karl Richter added the comment:
EDIT 1: other examples, e.g.
import os
import shelve
curdir = os.path.dirname(__file__)
passwords = shelve.open(os.path.join(curdir, 'password_db'))
work, so there's need for usable error messages
New submission from Karl Richter:
Due to the fact that `pdb` currently simply ignores breakpoints which are set
and hit in another than the main thread the docs need to contain a statement on
behavior in a multithreaded environment.
--
components: Library (Lib)
messages: 233409
nosy
New submission from Karl Richter:
reproduction (on Ubuntu 14.04 amd64 with lxc 1.0.4) (with python 2.7.6 and
3.4.0)
# as root/with privileges
lxc-create -n ubuntu-trusty-amd64 -t ubuntu -- --arch amd64 --release trusty
lxc-stop -n ubuntu-trusty-amd64 # assert container isn't
New submission from Karl Richter:
Although the section
https://docs.python.org/2/library/multiprocessing.html#process-and-exceptions
(of the multiprocessing module documentation) is titled ... and exceptions it
doesn't say anything about exceptions. I assume that it behaves like the thread
New submission from Karl Richter:
It would be useful to have a short statement in the docs
(https://docs.python.org/2/tutorial/datastructures.html#list-comprehensions)
that the expression in a list comprehension isn't put into a block, but
evaluated against the same block where it is located
Karl Richter added the comment:
@paul.j3 That's interesting [1]. Documenting argparse.register seems crucial to
me (- reopen or file a new request?).
After dealing more with the very sophisticated and complex functionality of
argparse I'm sure that this is the only use case where
Karl Richter added the comment:
That's a pity, I still think it's confusing. Thanks for your feedback!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21208
New submission from Karl Richter:
As arguments with type bool are the only ones whose values can be manipulated
without passing an option to the argument on CLI, the default behavior for
those should be changed from ignoring options to failing when options are
specified. Consider
Karl Richter added the comment:
I've been mistaken about the behavior if no argument is specified (then the
argument value is None), so this is a bug!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21208
New submission from Karl Richter:
The explanation of namespaces in section 9.2 in documentation
(http://docs.python.org/3/tutorial/classes.html#python-scopes-and-namespaces)
is just so complicated without (at least one tiny) example. The example would
ease the comprehension of the section
28 matches
Mail list logo
