[issue14851] Python-2.6.8 install fails due to missing files
New submission from gene : Hi, I've downloaded both source versions of Python for Mac 2.6.8 and have unziped them with Mac GUI or gunzip but all attempts fail due to build not finding files. First missing file is pyconfig.h which appears to be named pyconfig.h.in. When I remove the .in then next missing object is Modules/Setup. I don't see a fix for this. I'm installing this in Mac OS X 10.6.8. Any ideas? Gene Sources: http://www.python.org/download/releases/2.6.8/ -- components: Installation messages: 161060 nosy: spacebuoy priority: normal severity: normal status: open title: Python-2.6.8 install fails due to missing files type: behavior versions: Python 2.6 ___ Python tracker <http://bugs.python.org/issue14851> ___ ___ Python-bugs-list mailing list Unsubscribe: http://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
[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
[issue44264] Add descriptive error message when environment variable not detected
New submission from David Gene :
Using os.environ[KEY] with a non-existent environment variable key only gives a
simple KeyError, which may be fine for a developer to understand, but if a user
of a Python program were to come across it, it may not indicate what they
needed to do to avoid the crash. I would raising the keyError with a message
such as "Environment variable '{}' not set".
--
messages: 394735
nosy: astrosticks
priority: normal
pull_requests: 25047
severity: normal
status: open
title: Add descriptive error message when environment variable not detected
type: enhancement
versions: Python 3.11
___
Python tracker
<https://bugs.python.org/issue44264>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40563] Support pathlike objects on dbm/shelve
Gene Wood added the comment: @DahlitzFlorian it looks like a PR was submitted August of last year : https://github.com/python/cpython/pull/21849 -- nosy: +gene_wood ___ Python tracker <https://bugs.python.org/issue40563> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17088] ElementTree incorrectly refuses to write attributes without namespaces when default_namespace is used
Gene Wood added the comment:
One workaround to this is described here :
http://stackoverflow.com/a/4999510/168874
It involves prefixing all of the elements with the namespace like this :
from xml.etree import ElementTree as ET
# build a tree structure
root = ET.Element("{http://www.company.com}STUFF";)
body = ET.SubElement(root, "{http://www.company.com}MORE_STUFF";)
body.text = "STUFF EVERYWHERE!"
# wrap it in an ElementTree instance, and save as XML
tree = ET.ElementTree(root)
tree.write("page.xml",
xml_declaration=True,encoding='utf-8',
method="xml",default_namespace='http://www.company.com')
--
nosy: +gene_wood
___
Python tracker
<http://bugs.python.org/issue17088>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20805] Error in 3.3 Tutorial
New submission from Gene Anderson: In the tutorial for Python 3.3 the content for 9.3.4 Method Objects seems to have an error. In the following lines: xf = x.f while True: print(xf()) ... it seems to me that based on the x object's method f(), the command should be print(x.f()) At least it did when I tried to run it without the endless loop. I'm pretty new at this Python stuff, though, so I could be wrong. -- messages: 212421 nosy: Andesheng priority: normal severity: normal status: open title: Error in 3.3 Tutorial versions: Python 3.3 ___ Python tracker <http://bugs.python.org/issue20805> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20805] Error in 3.3 Tutorial
Gene Anderson added the comment: I failed to mention that the associated web address for the documentation is: http://docs.python.org/3.3/tutorial/classes.html#method-objects -- ___ Python tracker <http://bugs.python.org/issue20805> ___ ___ 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 :
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 "", 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 "", 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
<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 : 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 <http://bugs.python.org/issue6880> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
