New submission from Steven Bethard <steven.bethard(a)gmail.com>:
[From http://code.google.com/p/argparse/issues/detail?id=61]
It should be documented clearly that only the arguments present on the parent parser at the time ArgumentParser is called will be included in the parser.
>>> parent = argparse.ArgumentParser(add_help=False)
>>> child = argparse.ArgumentParser(parents=[parent])
>>> parent.add_argument('--foo', action='store_true')
>>> child.parse_args(['--foo'])
usage: [-h]
: error: unrecognized arguments: --foo
----------
assignee: docs@python
components: Documentation
messages: 111306
nosy: bethard, docs@python
priority: normal
severity: normal
status: open
title: Document that argparse "parents" must be fully declared before children
versions: Python 2.7, Python 3.2, Python 3.3
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue9343>
_______________________________________
New submission from Alexander Belopolsky <belopolsky(a)users.sourceforge.net>:
This bikeshed have been repainted several times already, but here is a true story.
Cast:
Me = myself
Novice = a 14-year-old boy
Laptop = a MacBook Air
Novice: How do i exit [from python prompt]?
Me: What's your best guess?
Novice: [typing] exit [pressing Enter]
Laptop: Use exit() or Ctrl-D (i.e. EOF) to exit
Novice: [typing] Ctrl...
Me: OMG, you don't know what Ctrl-D means? Look for the Ctrl key.
Novice: There is no such key.
--- curtains ---
I suggest changing
Use exit() or Ctrl-D (i.e. EOF) to exit
to
Type exit() or quit() and press the Enter key to exit
or
Type exit() or quit() and press Enter to exit
or just
Use exit() to exit
My theory is that someone who knows what EOF is, will probably already know how to exit from common terminal oriented programs and Ctrl-D is not universally bound to EOF.
TOOWTDI: two ways to exit is more than enough to teach a novice.
----------
assignee: docs@python
components: Documentation
keywords: easy
messages: 111374
nosy: belopolsky, docs@python
priority: normal
severity: normal
status: open
title: Make exit/quit hint more novice friendly
type: feature request
versions: Python 3.2
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue9362>
_______________________________________
New submission from Terry J. Reedy <tjreedy(a)udel.edu>:
As reported on python-list by Alan G Isaac,
Lib Ref 6.1.3.1. Format Specification Mini-Language, for instance
http://docs.python.org/dev/py3k/library/string.html#formatstrings
wrongly says in the alignment section
"'<' Forces the field to be left-aligned within the available space (This is the default.)"
This latter, of course, is not true for number fields.
"(This is the default.)" could be replaced by "(the string default)."
(in any case, the '.' should be outside the () unless one is added after 'space' before '(') and "(the number default)" added to the next line. Or instead the issue of defaults could be addressed in the text below the table.
I am assuming that this issue affects 2.6/7.
----------
assignee: docs@python
components: Documentation
messages: 105536
nosy: docs@python, tjreedy
priority: normal
severity: normal
status: open
title: Doc: left alignment is not the default for numbers
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue8691>
_______________________________________
New submission from Nick Coghlan <ncoghlan(a)gmail.com>:
Brett updated the docs for the test package to (correctly) point out that it is our internal testing package and isn't subject to the same stringent backwards compatibility rules as the rest of the standard library.
A "see also" link pointing readers that have landed there over to the unittest module for their testing infrastructure needs would be a friendly thing to include.
----------
assignee: docs@python
components: Documentation
keywords: easy
messages: 111450
nosy: docs@python, ncoghlan
priority: normal
severity: normal
stage: needs patch
status: open
title: Add reader redirect from test package docs to unittest module
versions: Python 2.7, Python 3.2
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue9370>
_______________________________________
New submission from Alexander Belopolsky <belopolsky(a)users.sourceforge.net>:
With python started at the root of the source tree and TZ=US/Eastern in the environment,
>>> exec(open('Doc/includes/tzinfo-examples.py').read())
>>> import os
>>> os.environ['TZ']
'US/Eastern'
>>> from datetime import *
>>> x = datetime(2010, 11, 7, 5, tzinfo=timezone.utc)
>>> print(x, x.astimezone(Local), x.astimezone(Eastern))
2010-11-07 05:00:00+00:00 2010-11-07 01:00:00-04:00 2010-11-07 01:00:00-05:00
>>> x.astimezone(Local).dst() == x.astimezone(Eastern).dst()
False
Note that according to my understanding of the long comment at the end of datetimemodule.c, zone conversion from UTC is a well defined operation unless there is a bug in tzinfo subclass implementation.
----------
assignee: docs@python
components: Documentation
messages: 108462
nosy: belopolsky, docs@python
priority: normal
severity: normal
stage: needs patch
status: open
title: TZ examples in datetime.rst are incorrect
versions: Python 2.7, Python 3.2
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue9063>
_______________________________________
New submission from MATSUI Tetsushi <mft(a)users.sourceforge.net>:
The library reference of pkgutil is only sparsely marked up.
The attached patch is against 2.6 version, because I'm currently working with 2.6. Since a part of markups (namely :pep:'s) has already been done for 3.2 version, the patch cannot be applied directly to that version, and I haven't checked the versions in between.
----------
assignee: docs@python
components: Documentation
files: pkgutil.diff
keywords: patch
messages: 106708
nosy: docs@python, mft
priority: normal
severity: normal
status: open
title: pkgutil document needs more markups
versions: Python 2.6
Added file: http://bugs.python.org/file17492/pkgutil.diff
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue8851>
_______________________________________
New submission from Daniel Stutzbach <daniel(a)stutzbachenterprises.com>:
Here's the relevant signature:
/* Get the maximum ordinal for a Unicode character. */
PyAPI_FUNC(Py_UNICODE) PyUnicode_GetMax(void);
----------
assignee: docs@python
components: Documentation
messages: 105206
nosy: docs@python, stutzbach
priority: normal
severity: normal
stage: needs patch
status: open
title: PyUnicode_GetMax is undocumented
versions: Python 2.7, Python 3.2
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue8647>
_______________________________________
New submission from Daniel Stutzbach <daniel(a)stutzbachenterprises.com>:
PyUnicode_AsEncodedObject is undocumented. It has the same signature as PyUnicode_AsEncodedString, although they do slightly different things based on a brief source code inspection (I'm not clear on what that difference is though).
----------
assignee: docs@python
components: Documentation
messages: 105203
nosy: docs@python, stutzbach
priority: normal
severity: normal
stage: needs patch
status: open
title: PyUnicode_AsEncodedObject is undocumented
versions: Python 2.7, Python 3.2
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue8645>
_______________________________________