[issue43877] Logging Cookbook ambiguity
Gene Ratzlaff added the comment: Agreed, but only to the limits of the buffer - that's what I was getting at when I suggested that limitations should be explained. -- ___ Python tracker <https://bugs.python.org/issue43877> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43877] Logging Cookbook ambiguity
New submission from Gene Ratzlaff : In the section titled "Logging to a single file from multiple processes" I am puzzled by the second example, as follows: The first example has the listener/logger is in a separate >process< and the listener/logger process is (as I would anticipate) started >before< the worker/sender processes. In the 2nd example, the listener/logger is in a separate >thread< and the listener/logger thread is (oddly) started >after< the worker/sender processes. Please correct it, or explain in the Cookbook what is OK about doing it that way, and if it is OK, are there limitations to doing it that way? -- assignee: docs@python components: Documentation messages: 391267 nosy: bluebloodpole, docs@python priority: normal severity: normal status: open title: Logging Cookbook ambiguity type: enhancement ___ Python tracker <https://bugs.python.org/issue43877> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6879] misstatement in example explanation using raise
New submission from Gene Ratzlaff gener...@gmail.com:
v2.6.2 Python Tutorial
http://docs.python.org/tutorial/errors.html#raising-exceptions
Section 8. Errors and Exceptions
8.4. Raising Exceptions
It appears that in the example, the original may have been:
raise(NameError('HiThere')) and was then changed to
raise NameError('HiThere') but the explanation was not changed
accordingly. The current state and my suggested change are found below,
respectively:
Currently:
raise NameError('HiThere')
Traceback (most recent call last):
File stdin, line 1, in ?
NameError: HiThere
The first argument to raise names the exception to be raised. The
optional second argument specifies the exception’s argument.
Alternatively, the above could be written as
raise NameError('HiThere'). Either form works fine, but there seems to
be a growing stylistic preference for the latter.
Suggest change to:
raise NameError('HiThere')
Traceback (most recent call last):
File stdin, line 1, in ?
NameError: HiThere
The first argument to raise names the exception to be raised. The
optional second argument specifies the exception’s argument.
Alternatively, the above could be written as
raise(NameError('HiThere')). Either form works fine, but there seems to
be a growing stylistic preference for the former.
--
assignee: georg.brandl
components: Documentation
messages: 92501
nosy: bluebloodpole, georg.brandl
severity: normal
status: open
title: misstatement in example explanation using raise
versions: Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6879
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6880] class needs forward reference
New submission from Gene Ratzlaff gener...@gmail.com: http://docs.python.org/tutorial/errors.html#user-defined-exceptions class mechanism used in 8.5 before classes are explained in chapter 9. Suggest first use of word class be a forward link to 9. Classes: http://docs.python.org/tutorial/classes.html#classes -- assignee: georg.brandl components: Documentation messages: 92502 nosy: bluebloodpole, georg.brandl severity: normal status: open title: class needs forward reference type: feature request versions: Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6880 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
