Mailman 3 June 2012 - docs

[issue12982] Document that importing .pyo files needs python -O
by Éric Araujo June 12, 2012

June 12, 2012

Changes by Éric Araujo <merwok(a)netwok.org>: ---------- title: .pyo file can't be imported unless -O is given -> Document that importing .pyo files needs python -O _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue12982] .pyo file can't be imported unless -O is given
by Éric Araujo June 12, 2012

June 12, 2012

Éric Araujo <merwok(a)netwok.org> added the comment: Michael, I don’t think your proposed change would be considered favorably: importing .pyc or .pyo is well defined for CPython and the -O switch is really required for .pyo. However you may be able to import them anyway without any change to Python if you write a custom importer (more info in PEP 302 and the import docs) which reuses the low-level imp module to find and load .pyo files. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue12982] .pyo file can't be imported unless -O is given
by Michael Herrmann June 12, 2012

June 12, 2012

Michael Herrmann <mherrmann.at(a)gmail.com> added the comment: Hi, I need to use a third-party library that ships as a mixture of .pyc and .pyo files. I found it a little surprising and inconvenient that I have to set the -O flag just to read .pyo files. I don't mind whether .pyc or .pyo files are being created during compilation, I just want to be able to read from both .pyc and .pyo files without having to use the -O flag. Can somebody fix this? I unfortunately have absolutely no clue how. Thanks! ---------- components: +Interpreter Core -Documentation nosy: +mherrmann.at _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue7699] strptime, strftime documentation
by R. David Murray June 10, 2012

June 10, 2012

R. David Murray <rdmurray(a)bitdance.com> added the comment: This was applied by Georg in SVN revision r77561 on 2010-01-17. ---------- nosy: +r.david.murray resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue7699> _______________________________________

1 0

[issue14968] Section "Inplace Operators" of :mod:`operator` should be a subsection
by Lars Buitinck June 10, 2012

June 10, 2012

New submission from Lars Buitinck <L.J.Buitinck(a)uva.nl>: The section "Inplace Operators" of the module docs for operator now show up in TOC at http://docs.python.org/dev/library/. I don't think that's intended as it does not describe a separate module. ---------- assignee: docs@python components: Documentation files: operator-module-docs.patch keywords: patch messages: 161996 nosy: docs@python, larsmans priority: normal severity: normal status: open title: Section "Inplace Operators" of :mod:`operator` should be a subsection type: enhancement versions: Python 3.3 Added file: http://bugs.python.org/file25772/operator-module-docs.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14968> _______________________________________

4 4

[issue14680] pydoc with -w option does not work for a lot of help topics
by Gregor June 10, 2012

June 10, 2012

New submission from Gregor <gregor.hochschild(a)gmx.de>: pydoc with pydoc with -w option (to write html files) does not work for a lot of help topics (e.g. EXPRESSIONS, FORMATTING, TUPLELITERALS, def, if, else...) If you look at the source you can see that when using the switch '-w' (http://hg.python.org/cpython/file/2.7/Lib/pydoc.py#l2311) pydoc uses the function writedoc, otherwise to the class Helper (http://hg.python.org/cpython/file/2.7/Lib/pydoc.py#l2325). In the Helper-class EXPRESSIONS is defined under line 1666 (http://hg.python.org/cpython/file/2.7/Lib/pydoc.py#l1666). The function writedoc does not utilize this nor does it use the Helper class. For dicussion see: http://stackoverflow.com/a/10333615/1318686 Example: pydoc EXPRESSIONS works perfectly fine but pydoc -w EXPRESSIONS does not. ---------- assignee: docs@python components: Documentation messages: 159428 nosy: docs@python, gregor.hoch priority: normal severity: normal status: open title: pydoc with -w option does not work for a lot of help topics versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14680> _______________________________________

2 1

[issue14971] (unittest) loadTestsFromName does not work on method with a decorator
by Michael Foord June 9, 2012

June 9, 2012

Michael Foord <michael(a)voidspace.org.uk> added the comment: Patch looks great - thanks David. ---------- assignee: docs@python -> michael.foord _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14971> _______________________________________

1 0

[issue1040439] Missing documentation on how to link with libpython
by Eli Bendersky June 8, 2012

June 8, 2012

Changes by Eli Bendersky <eliben(a)gmail.com>: ---------- nosy: -eli.bendersky _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue1040439> _______________________________________

1 0

[issue14006] Improve the documentation of xml.etree.ElementTree
by Eli Bendersky June 8, 2012

June 8, 2012

New submission from Eli Bendersky <eliben(a)gmail.com>: The documentation of xml.etree.ElementTree has to be improved. The first, very obvious step, would be to start the documentation page with a general overview of the module + some simple examples. The current opening section makes no sense for this module. ---------- assignee: docs@python components: Documentation keywords: easy messages: 153318 nosy: docs@python, eli.bendersky, eric.araujo, ezio.melotti, flox, scoder priority: normal severity: normal status: open title: Improve the documentation of xml.etree.ElementTree type: enhancement versions: Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14006> _______________________________________

9 16

[issue8652] Minor improvements to the "Handling Exceptions" part of the tutorial
by Marien Zwart June 8, 2012

June 8, 2012

New submission from Marien Zwart <m_zwart(a)123mail.org>: Based on questions asked on freenode's #python by people reading the tutorial I would like to suggest two improvements to http://docs.python.org/tutorial/errors.html#handling-exceptions : - Mention the older "except SomeException, e:" syntax too, not just "except SomeException as e:". I have had people ask me to help them upgrade to a newer python because they thought their version of python did not support catching exception instances (their distro python being 2.5). A big fat warning that they're reading the Python 2.6 tutorial (with links to older tutorials) may also work. - Mention "except IOError as e" before mentioning "except IOError as (errno, strerror):". The latter is an advanced and relatively unusual trick, combining regular exception catching and unpacking. Those two concepts need to be explained before the combination is. I have had people ask me how to do "except KeyError as (key, insert_something_here):" because they thought they *always* needed those parens there. (perhaps just not mentioning unpacking here at all, using "except IOError as e:" and then using e.errno would make more sense, especially since "except IOError as (errno, strerror):" is a SyntaxError in python 3 and up (because of the unpacking) and python 2.5.x and down (because of the "as")...) I can try to write a patch to the documentation if you like. ---------- assignee: docs@python components: Documentation messages: 105218 nosy: docs@python, marienz priority: normal severity: normal status: open title: Minor improvements to the "Handling Exceptions" part of the tutorial _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8652> _______________________________________

4 6