Mailman 3 September 2010 - docs

[issue9933] os module does not have the documented EX_NOTFOUND attribute
by R. David Murray Sept. 24, 2010

Sept. 24, 2010

R. David Murray <rdmurray(a)bitdance.com> added the comment: Perhaps this constant existed at some point on some linux systems...google found one comment about it referencing posix.2. I also found it mentioned in a specific version of sendmail, and in bash. When it appears it seems to most often have the value 127. I suspect the mention of this constant should just be deleted from the docs. Google code search finds no mention of it in any sysexits.h file anywhere it has searched, so the chances are this constant will never be defined by Python. ---------- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python, r.david.murray versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9933> _______________________________________

1 0

[issue9921] os.path.join('x','') behavior
by Brian Brazil Sept. 23, 2010

Sept. 23, 2010

Brian Brazil <brian.brazil(a)gmail.com> added the comment: The behaviour is a bit more nuanced: >>> os.path.join('x', '') 'x/' >>> os.path.join('x', '', 'y') 'x/y' >>> os.path.join('x', '', 'y', '', '') 'x/y/' >>> os.path.join('', 'x') 'x' I'm unsure how to word this best, maybe "non-trailing empty paths are ignored"? ---------- nosy: +bbrazil _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9921> _______________________________________

1 0

[issue9582] documentation line needs rewording
by Robert Mohr Sept. 23, 2010

Sept. 23, 2010

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

http://docs.python.org/library/compiler.html
by Jean-Jacques DORMARD Sept. 23, 2010

Sept. 23, 2010

Hi, (very) little syntax error here " It uses the built-in parser and standard parser module to generate d a concrete syntax tree" More importantly, it is mentioned that the package is deprecated. Can you give the name of a valid equivalent package? Congratulations for the excellent work ;) JJ

1 0

[issue9921] os.path.join('x','') behavior
by R. David Murray Sept. 22, 2010

Sept. 22, 2010

R. David Murray <rdmurray(a)bitdance.com> added the comment: Since changing the implementation would be a backward incompatible behavior change to a behavior that has existed for a long time, it's the docs that should be updated. ---------- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python, r.david.murray stage: -> needs patch versions: +Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9921> _______________________________________

1 0

[issue1660009] continuing problem with httplib multiple set-cookie headers
by John J Lee Sept. 21, 2010

Sept. 21, 2010

John J Lee <jjlee(a)users.sourceforge.net> added the comment: What I said in 2007 re commas could be well out of date (might well have been so even then, in fact). Somebody should check what browsers do now... ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue1660009> _______________________________________

1 0

[issue6627] threading.local() does not work with C-created threads
by Swapnil Talekar Sept. 21, 2010

Sept. 21, 2010

Swapnil Talekar <swapnil.st(a)gmail.com> added the comment: Nick, the last statement, "While this is correct for most purposes, it does mean that..." can be simplified to, "It means...". I had to read it several times before I realized, there is no "not" after "does" :) BTW, since this particular arrangement of having a temporary thread state during the callback is particularly useful for ctypes (I cannot imagine any other usecase) and also it sort-of breaks things, a potential feature request could be to have consistent thread state during the lifetime of a C thread. I don't have much idea how to do that or whether it is even possible? Would anyone like to give a thought? ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue6627> _______________________________________

2 1

[issue9583] Document startup option/environment interaction
by Terry J. Reedy Sept. 21, 2010

Sept. 21, 2010

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: I do not deny that the behavior described in the doc is a bit strange (keying off of type, ignoring value) is a bit bizarre and contrary to reasonable expectation based on other programs. But to alter behavior before 3.2 or later would require a clearly demonstrated discrepancy between doc and behavior, which I do not see. For startup behavior, some discussion on pydev or python-ideas lists would probably be needed. If the C code you posted is a quote from the Python source, please give the file path, preferably for current trunk version (the py3k branch). The second 'if' looks a bit strange at first glance, but I will not judge without seeing more. > I believe setting this environment value to zero and expecting the feature to be off (given no contradicting options) is reasonable. Optimization is off by default. So there is no need to have a environment value that means to keep it off. Just do not set it. Or unset it if needed. That said, the code you showed suggests that the option/environment interaction is more complicated than I thought, at least for this pair. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9583> _______________________________________

2 1

[issue9583] Document startup option/environment interaction
by R. David Murray Sept. 21, 2010

Sept. 21, 2010

R. David Murray <rdmurray(a)bitdance.com> added the comment: I understood the documentation snippet Terry quoted as saying exactly what you say the code does. The doc could be clearer by replacing "multiple times" with "that number of times". Not that more than two has any meaning currently... Changing the behavior of PYTHONOPTIMIZE as you suggest would be a backward compatibility change that would probably require a deprecation cycle. (And the message would have to not really be a DeprecationWarning, since DeprecationWarnings are now silent by default but this is a user-triggered event, not a developer-triggered event and so should be user visible.) Unsetting an environment variable to remove its effect is a fairly common idiom. So I don't think it is worth the effort of making the change you suggest, even though I agree it would be more intuitive if PYTHONOPTIMIZE=0 meant what you thought it meant. ---------- nosy: +r.david.murray _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9583> _______________________________________

2 1

[issue9583] Document startup option/environment interaction
by Buck Golemon Sept. 21, 2010

Sept. 21, 2010

Buck Golemon <buck.golemon(a)amd.com> added the comment: If I understand this code, it means that PYTHONOPTIMIZE set to 1 or 2 works as expected, but set to 0, gives a flag value of 1. static int add_flag(int flag, const char *envs) { int env = atoi(envs); if (flag < env) flag = env; if (flag < 1) flag = 1; return flag; } Read literally, the man page indicates that any integer value will give a flag value of 2. I agree my shell script is probably unusual, but I believe setting this environment value to zero and expecting the feature to be off (given no contradicting options) is reasonable. I petition to remove the second if statement above (environment value of "0" yields no flag). I'd also love to provide a numeric argument to -O, to dynamically set this value more readily, but that is lower importance. I can implement these and run the unit tests if required. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9583> _______________________________________

1 0