[issue13365] str.expandtabs documentation is wrong
Roundup Robot devn...@psf.upfronthosting.co.za 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: correct an error in the documentation of str.expandtabs. Patch by John Feuerstein http://hg.python.org/cpython/rev/25191fe10da9 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13365 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13365] str.expandtabs documentation is wrong
Eli Bendersky eli...@gmail.com added the comment: Committed. Thanks for contributing. -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13365 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13378] Change the variable nsmap from global to instance (xml.etree.ElementTree)
Stefan Behnel sco...@users.sourceforge.net 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 serialiser are: 1) cET doesn't have to be modified, and 2) it does not require additional memory to store the nsmap reference on each Element. The latter by itself is a very valuable property, given that cET aims specifically at a low memory overhead. I see a couple of drawbacks: 1) it only supports the case that namespaces are globally defined. The implementation cannot handle the case that local namespaces should only be defined in subtrees, or that prefixes are being reused. This is no real restriction because globally defined namespaces are usually just fine. It's more of an inconvenience in some cases, such as multi-namespace languages like SOAP or WSDL+XSD, where namespaces are commonly declared on the subtree where they start being used. 2) lxml.etree cannot support this because it keeps the prefixes in the tree nodes and uses them on serialisation. This cannot easily be overridden because the serialiser is part of libxml2. I didn't see in the patch how (or if?) the prefix redefinition case is handled. Given that prefixes are always defined globally, it would be nice if this only resulted in an error if two namespaces that are really used in the document map to the same prefix, not always when the namespace dict is redundant by itself. Also note that it's good to be explicit about the keyword arguments that a function accepts. It aids when help(tostring) tells you directly what you can pass in, instead of just printing **kw. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13378 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13191] Typo in argparse documentation
Roundup Robot devn...@psf.upfronthosting.co.za 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.org/cpython/rev/edf944ab87c5 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13191 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13191] Typo in argparse documentation
Changes by Eli Bendersky eli...@gmail.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13191 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13239] Remove operator from Grammar/Grammar
Eli Bendersky eli...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue13239 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13368] Possible problem in documentation of module subprocess, method send_signal
Eli Bendersky eli...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue13368 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13309] test_time fails: time data 'LMT' does not match format '%Z'
Antoine Pitrou pit...@free.fr added the comment: Has it been reported? Yes, in http://sourceware.org/bugzilla/show_bug.cgi?id=13401 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13309 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13383] UnicodeDecodeError in distutils.core.setup when version is unicode
New submission from Jason R. Coombs jar...@jaraco.com: 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 it with python2.7 setup.py sdist --format gztar and you'll get the following: C:\Python\lib\distutils\dist.py:267: UserWarning: Unknown distribution option: 'modules' warnings.warn(msg) running sdist running check warning: check: missing required meta-data: url warning: check: missing meta-data: either (author and author_email) or (maintainer and maintainer_email) must be supplied warning: sdist: manifest template 'MANIFEST.in' does not exist (using default file list) warning: sdist: standard file not found: should have one of README, README.txt writing manifest file 'MANIFEST' copying files to foo-1.0... copying setup.py - foo-1.0 Creating tar archive Traceback (most recent call last): File C:\Users\jaraco\bugs\setup.py, line 6, in module modules=['setup.py'], File C:\Python\lib\distutils\core.py, line 152, in setup dist.run_commands() File C:\Python\lib\distutils\dist.py, line 953, in run_commands self.run_command(cmd) File C:\Python\lib\distutils\dist.py, line 972, in run_command cmd_obj.run() File C:\Python\lib\distutils\command\sdist.py, line 168, in run self.make_distribution() File C:\Python\lib\distutils\command\sdist.py, line 451, in make_distribution owner=self.owner, group=self.group) File C:\Python\lib\distutils\cmd.py, line 392, in make_archive owner=owner, group=group) File C:\Python\lib\distutils\archive_util.py, line 237, in make_archive filename = func(base_name, base_dir, **kwargs) File C:\Python\lib\distutils\archive_util.py, line 101, in make_tarball tar = tarfile.open(archive_name, 'w|%s' % tar_compression[compress]) File C:\Python\lib\tarfile.py, line 1687, in open _Stream(name, filemode, comptype, fileobj, bufsize), File C:\Python\lib\tarfile.py, line 431, in __init__ self._init_write_gz() File C:\Python\lib\tarfile.py, line 459, in _init_write_gz self.__write(self.name + NUL) File C:\Python\lib\tarfile.py, line 475, in __write self.buf += s UnicodeDecodeError: 'ascii' codec can't decode byte 0x8b in position 1: ordinal not in range(128) Since tarfile doesn't support unicode filenames, distutils should encode the generated filename. issue8396 suggests encoding using sys.getfilesystemencoding(). -- assignee: tarek components: Distutils messages: 147427 nosy: eric.araujo, jason.coombs, tarek priority: normal severity: normal status: open title: UnicodeDecodeError in distutils.core.setup when version is unicode versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13383 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13383] UnicodeDecodeError in distutils.core.setup when version is unicode
Ezio Melotti ezio.melo...@gmail.com added the comment: This is a duplicate of #11638. -- nosy: +ezio.melotti resolution: - duplicate stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13383 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11638] python setup.py sdist crashes if version is unicode
Jason R. Coombs jar...@jaraco.com 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 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11638 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13237] subprocess docs should emphasise convenience functions
Nick Coghlan ncogh...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue13237 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13349] Uninformal error message in index() and remove() functions
Nick Coghlan ncogh...@gmail.com 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, there's also a reason why IGNORE_EXCEPTION_DETAIL is an available doctest option. -- nosy: +ncoghlan ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13349 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3974] collections.namedtuple uses exec to create new classes
Changes by Giampaolo Rodola' g.rod...@gmail.com: -- nosy: +giampaolo.rodola ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3974 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3974] collections.namedtuple uses exec to create new classes
Changes by Florent Xicluna florent.xicl...@gmail.com: -- nosy: +flox ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3974 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13368] Possible problem in documentation of module subprocess, method send_signal
Brian Curtin br...@python.org 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 exactly CTRL_C_EVENT and CTRL_BREAK_EVENT, as this uses GenerateConsoleCtrlEvent which only works with those two values. As the documentation states, anything other than those two constants is sent to TerminateProcess. If you call os.kill with signal.SIGTERM, it would kill the process with return code 15. I will look into adjusting the text a little, and I also need to look into the tests. I currently have CTRL_C_EVENT tests skipped, probably because I am passing the wrong process stuff as he mentioned. I had it working at some point, but I may have generalized it too far. -- assignee: docs@python - brian.curtin components: +Windows stage: - needs patch type: - behavior versions: +Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13368 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13191] Typo in argparse documentation
Roundup Robot devn...@psf.upfronthosting.co.za 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 rep...@bugs.python.org http://bugs.python.org/issue13191 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 adapted from [1]:
def escape_glob(path):
transdict = {
'[': '[[]',
']': '[]]',
'*': '[*]',
'?': '[?]',
}
rc = re.compile('|'.join(map(re.escape, transdict)))
return rc.sub(lambda m: transdict[m.group(0)], path)
[1] http://www.daniweb.com/software-development/python/code/216636
--
components: +Library (Lib)
nosy: +flacs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8402
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8402] glob returns empty list with [ character in the folder name
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8402 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13161] problems with help() documentation of __i*__ operators
Roundup Robot devn...@psf.upfronthosting.co.za 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 rep...@bugs.python.org http://bugs.python.org/issue13161 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13161] problems with help() documentation of __i*__ operators
Roundup Robot devn...@psf.upfronthosting.co.za 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*__ operators. Closes #13161 http://hg.python.org/cpython/rev/d58de3e9870a -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13161 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13161] problems with help() documentation of __i*__ operators
Changes by Eli Bendersky eli...@gmail.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13161 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13384] Unnecessary __future__ import in random module
New submission from Robert Xiao nneon...@gmail.com: 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/python3.2/random.py 2011-11-11 11:11:11.0 -0400 @@ -36,7 +36,6 @@ -from __future__ import division from warnings import warn as _warn from types import MethodType as _MethodType, BuiltinMethodType as _BuiltinMethodType from math import log as _log, exp as _exp, pi as _pi, e as _e, ceil as _ceil -- components: Library (Lib) messages: 147437 nosy: nneonneo priority: normal severity: normal status: open title: Unnecessary __future__ import in random module versions: Python 3.2, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13384] Unnecessary __future__ import in random module
Roundup Robot devn...@psf.upfronthosting.co.za 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 rep...@bugs.python.org http://bugs.python.org/issue13384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13384] Unnecessary __future__ import in random module
Changes by Brian Curtin br...@python.org: -- assignee: - brian.curtin nosy: +brian.curtin resolution: - fixed stage: - committed/rejected status: open - closed type: - behavior versions: -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10854] Output .pyd name in error message of ImportError when DLL load fails
Brian Curtin br...@python.org 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 rep...@bugs.python.org http://bugs.python.org/issue10854 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13309] test_time fails: time data 'LMT' does not match format '%Z'
Roundup Robot devn...@psf.upfronthosting.co.za 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 rep...@bugs.python.org http://bugs.python.org/issue13309 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13309] test_time fails: time data 'LMT' does not match format '%Z'
Florent Xicluna florent.xicl...@gmail.com 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 tracker rep...@bugs.python.org http://bugs.python.org/issue13309 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Roundup Robot devn...@psf.upfronthosting.co.za 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 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Changes by Eli Bendersky eli...@gmail.com: -- status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13385] Add an explicit re.NOFLAGS flag value to the re module
New submission from Eli Bendersky eli...@gmail.com: 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 simple re.NOFLAGS constant to the 're' module with the value of 0, and use it in the documentation instead of plain 0. It's a simple change that won't break anything and may provide better readability for some code, as well as remove the need for plain integer references in the documentation. See also issues #11957 and #12875. Adding to nosy people taking part in discussion of the aforementioned issue. If you're not interested, please remove yourself - I apologize in advance. -- components: Library (Lib), Regular Expressions messages: 147443 nosy: eli.bendersky, eric.araujo, eric.smith, ezio.melotti, terry.reedy priority: normal severity: normal status: open title: Add an explicit re.NOFLAGS flag value to the re module versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13385 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13385] Add an explicit re.NOFLAGS flag value to the re module
Eric V. Smith e...@trueblade.com 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. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13385 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Amaury Forgeot d'Arc amaur...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Georg Brandl ge...@python.org added the comment: No, it's not. -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13239] Remove operator from Grammar/Grammar
Brett Cannon br...@python.org added the comment: I think the clarification should be enough. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13239 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13385] Add an explicit re.NOFLAGS flag value to the re module
Antoine Pitrou pit...@free.fr 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 rep...@bugs.python.org http://bugs.python.org/issue13385 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13384] Unnecessary __future__ import in random module
Raymond Hettinger raymond.hettin...@gmail.com added the comment: I thought we had a policy that future imports would never be removed. -- nosy: +rhettinger status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13384] Unnecessary __future__ import in random module
Brian Curtin br...@python.org 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 rep...@bugs.python.org http://bugs.python.org/issue13384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13385] Add an explicit re.NOFLAGS flag value to the re module
Ezio Melotti ezio.melo...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue13385 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12988] IDLE on Win7 crashes when saving to Documents Library
Changes by Cody C cca...@gmail.com: -- type: - crash ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12988 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12988] IDLE on Win7 crashes when saving to Documents Library
Cody C cca...@gmail.com added the comment: Still an issue as of 11/11/11. -- nosy: +Cody.C ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12988 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13384] Unnecessary __future__ import in random module
Benjamin Peterson benja...@python.org 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 rep...@bugs.python.org http://bugs.python.org/issue13384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12988] IDLE on Win7 crashes when saving to Documents Library
Changes by Ned Deily n...@acm.org: -- nosy: +amaury.forgeotdarc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12988 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13193] test_packaging and test_distutils failures
Roundup Robot devn...@psf.upfronthosting.co.za 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://hg.python.org/cpython/rev/80d5040f2a78 New changeset 64485e0700ba by Antoine Pitrou in branch 'default': Issue #13193: Fix distutils.filelist.FileList and http://hg.python.org/cpython/rev/64485e0700ba New changeset 557a973709de by Antoine Pitrou in branch '2.7': Issue #13193: Fix distutils.filelist.FileList under Windows. The http://hg.python.org/cpython/rev/557a973709de -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13193 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13384] Unnecessary __future__ import in random module
Raymond Hettinger raymond.hettin...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue13384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13384] Unnecessary __future__ import in random module
Ezio Melotti ezio.melo...@gmail.com 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 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13333] utf-7 inconsistent with surrogates
Ezio Melotti ezio.melo...@gmail.com 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 surrogate pair and then each of the surrogates should be encoded just like any other 16bit code unit. While decoding, it seems reasonable to do the opposite, i.e. recombine the surrogate pair. The RFC doesn't say anything about lone surrogates, but I think that the fact that surrogates are used internally doesn't necessarily mean that the codec should be able to encode/decode them when they are not paired. The other UTF-* codecs reject them, but that's because it is explicitly forbidden by their respective standards. So I'm +1 about recombining them while decoding, and ±0 about allowing lone surrogates. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13385] Add an explicit re.NOFLAGS flag value to the re module
Eli Bendersky eli...@gmail.com 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. Provide a single flag 3. Provide a few flags ORed together The OR (which makes no mathematical sense in this case) is bad enough, but why not provide an easy fix for (1), making it explicit instead of implicit. I think we sometimes forget that not everyone who picks up Python is an old C dog, familiar with these tricks. To newbies for whom Python is the first language, these flags aren't very intuitive to use, I imagine. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13385 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Eli Bendersky eli...@gmail.com 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 -- look at: sniff(sample[, delimiters=None]) or even: class csv.DictReader(csvfile[, fieldnames=None[, restkey=None[, restval=None[, dialect='excel'[, *args, **kwds]) That said, I have absolutely no objections to following an accepted convention. But what is it? I looked around, and found the following in the documentation guide: http://docs.python.org/dev/py3k/documenting/fromlatex.html There is no optional command. Just give function signatures like they should appear in the output: .. function:: open(filename[, mode[, buffering]]) Description. This (taken from the 3.3 guide) mentions the 2.x guideline and doesn't mention default values. So what should I do here? According to Ezio's earlier message, the new style (without brackets) is also being used in Python 2 now. I can do the switch for the 're' module, but can we first get the convention documented somewhere? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13385] Add an explicit re.NOFLAGS flag value to the re module
Ezio Melotti ezio.melo...@gmail.com 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 might not be the best API ever, but that a separate problem. So in my opinion there's nothing to fix about 1. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13385 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Ezio Melotti ezio.melo...@gmail.com 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 conventions and how/where they should be followed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Eli Bendersky eli...@gmail.com added the comment: Ezio, what do you suggest to do regarding *this* issue? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12767] document threading.Condition.notify
Eli Bendersky eli...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue12767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12768] docstrings for the threading module
Eli Bendersky eli...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue12768 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12188] PEP 7 (or guide) add C style policies and explanation
Changes by Eli Bendersky eli...@gmail.com: -- nosy: -eli.bendersky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12188 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11173] Undocumented public APIs in Python 3.2
Changes by Eli Bendersky eli...@gmail.com: -- nosy: -eli.bendersky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11173 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3849] FUD in documentation for urllib.urlopen()
Changes by Eli Bendersky eli...@gmail.com: -- nosy: -eli.bendersky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3849 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10838] subprocess __all__ is incomplete
Changes by Eli Bendersky eli...@gmail.com: -- nosy: -eli.bendersky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10838 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5088] optparse: inconsistent default value for append actions
Changes by Eli Bendersky eli...@gmail.com: -- nosy: -eli.bendersky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5088 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10501] make_buildinfo regression with unquoted path
Changes by Eli Bendersky eli...@gmail.com: -- nosy: -eli.bendersky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10501 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Ezio Melotti ezio.melo...@gmail.com added the comment: I suggest removing the []. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12767] document threading.Condition.notify
Ezio Melotti ezio.melo...@gmail.com 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: +ezio.melotti stage: needs patch - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Eli Bendersky eli...@gmail.com 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 ;-) I suggest to just convert the whole 're' RST page to the new 3.x convention (i.e. model it after the same RST in the default branch). Is this acceptable? If yes, I will submit a patch for review first. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12767] document threading.Condition.notify
Eli Bendersky eli...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue12767 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13386] Document documentation conventions for optional args
New submission from Ezio Melotti ezio.melo...@gmail.com: 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 optional arguments but it doesn't accept keyword arguments, the func([arg1]) notation is used instead. This should apply only to some C functions, for example: str.strip([chars]) The notation func([arg=default]) should never be used, and func([arg]) should be used only when keyword args are not accepted. These rules apply to both Python 2 and Python 3. A thing that is still not clear is what to do in case the default value is a placeholder (like object(), None, -1) and the actual value is then computed in the function. -- assignee: docs@python components: Documentation messages: 147469 nosy: docs@python, eli.bendersky, eric.araujo, ezio.melotti, georg.brandl priority: normal severity: normal stage: needs patch status: open title: Document documentation conventions for optional args versions: Python 2.7, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13386 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12875] backport re.compile flags default value documentation
Ezio Melotti ezio.melo...@gmail.com 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 rep...@bugs.python.org http://bugs.python.org/issue12875 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
