Mailman 3 October 2011 - docs

[issue12943] tokenize: add python -m tokenize support back
by Éric Araujo 06 Oct '11

06 Oct '11

Éric Araujo <merwok(a)netwok.org> added the comment: I made a few last remarks on Rietveld; feel free to address or ignore them and commit right away. ---------- nosy: +eric.araujo _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12943> _______________________________________

1 0

Documentation bug in glob examples
by Ewan Higgs 05 Oct '11

05 Oct '11

Sir/Madame, I believe there is a bug in the documentation for the glob module accessed through the following url on 2011/10/05: http://docs.python.org/library/glob.html Currently the example demonstrates the output of a series of globbing patterns in a directory with files 1.gif, 2.gif, and card.gif. The results returned are incorrect. They read: >>> import glob >>> glob.glob('./[0-9].*') ['./1.gif', './2.txt'] >>> glob.glob('*.gif') ['1.gif', 'card.gif'] >>> glob.glob('?.gif') ['1.gif'] However, the results should be as follows: $python Python 2.6.5 (r265:79063, Apr 26 2010, 12:52:32) [GCC 4.4.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import glob >>> glob.glob('./[0-9].gif') ['./1.gif', './2.gif'] >>> glob.glob('*.gif') ['1.gif', 'card.gif', '2.gif'] >>> glob.glob('?.gif') ['1.gif', '2.gif'] >>> Yours, Ewan Higgs NB: This email was written based on advice found here: http://docs.python.org/bugs.html

2 2

[issue12880] ctypes: clearly document how structure bit fields are allocated
by Meador Inge 04 Oct '11

04 Oct '11

New submission from Meador Inge <meadori(a)gmail.com>: As issues like issue6069 and issue11920 allude to, figuring out how 'ctypes' allocates bit-fields is not very clear. The documentation should be enhanced to flesh this out in more detail. As an example, Microsoft documents the VC++ implementation in a reasonably clear manner ( http://msdn.microsoft.com/en-us/library/ewwyfdbe(v=vs.71).aspx ). ---------- assignee: docs@python components: Documentation messages: 143369 nosy: docs@python, meadori, terry.reedy, vladris priority: normal severity: normal stage: needs patch status: open title: ctypes: clearly document how structure bit fields are allocated type: feature request versions: Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12880> _______________________________________

3 9

Epub and A5
by akatsuki deidara 03 Oct '11

03 Oct '11

Hi. Is it possible to have an epub version or an A5 version of the documentations? Thanks.

2 1

"sane" tzinfo subclasses
by Paul Koning 03 Oct '11

03 Oct '11

Gentlepeople, Section 8.1.6 of the library manual talks about utcoffset(dt)-dst(dt) as the "standard offset" and says that this should not depend on the date or time but only on the location. That seems to assume that the politicians who change timezone rules only change the times when DST is in effect, but don't meddle with the standard offset. Often that is true, at least so long as you don't go all that far into the past. But not always. Consider Venezuela, which changed from standard offset -4:00 to -4:30 in 2007, or Samoa, which is changing from -11:00 to +13:00 end of this year. For that matter, various parts of Indiana seem to be switching from time to time, as recently as a couple of years ago. Admittedly this is not all that sane, but then again it's politics. If datetime.astimezone() relies on this assumption when it's clearly not always satisfied, what goes wrong? See the Olson database for all the gory details; the examples I quoted all can be found in there. paul

2 3

[issue13094] Need Programming FAQ entry for the behavior of closures
by Ezio Melotti 03 Oct '11

03 Oct '11

Ezio Melotti <ezio.melotti(a)gmail.com> added the comment: Maybe with a different name is less confusing: lambda return_value=each: return_value This copies the value of 'each' in a variable called 'return_value' that is local to the lambda. Since the copy happens when the lambdas are defined, 'return_value' has then the right value. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13094> _______________________________________

1 0

[issue13094] Need Programming FAQ entry for the behavior of closures
by Tomáš Dvořák 03 Oct '11

03 Oct '11

Tomáš Dvořák <dvtomas(a)gmail.com> added the comment: Thank you all very much for the super-quick responses. I'm used to smalltalk, so the python variable binding behaviour is unnatural to me, but I guess there must have been some reasons for making it behave this way. Ezio, the "lambda each=each: each" trick works nicely, thanks a lot. But - what does it mean? :) I just don't know how to parse and understand it :-) Best regards, Tomáš Dvořák ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13094> _______________________________________

1 0

[issue13094] Need Programming FAQ entry for the behavior of closures
by Ezio Melotti 03 Oct '11

03 Oct '11

Ezio Melotti <ezio.melotti(a)gmail.com> added the comment: To understand better what's going on, try to change the value of 'each' after the 3 prints and then call again the 3 methods: you will see that they now return the new value of each. This is because the lambdas refer to global 'each' (that at the end of the loop is set to 'baz'). If you do setattr(x, each, lambda each=each: each), the each will be local to the lambda, and it will then work as expected. An entry in the FAQ would be useful, I thought it was there already but apparently it's not (I'm pretty sure I saw this already somewhere in the doc, but I can't seem to find where). ---------- assignee: docs@python -> components: +None -Documentation nosy: +ezio.melotti stage: needs patch -> type: behavior -> versions: -Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13094> _______________________________________

1 0

[issue13094] Need Programming FAQ entry for the behavior of closures
by R. David Murray 03 Oct '11

03 Oct '11

Changes by R. David Murray <rdmurray(a)bitdance.com>: ---------- title: setattr misbehaves when used with lambdas inside for loop -> Need Programming FAQ entry for the behavior of closures _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13094> _______________________________________

1 0

[issue13094] setattr misbehaves when used with lambdas inside for loop
by R. David Murray 03 Oct '11

03 Oct '11

R. David Murray <rdmurray(a)bitdance.com> added the comment: Sorry. It is intended behavior. The lambda 'each' is bound to the local 'each', and by the time the lambda's execute, the value of 'each' is 'baz'. I'm going to turn this into a doc bug, because while I'm pretty sure this is documented *somewhere*, I don't see it in the programming FAQ, and it should be there. ---------- assignee: -> docs@python components: +Documentation -None nosy: +docs@python, r.david.murray stage: -> needs patch type: -> behavior versions: +Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13094> _______________________________________

1 0