docs December 2014

docs@python.org

39 participants
553 discussions

Typo in class io.BufferedIOBase docs (issue 22671)
by vadmium+py＠gmail.com 20 Dec '14

20 Dec '14

https://bugs.python.org/review/22671/diff/13472/Doc/library/io.rst File Doc/library/io.rst (right): https://bugs.python.org/review/22671/diff/13472/Doc/library/io.rst#newcode4… Doc/library/io.rst:495: A default implementation is provided. Just noticed the summary of mixin methods near the top of the page. Need to add readinto1() there, but maybe all of this “default implementation provided” is not needed after all. https://bugs.python.org/review/22671/

1 0

[issue22673] document the special features (eg: fdclose=False) of the standard streams
by Martin Panter 20 Dec '14

20 Dec '14

Changes by Martin Panter <vadmium+py(a)gmail.com>: ---------- nosy: +vadmium _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22673> _______________________________________

1 0

[issue12600] Add example of using load_tests to parameterise Test Cases
by Martin Panter 20 Dec '14

20 Dec '14

1 0

[issue21071] struct.Struct.format is bytes, but should be str
by Raymond Hettinger 19 Dec '14

19 Dec '14

Raymond Hettinger added the comment: I would like to see this and issue 8934 discussed as a usability bug. As far as I can tell, the current state of affairs an unintended by-product of a rushed effort to split the standard library to bytes apis and unicode apis. I don't see any reason that we should have to live with this forever. ---------- nosy: +rhettinger _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue21071> _______________________________________

1 0

[issue9694] argparse required arguments displayed under "optional arguments"
by Martin Panter 19 Dec '14

19 Dec '14

Martin Panter added the comment: Updated my patch with a “version changed” notice ---------- Added file: http://bugs.python.org/file37505/option-internal.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9694> _______________________________________

1 0

Document PySequence_List(o) as equivalent to list(o) (issue 23081)
by berker.peksag＠gmail.com 18 Dec '14

18 Dec '14

http://bugs.python.org/review/23081/diff/13453/Doc/c-api/sequence.rst File Doc/c-api/sequence.rst (right): http://bugs.python.org/review/23081/diff/13453/Doc/c-api/sequence.rst#newco… Doc/c-api/sequence.rst:111: or *NULL* on failure. The returned list is guaranteed to be new. This is *NULL* -> ``NULL`` http://bugs.python.org/review/23081/

1 0

[issue21071] struct.Struct.format is bytes, but should be str
by Arfrever Frehtes Taifersar Arahesis 18 Dec '14

18 Dec '14

Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA(a)GMail.Com>: ---------- nosy: +Arfrever _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue21071> _______________________________________

1 0

[issue23083] sys.exit with bool parameter
by Polux Moon 18 Dec '14

18 Dec '14

New submission from Polux Moon: when using a bool as parameter implementation (2.7) behave like: sys.exit(True) <=> sys.exit(1) sys.exit(False) <=> sys.exit(0) so the bool indicate if the termination is abnormal following the doc it should be equivalent to sys.exit(1) in all cases if we assume the implementation is right, the doc should describe the behavior for boolean input ---------- assignee: docs@python components: Documentation messages: 232883 nosy: Polux.Moon, docs@python priority: normal severity: normal status: open title: sys.exit with bool parameter type: enhancement versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue23083> _______________________________________

4 5

[issue23079] os.path.normcase documentation confusing
by Chris Jerdonek 18 Dec '14

18 Dec '14

New submission from Chris Jerdonek: The documentation for os.path.normcase(path) is currently confusing or self-contradictory. Currently, it reads-- "Normalize the case of a pathname. On Unix and Mac OS X, this returns the path unchanged; on case-insensitive filesystems, it converts the path to lowercase." However, with a case-insensitive file system on Mac OS X (e.g. "File System Personality: Journaled HFS+"), normcase() does not convert paths to lowercase. As it stands, it seems like the clause "on case-insensitive filesystems, it converts the path to lowercase" should be removed or further qualified. I don't know what the qualification is though. ---------- assignee: docs@python components: Documentation, Library (Lib) messages: 232871 nosy: chris.jerdonek, docs@python priority: normal severity: normal status: open title: os.path.normcase documentation confusing type: behavior versions: Python 2.7, Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue23079> _______________________________________

3 4

[issue21071] struct.Struct.format is bytes, but should be str
by R. David Murray 18 Dec '14

18 Dec '14

R. David Murray added the comment: A backward compatibility break would certainly need to be discussed, IMO. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue21071> _______________________________________

1 0

← Newer
1
...
46
47
48
49
50
51
52
...
56
Older →

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

docs December 2014