[issue12875] backport re.compile flags default value documentation

Ezio Melotti added the comment: I created #13386 about the conventions that should be followed in the doc. Converting the whole page is fine with me. -- ___ Python tracker ___

[issue13386] Document documentation conventions for optional args

New submission from Ezio Melotti : AFAIU the conventions for optional argument in the doc are as follow: If a function has optional arguments and it accepts keyword arguments, the "func(arg=default)" notation should be used, for example: str.splitlines(keepends=False) If a function has optio

[issue12767] document threading.Condition.notify

Eli Bendersky added the comment: Ezio, thanks for the catch. I missed that one. Attaching a new, fixed patch. -- Added file: http://bugs.python.org/file23658/issue12767.2.patch ___ Python tracker _

[issue12875] backport re.compile flags default value documentation

Eli Bendersky added the comment: Hmm, I've just notice that this [default=val] pattern already exists in the 're' docs in 2.7, for example: subn(repl, string[, count=0]) So my change was consistent within the documentation of this module. No doubt, the conventions are currently a mess ;-)

[issue12767] document threading.Condition.notify

Ezio Melotti added the comment: + This method wakes up at most *n* of the threads + The current implementation wakes up exactly *n* threads + A future, optimized implementation may occasionally wake up more than + one thread. Isn't this a bit contradictory? -- nosy:

[issue12875] backport re.compile flags default value documentation

Ezio Melotti added the comment: I suggest removing the []. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10501] make_buildinfo regression with unquoted path

Changes by Eli Bendersky : -- nosy: -eli.bendersky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue5088] optparse: inconsistent default value for append actions

Changes by Eli Bendersky : -- nosy: -eli.bendersky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue10838] subprocess __all__ is incomplete

Changes by Eli Bendersky : -- nosy: -eli.bendersky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue3849] FUD in documentation for urllib.urlopen()

Changes by Eli Bendersky : -- nosy: -eli.bendersky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue11173] Undocumented public APIs in Python 3.2

Changes by Eli Bendersky : -- nosy: -eli.bendersky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue12188] PEP 7 (or guide) add C style policies and explanation

Changes by Eli Bendersky : -- nosy: -eli.bendersky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue12768] docstrings for the threading module

Eli Bendersky added the comment: Graeme, any news on this? If you re-do the patch for current tip and address the review comments, I think we can commit it. -- ___ Python tracker

[issue12767] document threading.Condition.notify

Eli Bendersky added the comment: I propose the attached patch for the documentation. Any objections? -- keywords: +patch Added file: http://bugs.python.org/file23657/issue12767.1.patch ___ Python tracker _

[issue12875] backport re.compile flags default value documentation

Eli Bendersky added the comment: Ezio, what do you suggest to do regarding *this* issue? -- ___ Python tracker ___ ___ Python-bugs-li

[issue12875] backport re.compile flags default value documentation

Ezio Melotti added the comment: > but can we first get the convention documented somewhere? +1 This was on my todo list, but feel free to open a new issue about it. > Grepping through the docs disagrees with your claims That's because is not documented and not everyone is aware of the conven

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Ezio Melotti added the comment: If you want to provide no flags, I think it's easier to provide no flags, rather than having to learn some NOFLAGS constant value that can be used to make the fact that you are passing no flags more explicit than it already is. I might agree that ORing flags mig

[issue12875] backport re.compile flags default value documentation

Eli Bendersky added the comment: Amaury & Georg, Grepping through the docs disagrees with your claims ;-) Try to grep for "\=None\]" to see what I mean. There are tons of places where default values are placed inside the brackets. For example in http://docs.python.org/library/csv.html --> lo

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Eli Bendersky added the comment: Antoine, what's the outcome of people wondering about the difference? I don't see what's bad about it, it's not as if people are writing (or supposed to write) code that does arithmetic on these flag values. Their only usage is to: 1. Provide no flags 2. Provi

[issue13333] utf-7 inconsistent with surrogates

Ezio Melotti added the comment: FWIW Wikipedia says "Other characters must be encoded in UTF-16 (hence U+1 and higher would be encoded into surrogates) and then in modified Base64." So one possible interpretation is that while encoding a non-BMP char, it should be first converted in a sur

[issue13384] Unnecessary __future__ import in random module

Ezio Melotti added the comment: AFAIK on 2.x there are a few modules that are supposed to work even with older version of Python (I think I even saw one that is supposed to still be compatible with Python 1.5). I don't think this is the case for Python 3 though. -- nosy: +ezio.melotti

[issue13384] Unnecessary __future__ import in random module

Raymond Hettinger added the comment: At one point, for 2.x at least, we weren't removing the "from __future__" imports even after the feature became available. -- ___ Python tracker __

[issue13193] test_packaging and test_distutils failures

Roundup Robot added the comment: New changeset 0a94e2f807c7 by Antoine Pitrou in branch '3.2': Issue #13193: fix distutils.filelist.FileList under Windows http://hg.python.org/cpython/rev/0a94e2f807c7 New changeset 80d5040f2a78 by Antoine Pitrou in branch '3.2': Add NEWS entry for #13193 http:/

[issue12988] IDLE on Win7 crashes when saving to Documents Library

Changes by Ned Deily : -- nosy: +amaury.forgeotdarc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue13384] Unnecessary __future__ import in random module

Benjamin Peterson added the comment: Things won't ever be removed from the __future__ module, but there's no harm in removing ones with no effect. -- nosy: +benjamin.peterson ___ Python tracker __

[issue12988] IDLE on Win7 crashes when saving to Documents Library

Cody C added the comment: Still an issue as of 11/11/11. -- nosy: +Cody.C ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue12988] IDLE on Win7 crashes when saving to Documents Library

Changes by Cody C : -- type: -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Ezio Melotti added the comment: I think a proper solution would be fixing #11957. Adding a NOFLAGS alias for 0 would help fixing #12875, but I don't think it will be useful/use otherwise. -- ___ Python tracker _

[issue13384] Unnecessary __future__ import in random module

Brian Curtin added the comment: That's news to me since it probably pre-dates my involvement around here. I'll revert if that's correct. -- ___ Python tracker ___ _

[issue13384] Unnecessary __future__ import in random module

Raymond Hettinger added the comment: I thought we had a policy that future imports would never be removed. -- nosy: +rhettinger status: closed -> open ___ Python tracker ___ ___

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Antoine Pitrou added the comment: As Eric, I don't really think it's useful, and it might actually be confusing (people will start wondering if there's a difference between 0 and NOFLAGS). -- nosy: +pitrou ___ Python tracker

[issue13239] Remove <> operator from Grammar/Grammar

Brett Cannon added the comment: I think the clarification should be enough. -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue12875] backport re.compile flags default value documentation

Georg Brandl added the comment: No, it's not. -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue12875] backport re.compile flags default value documentation

Amaury Forgeot d'Arc added the comment: The documentation now shows:: match(pattern, string[, flags=0]) Is it normal to have the brackets *and* the default value? -- nosy: +amaury.forgeotdarc status: closed -> open ___ Python tracker

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

Eric V. Smith added the comment: Since the flags are OR'd together, I don't see what other value the "no flags" parameter could have, other than zero. That said, I don't feel strongly about it, and if it helps readability I'm not opposed. -- ___ Py

[issue13385] Add an explicit re.NOFLAGS flag value to the re module

New submission from Eli Bendersky : The flags 're' accept are numeric underneath, and the current value of "no flags" is just 0, which is also specified in the documentation as the default value. However, using raw numeric values is not a good programming practice. The suggestion is to add a

[issue12875] backport re.compile flags default value documentation

Changes by Eli Bendersky : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue12875] backport re.compile flags default value documentation

Roundup Robot added the comment: New changeset 02e4d3ebbb02 by Eli Bendersky in branch '2.7': Issue #12875: explicitly specify default value of the optional 'flags' argument to re.* functions. Closes #12875 http://hg.python.org/cpython/rev/02e4d3ebbb02 -- nosy: +python-dev ___

[issue13309] test_time fails: time data 'LMT' does not match format '%Z'

Florent Xicluna added the comment: Thank you for the investigation, and the bug report to the glibc team. I propose to close it as "won't fix". -- resolution: -> wont fix stage: test needed -> committed/rejected status: open -> pending ___ Python tr

[issue13309] test_time fails: time data 'LMT' does not match format '%Z'

Roundup Robot added the comment: New changeset bcd347cd6bf2 by Florent Xicluna in branch 'default': Use unittest.skipUnless to skip the test related to the glibc bug, issue #13309. http://hg.python.org/cpython/rev/bcd347cd6bf2 -- ___ Python tracker

[issue10854] Output .pyd name in error message of ImportError when DLL load fails

Brian Curtin added the comment: Marked #1559549 as a dependency. I combine the patch in this issue with the one over there. -- dependencies: +ImportError needs attributes for module and file name ___ Python tracker

[issue13384] Unnecessary __future__ import in random module

Changes by Brian Curtin : -- assignee: -> brian.curtin nosy: +brian.curtin resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> behavior versions: -Python 3.4 ___ Python tracker __

[issue13384] Unnecessary __future__ import in random module

Roundup Robot added the comment: New changeset 3fdc5a75d6e1 by Brian Curtin in branch '3.2': Fix #13384. Remove __future__ import in 3.x code. http://hg.python.org/cpython/rev/3fdc5a75d6e1 -- nosy: +python-dev ___ Python tracker

[issue13384] Unnecessary __future__ import in random module

New submission from Robert Xiao : Lib/random.py in Python 3.2 contains the line from __future__ import division even though it is no longer necessary, as true float division is the default in Python 3. Trivial patch: --- lib/python3.2/random.py 2011-09-03 20:32:05.0 -0400 +++ lib

[issue13161] problems with help() documentation of __i*__ operators

Changes by Eli Bendersky : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13161] problems with help() documentation of __i*__ operators

Roundup Robot added the comment: New changeset 9fbaa190f011 by Eli Bendersky in branch '3.2': Issue #13161: fix doc strings of __i*__ operators http://hg.python.org/cpython/rev/9fbaa190f011 New changeset d58de3e9870a by Eli Bendersky in branch 'default': Issue #13161: fix doc strings of __i*__

[issue13161] problems with help() documentation of __i*__ operators

Roundup Robot added the comment: New changeset 369487785e9f by Eli Bendersky in branch '2.7': Issue #13161: fix doc strings of __i*__ operators http://hg.python.org/cpython/rev/369487785e9f -- nosy: +python-dev ___ Python tracker

[issue8402] glob returns empty list with "[" character in the folder name

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8402] glob returns empty list with "[" character in the folder name

flacs <0f1...@gmail.com> added the comment: As a workaround, it is possible to make every glob character a character set of one character (wrapping it with [] ). The gotcha here is that you can't just use multiple replaces because you would escape the escape brackets. Here is a function adapte

[issue13191] Typo in argparse documentation

Roundup Robot added the comment: New changeset 477f633aa09d by Eli Bendersky in branch '2.7': Issue #13191: typo in argparse docs http://hg.python.org/cpython/rev/477f633aa09d -- ___ Python tracker ___

[issue13368] Possible problem in documentation of module subprocess, method send_signal

Brian Curtin added the comment: > But it is useless for terminating a process with os.kill() in combination > with signal.SIGTERM, which corresponds to a CTRL-C-EVENT. SIGTERM does not correspond to CTRL_C_EVENT. They may be similar in what they do, but os.kill on Windows only works with exac

[issue3974] collections.namedtuple uses exec to create new classes

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue3974] collections.namedtuple uses exec to create new classes

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue13349] Uninformal error message in index() and remove() functions

Nick Coghlan added the comment: doctests by their very nature tend to overspecify things - that's why actual regression tests should be written with unittest, while doctest is kept for its originally intended purpose of testing examples included in docstrings and other documentation. Still,

[issue13237] subprocess docs should emphasise convenience functions

Nick Coghlan added the comment: Calling this one done - any further adjustments can be handled as new tracker issues. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker

[issue11638] python setup.py sdist crashes if version is unicode

Jason R. Coombs added the comment: First, the term 'gztar' doesn't appear in this ticket, and since the issue only applies when sdist --format gztar, I mention that here. Also, issue8396 suggests encoding using sys.getfilesystemencoding(). -- nosy: +jason.coombs _

[issue13383] UnicodeDecodeError in distutils.core.setup when version is unicode

Ezio Melotti added the comment: This is a duplicate of #11638. -- nosy: +ezio.melotti resolution: -> duplicate stage: -> committed/rejected status: open -> closed ___ Python tracker _

[issue13383] UnicodeDecodeError in distutils.core.setup when version is unicode

New submission from Jason R. Coombs : If the version or name passed to distutils.core.setup is unicode, this results in a UnicodeDecodeError. Consider this setup.py: from distutils.core import setup setup( name=u'issue13381', version=u'1.0', modules=['setup.py'], ) Run

[issue13309] test_time fails: time data 'LMT' does not match format '%Z'

Antoine Pitrou added the comment: > Has it been reported? Yes, in http://sourceware.org/bugzilla/show_bug.cgi?id=13401 -- ___ Python tracker ___ ___

[issue13368] Possible problem in documentation of module subprocess, method send_signal

Eli Bendersky added the comment: Brian, I see this text (along with the implementation) was added by you in 60197:0ab89e8bdedc Could you state your opinion on this issue? -- nosy: +brian.curtin ___ Python tracker

[issue13239] Remove <> operator from Grammar/Grammar

Eli Bendersky added the comment: Attaching a patch with a clarifying comment in Grammar/Grammar. Should be enough for now? -- keywords: +patch Added file: http://bugs.python.org/file23656/issue13239.patch ___ Python tracker

[issue13191] Typo in argparse documentation

Changes by Eli Bendersky : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13191] Typo in argparse documentation

Roundup Robot added the comment: New changeset 61976390763f by Eli Bendersky in branch '3.2': Issue #13191: typo in argparse docs http://hg.python.org/cpython/rev/61976390763f New changeset edf944ab87c5 by Eli Bendersky in branch 'default': Issue #13191: typo in argparse docs http://hg.python.o

[issue13378] Change the variable "nsmap" from global to instance (xml.etree.ElementTree)

Stefan Behnel added the comment: Reading the proposed patch, I must agree that it makes more sense in ElementTree to support this as a serialiser feature. ET's tree model doesn't have a notion of prefixes, whereas it's native to lxml.etree. Two major advantages of putting this into the serial

[issue13365] str.expandtabs documentation is wrong

Eli Bendersky added the comment: Committed. Thanks for contributing. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs

[issue13365] str.expandtabs documentation is wrong

Roundup Robot added the comment: New changeset 84f803fdc0d2 by Eli Bendersky in branch '3.2': Issue #13365: correct an error in the documentation of str.expandtabs http://hg.python.org/cpython/rev/84f803fdc0d2 New changeset 25191fe10da9 by Eli Bendersky in branch 'default': Issue #13365: correc