Mailman 3 November 2011 - docs

[issue13305] datetime.strftime("%Y") not consistent for years < 1000
by STINNER Victor 03 Nov '11

03 Nov '11

STINNER Victor <victor.stinner(a)haypocalc.com> added the comment: Since the changeset 55a3b563f0dbed04af317f632f7f3c0f6abe175b, test_strptime is failing on "AMD64 Gentoo Wide 3.x" buildbot: ====================================================================== FAIL: test_strptime (test.test_time.TimeTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/buildbot/buildarea/3.x.ochtman-gentoo-amd64/build/Lib/test/test_time.py", line 159, in test_strptime time.strptime(strf_output, format) ValueError: time data 'LMT' does not match format '%Z' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/buildbot/buildarea/3.x.ochtman-gentoo-amd64/build/Lib/test/test_time.py", line 162, in test_strptime (format, strf_output)) AssertionError: conversion specifier '%Z' failed with 'LMT' input. ---------------------------------------------------------------------- http://www.python.org/dev/buildbot/all/builders/AMD64%20Gentoo%20Wide%203.x… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13305> _______________________________________

1 0

[issue13305] datetime.strftime("%Y") not consistent for years < 1000
by Florent Xicluna 03 Nov '11

03 Nov '11

Florent Xicluna <florent.xicluna(a)gmail.com> added the comment: I understand that the issue is because the C standard does not specify the length of the string returned by '%Y'. The changeset 230f0956aaa3 adds a test to verify that either '%Y' or '%4Y' returns a 4-digits value usable to produce ISO-8601 representations. Now it is a documentation issue: add a comment to the "%Y" specifier saying that the padding is not applicable to all platforms and in such case the "%4Y" specifier should return the 4-digit value. ---------- assignee: -> docs@python components: +Documentation dependencies: -external strftime for Python? nosy: +docs@python superseder: -> external strftime for Python? _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13305> _______________________________________

1 0

[issue13147] Multiprocessing Pool.map_async() does not have an error_callback parameter
by Jakub Gedeon 02 Nov '11

02 Nov '11

New submission from Jakub Gedeon <kazagistar(a)gmail.com>: Multiprocessing Pool.map_async() does not have an error_callback paramter as described here http://docs.python.org/library/multiprocessing.html#multiprocessing.pool.mu… I assume this is an old configuration that no longer works... I tried to call that parameter by name and I got a Type Error, plus the actual documentation does not mention it at all (and it is missing from similar functions). Recommend it be removed from the documentation, or else better described and implemented. ---------- assignee: docs@python components: Documentation messages: 145316 nosy: Jakub.Gedeon, docs@python priority: normal severity: normal status: open title: Multiprocessing Pool.map_async() does not have an error_callback parameter versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13147> _______________________________________

5 6

[issue12709] In multiprocessing, error_callback isn't documented for map_async
by Hynek Schlawack 02 Nov '11

02 Nov '11

New submission from Hynek Schlawack <hs(a)ox.cx>: While working on #12708 , I noticed that the error_callback argument of multiprocessing.Pool.map_async() isn't documented (callback is). ---------- assignee: docs@python components: Documentation messages: 141763 nosy: docs@python, hynek priority: normal severity: normal status: open title: In multiprocessing, error_callback isn't documented for map_async type: behavior versions: Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12709> _______________________________________

4 5

Python docs bug in 2.6 - 'as' is now a reserved keyword
by Tim Bellis 01 Nov '11

01 Nov '11

http://docs.python.org/whatsnew/2.6.html#porting-to-python-2-6 doesn't mention that 'as' is now a reserved keyword in Python 2.6 and so any variables named 'as' will need to be renamed. Regards, Tim PS Handily, we're warned about this in Python 2.5 :) Python 2.5 (r25, Dec 12 2008, 17:45:12) [GCC 4.1.2 20070626 (Red Hat 4.1.2-14)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> as=1 <stdin>:1: Warning: 'as' will become a reserved keyword in Python 2.6

2 1

A bug in the datetime module documentation
by Daniil Shved 01 Nov '11

01 Nov '11

Hi there, I found what seems to be an error in the python 2.7.2 docs for "datetime" module: http://docs.python.org/library/datetime.html?highlight=datetime#tzinfo-obje… In the documentation for method tzinfo.dst(self, dt) there are two code samples (under "most implementations of dst() will probably look like one of these two"). In these code samples the method is defined as "def dst(self):", but it should be "def dst(self, dt)". -- Dan Shved danshved(a)gmail.com

2 1