docs August 2010

docs@python.org

21 participants
214 discussions

hmac.digest() return value
by Perseids 17 Oct '10

17 Oct '10

Hi, I am new to Python 3, but I believe I have found a little error in the documentation. The return value of hmac.digest() is a bytes object, and not a string. See http://docs.python.org/py3k/library/hmac.html . Regards Perseids

2 1

[issue8855] Shelve documentation lacks security warning
by Longpoke 17 Oct '10

17 Oct '10

New submission from Longpoke <longpoke(a)gmail.com>: Loading a shelve can cause arbitrary code to be executed [1] and other black magic (because it's backed by Pickle). Shouldn't there be a big fat warning at the top of the shelve documentation page? Unless you're like me and assume anything to do with serialization in any language is insecure until proved otherwise, you aren't going to intuitively think there is anything wrong with "unshelving" untrusted data (unless you already know that Pickle is insecure). 1. http://nadiana.com/python-pickle-insecure#comment-261 ---------- assignee: docs@python components: Documentation messages: 106746 nosy: docs@python, q94IjzUfnNoyv4c75mMw priority: normal severity: normal status: open title: Shelve documentation lacks security warning _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8855> _______________________________________

3 3

[issue8811] fixing sqlite3 docs for py3k
by Shashwat Anand 17 Oct '10

17 Oct '10

New submission from Shashwat Anand <anand.shashwat(a)gmail.com>: The docs of sqlite3 for python 3.0 and 3.1 seems to be written for python 2.6 and hence wrong at many places. like, >>> for member in r: print member However the docs for sqlite3 in py3k trunk seems fine. The sqlite3 doc in py3k trunk should be used in these places. http://docs.python.org/release/3.0.1/library/sqlite3.html http://docs.python.org/release/3.1/library/sqlite3.html ---------- assignee: docs@python components: Documentation files: sqlite.rst.patch keywords: patch messages: 106382 nosy: docs@python, georg.brandl, ghaering, l0nwlf priority: normal severity: normal status: open title: fixing sqlite3 docs for py3k versions: Python 3.1, Python 3.2 Added file: http://bugs.python.org/file17451/sqlite.rst.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8811> _______________________________________

3 6

[issue8686] "This isn't defined beyond that" phrase is not friendly to non-native English speakers.
by INADA Naoki 17 Oct '10

17 Oct '10

New submission from INADA Naoki <songofacandy(a)gmail.com>: http://docs.python.org/library/difflib.html#difflib.SequenceMatcher.quick_r… > This isn’t defined beyond that it is an upper bound on ratio(), and is faster to compute. "beyond" is a bit confusing because it also means "over" and this sentence refers upper bound. I think "This isn't defined in detail more than..." is easier. ---------- assignee: docs@python components: Documentation messages: 105498 nosy: docs@python, naoki priority: normal severity: normal status: open title: "This isn't defined beyond that" phrase is not friendly to non-native English speakers. versions: Python 2.6, Python 2.7, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8686> _______________________________________

7 8

[issue8556] Confusing string formatting examples
by Jeff McNeil 17 Oct '10

17 Oct '10

New submission from Jeff McNeil <jeff(a)jmcneil.net>: I was going through the string formatting examples this evening and noticed this: print '%(language)s has %(#)03d quote types.' % \ {'language': "Python", "#": 2} The example uses a '#' as a map key. This is somewhat misleading as if we had simply left the parenthesis off, the '#' would have been interpreted as an alternate conversion flag. Should be updated to use a more verbose (and less confusing) dictionary key. ---------- assignee: docs@python components: Documentation files: stdtypes.rst.2.6.5.patch keywords: patch messages: 104410 nosy: docs@python, mcjeff priority: normal severity: normal status: open title: Confusing string formatting examples versions: Python 2.6 Added file: http://bugs.python.org/file17115/stdtypes.rst.2.6.5.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8556> _______________________________________

4 5

[issue9093] Tools/README is out of date
by Alexander Belopolsky 14 Oct '10

14 Oct '10

New submission from Alexander Belopolsky <belopolsky(a)users.sourceforge.net>: Here is the list of subdirectories in Tools. Here is the diff between directory listing and readme ('-' means no readme entry, '+' - no tool): -buildbot -ccbench +audiopy +compiler faqwiz -framer freeze gdb i18n -iobench -msi -pybench pynche scripts -ssl unicode versioncheck +webchecker world ---------- assignee: docs@python components: Documentation messages: 108797 nosy: belopolsky, docs@python priority: normal severity: normal stage: needs patch status: open title: Tools/README is out of date type: feature request versions: Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9093> _______________________________________

3 5

[issue9666] 'hasattr' fix to suppress only AttributeError
by Yury Selivanov 28 Sep '10

28 Sep '10

New submission from Yury Selivanov <yselivanov(a)gmail.com>: As discussed on python-dev mailing list (http://mail.python.org/pipermail/python-dev/2010-August/103178.html), 'hasattr' default behaviour should be changed to suppress only AttributeError exceptions. Other should pass through. The fix, however, shouldn't change behaviour of existing C API, functions PyObject_HasAttr and PyObject_HasAttrString in particular. I'm targeting this issue on Python 3.2 version, but probably it may be introduced in the next Python 3.1 maintenance release. ---------- assignee: docs@python components: Documentation, Library (Lib) files: hasattr.patch keywords: patch messages: 114767 nosy: Yury.Selivanov, docs@python priority: normal severity: normal status: open title: 'hasattr' fix to suppress only AttributeError type: behavior versions: Python 3.2 Added file: http://bugs.python.org/file18622/hasattr.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9666> _______________________________________

3 3

[issue9562] Slightly misleading wording in documentation of dict.update
by Mitchell Model 25 Sep '10

25 Sep '10

New submission from Mitchell Model <mlm(a)acm.org>: The documentation of dict.update says that it "accepts either another dictionary object or an iterable of key/value pairs (as a tuple or other iterable of length two)" The parenthesized phrase is slightly misleading in that it could be interpreted as requiring the argument to be an iterable of length two, whereas the argument should be an iterable of iterables of length 2 (if not a dictionary). Suggest rewriting in the plural: (as tuples or other iterables of length two) ---------- assignee: docs@python components: Documentation messages: 113557 nosy: MLModel, docs@python priority: normal severity: normal status: open title: Slightly misleading wording in documentation of dict.update versions: Python 2.6, Python 2.7, Python 3.1 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9562> _______________________________________

5 4

[issue9582] documentation line needs rewording
by Robert Mohr 23 Sep '10

23 Sep '10

New submission from Robert Mohr <python-bugs(a)mohrr.net>: The last line of http://docs.python.org/faq/programming.html#is-there-a-scanf-or-sscanf-equi… is not proper English: For more complicated input parsing, regular expressions more powerful than C’s sscanf() and better suited for the task. This also shows up in the 3.2 docs. ---------- assignee: docs@python components: Documentation messages: 113711 nosy: docs@python, mohrr priority: normal severity: normal status: open title: documentation line needs rewording versions: Python 2.7, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9582> _______________________________________

6 6

[issue9608] Re-phrase best way of using exceptions in doanddont.rst
by Floris Bruynooghe 12 Sep '10

12 Sep '10

New submission from Floris Bruynooghe <floris.bruynooghe(a)gmail.com>: The description of how to best use exceptions is slightly confusing and led me to believe there was an issue when using open() as a context manager. The main issue is that the wording seems to suggest the example above it is the best and not the very last. Attached is a patch which uses a slightly different wording which IMHO makes it clearer that the with-statement is the preferred method and does not introduce subtle bugs. ---------- assignee: docs@python components: Documentation files: doandont.diff keywords: patch messages: 113949 nosy: docs@python, flub priority: normal severity: normal status: open title: Re-phrase best way of using exceptions in doanddont.rst type: feature request versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file18538/doandont.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9608> _______________________________________

4 9

← Newer
1
...
4
5
6
7
8
9
10
...
22
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

docs August 2010