[issue17028] launcher does not read shebang line when arguments are given
Vinay Sajip added the comment: A test would also be nice :-) I do test the launcher in a standalone environment, but it's not straightforward to test in a standard build or buildbot environment. For example, it needs 4 sets of Python (Python 2.x and 3.x, 32-bit and 64-bit builds for each) setup in the Windows registry. The test script I use is at https://bitbucket.org/vinay.sajip/pylauncher/src/tip/tests.py -- versions: +Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17028 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15182] find_library_file() should try to link
Jeroen Demeyer added the comment: Sorry for the late answer, but yes: I found this out using an actual compilation. I must admit it was in a bit of an usual situation (32-bit userspace on a mixed 32/64-bit mutilib installation), but most other software packages have no problems configuring correctly in such a situation. I can imagine that it's not a trivial change and would require some redesign. Some more context: this was discovered when building Python as part of Sage, see http://trac.sagemath.org/sage_trac/ticket/12725 for the downstream bug report. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15182 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13590] extension module builds fail with python.org OS X installers on OS X 10.7 and 10.6 with Xcode 4.2
Roundup Robot added the comment: New changeset 1d061f83a6bf by Ned Deily in branch '2.7': Issue #13590: OS X Xcode 4 - improve support for universal extension modules http://hg.python.org/cpython/rev/1d061f83a6bf New changeset 502b139b3b19 by Ned Deily in branch '3.2': Issue #13590: OS X Xcode 4 - improve support for universal extension modules http://hg.python.org/cpython/rev/502b139b3b19 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13590 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13590] extension module builds fail with python.org OS X installers on OS X 10.7 and 10.6 with Xcode 4.2
Ned Deily added the comment: Backports committed for 2.7 (2.7.4) and 3.2 (3.2.4). Note that, although the uploaded review patches also included backported changes to ./configure to improve defaults for building Python itself under Xcode 4, I decided not to commit them here as they might introduce a small incompatibility and are more directly associated with Issue11485. -- resolution: - fixed stage: commit review - committed/rejected status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13590 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17063] assert_called_with could be more powerful if it allowed placeholders
Antoine Pitrou added the comment: I think a better possibility would be to return an indexable match object (as bit like re match objects): my_mock(1, someobj(), bar=someotherobj()): match = my_mock.assert_called_with( 1, ANY, bar=ANY) self.assertIsInstance(match[0], someobj) self.assertIsInstance(match['bar'], someotherobj) It's a *little* cumbersome, but not something I do very often and not much extra code. I'm not sure that having assert_called_with return objects is an intuitive API either. It has happened to me quite a bit in the latest days :-) assert_called_with returning something may fall in the not very pure category, but we already have assertRaises and friends returning a context manager, and it has proved quite practical. Also, your proposed workaround wouldn't work for assert_any_call(). Perhaps we should wait for other people to chime in. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17063 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17089] Expat parser parses strings only when XML encoding is UTF-8
New submission from Serhiy Storchaka: xmlparser.Parse() works with string data only if XML encoding is utf-8 (or ascii). Examples: import xml.parsers.expat parser = xml.parsers.expat.ParserCreate() content = [] parser.CharacterDataHandler = content.append parser.Parse(?xml version='1.0' encoding='utf-8'?tag\xb5/tag) 1 content ['µ'] parser = xml.parsers.expat.ParserCreate() content = [] parser.CharacterDataHandler = content.append parser.Parse(?xml version='1.0' encoding='iso8859'?tag\xb5/tag) 1 content ['µ'] parser = xml.parsers.expat.ParserCreate() content = [] parser.CharacterDataHandler = content.append parser.Parse(?xml version='1.0' encoding='utf-16'?tag\xb5/tag) Traceback (most recent call last): File stdin, line 1, in module xml.parsers.expat.ExpatError: encoding specified in XML declaration is incorrect: line 1, column 30 This affects all other modules which works with XML: xml.sax, xml.dom.minidom, xml.dom.pulldom, xml.etree.ElementTree. Here is a patch which fixes parsing string data with non-UTF-8 XML. -- assignee: serhiy.storchaka components: Extension Modules, Unicode, XML files: pyexpat_parse_str.patch keywords: patch messages: 181014 nosy: ezio.melotti, serhiy.storchaka priority: normal severity: normal stage: patch review status: open title: Expat parser parses strings only when XML encoding is UTF-8 type: behavior versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 Added file: http://bugs.python.org/file28916/pyexpat_parse_str.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17089 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2175] Expat sax parser silently ignores the InputSource protocol
Changes by Serhiy Storchaka storch...@gmail.com: -- dependencies: +Expat parser parses strings only when XML encoding is UTF-8 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2175 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2174] xml.sax.xmlreader does not support the InputSource protocol
Changes by Serhiy Storchaka storch...@gmail.com: -- dependencies: +Expat parser parses strings only when XML encoding is UTF-8 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2174 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1483] xml.sax.saxutils.prepare_input_source ignores character stream in InputSource
Changes by Serhiy Storchaka storch...@gmail.com: -- dependencies: +Expat parser parses strings only when XML encoding is UTF-8 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1483 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10590] Parameter type error for xml.sax.parseString(string, ...)
Changes by Serhiy Storchaka storch...@gmail.com: -- dependencies: +Expat parser parses strings only when XML encoding is UTF-8 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10590 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12681] unittest expectedFailure could take a message argument like skip does
Changes by Adam Collard adam.coll...@gmail.com: -- nosy: +adam-collard ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12681 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected
Changes by Adam Collard adam.coll...@gmail.com: -- nosy: +adam-collard ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9495 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11485] Default SDK value on MacOSX needs changing
Ned Deily added the comment: For 3.3.0, ./configure (configure.ac) was modified in 688d48e434e4 for Issue13590 to use more appropriate defaults for universal builds on newer releases. In particular, --enable-universalsdk=yes uses the Xcode default SDK (as returned by xcodebuild) instead of the 10.4u SDK (not included with Xcode 4), --with-universal-archs now defaults to intel if ppc support is not available, and MACOSX_DEPLOYMENT_TARGET defaults to the OS level for 10.6 and newer systems (rather than using 10.4 or 10.3 by default). It also attempts to avoid building Python with deprecated and problematic Apple llvm-gcc compiler, using clang instead. The defaults can be overridden by providing explicit arguments and/or environment variables to ./configure (--enable-universalsdk, --with-universal-archs, CC, MACOSX_DEPLOYMENT_TARGET). While not 100% perfect, the 3.3 changes give good defaults for nearly all common universal build configurations on 10.4 through 10.8. 2.7.x and 3.2.x have the same problems; attached are patches that backport the 3.3 configure changes to them. However, they do introduce a potential incompatibility. Currently, 2.7 and 3.2 initial configures set MACOSX_DEPLOYMENT_TARGET by default to 10.4 (10.3 on a PPC system) for non-universal builds or 32-bit universal builds and to 10.5 for other universal builds. For 3.3, those values are still used for 10.4 and 10.5 systems; for 10.6 and later systems, the default deployment target is now the OS level itself (10.6 for builds on 10.6, etc). Changing the default deployment target for more recent systems has some benefits: the most obvious is that readline support linking with the system BSD libedit is now enabled by default. The potential incompatibility is that the deployment target value is used by distutils.util.get_platform() to form the platform name which is used for bdist names (like eggs) and the lib build directory for the standard library build. While I haven't ve rified that this is the case, if you've built Python 2.7.2, say, from source on 10.6+ and installed some extension modules with Distutils, then would build from a new release with the proposed patches and install to the existing install location without reinstalling the extension modules, there might be a chance of unexpected incompatibilities between the old extension module (built to an older deployment target) and the upgraded interpreter. Perhaps somewhat more likely is that an extension module binary distribution available on PyPI was available for the old deployment target (10.4) but not for the new target (10.6). Also, it is possible that differences in behavior might be introduced by a change in default compiler. All of these potential incompatibilities can be avoided by overriding the changed defaults, either at Python build time with arguments to ./configure or at extension module build time with environment variables or Distutils config files. Introducing such changes is clearly acceptable with a new release, such as 3.3. For existing releases, it can be argued that the newer, more appropriate settings can also be obtained by just overriding the old defaults (Explicit is better than implicit.). The question then is, when the old default behavior no longer makes sense due to changes outside of our control, do the benefits of changing them in a maintenance release outweigh the risk of introducing an incompatibility? If they are applied, some or all of the changes to the Mac/README file should be backported as well. Also, while working on this, I did find one edge case where the ./configure defaults do not produce a buildable configuration. The case is on 10.6 with (the optional) Xcode 4. For universal builds, the test added early in ./configure to determine if ppc is supported doesn't work. Since the correct compiler hasn't been determined yet, the test looks at the architectures in /usr/lib/libSystem.dylib. On 10.6, unfortunately, that (and other libs) is a 3-way universal files (i386, x86_64, and ppc) even in the 10.6 SDK supplied with Xcode 4.2 for 10.6 despite the fact that the compilers provided with 4.x do not support building ppc binaries. The problem shows up right away as the make dies quickly and it is easily fixed by specifying --with-universal-archs=intel. Still, it would be nice to fix that. -- keywords: +patch stage: needs patch - patch review versions: +Python 2.7, Python 3.2 Added file: http://bugs.python.org/file28917/issue11485_backport_27.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11485 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11485] Default SDK value on MacOSX needs changing
Changes by Ned Deily n...@acm.org: Added file: http://bugs.python.org/file28918/issue11485_backport_32.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11485 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17086] backport cross-build patches to the 2.7 branch
Matthias Klose added the comment: config.add and config.sub are needed for the AC_CANONICAL_HOST macro. the patch includes these and the regenerated configure script. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17086 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16904] http.client.HTTPConnection.send double send data
Attila Gerendi added the comment: Renamed the report since it's unsafe for sure. This problem was previously called: Avoid unnecessary and possibly unsafe code from http.client.HTTPConnection.send. Imagine that the data parameter from HTTPConnection it's a file like object but it's not iterable, maybe some custom data wrapper. the if hasattr(data, read): True branch will correctly send out the response then unnecessary continue to: try: self.sock.sendall(data) except TypeError: if isinstance(data, collections.Iterable): for d in data: self.sock.sendall(d) else: raise TypeError(data should be a bytes-like object or an iterable, got %r % type(data)) and crash! -- resolution: - remind title: Avoid unnecessary and possibly unsafe code from http.client.HTTPConnection.send - http.client.HTTPConnection.send double send data type: performance - crash ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16904 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17041] Fix tests for build --without-doc-strings
Stefan Krah added the comment: Serhiy, if you have time, I think it would be nice to get the remaining fix into the upcoming release candidates. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17041 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4844] ZipFile doesn't range check in _EndRecData()
Roundup Robot added the comment: New changeset 32de35f0f877 by Serhiy Storchaka in branch '2.7': Issue #4844: ZipFile now raises BadZipfile when opens a ZIP file with an http://hg.python.org/cpython/rev/32de35f0f877 New changeset 01147e468c8c by Serhiy Storchaka in branch '3.2': Issue #4844: ZipFile now raises BadZipFile when opens a ZIP file with an http://hg.python.org/cpython/rev/01147e468c8c New changeset 46f24a18a4ab by Serhiy Storchaka in branch '3.3': Issue #4844: ZipFile now raises BadZipFile when opens a ZIP file with an http://hg.python.org/cpython/rev/46f24a18a4ab New changeset e406b8bd7b38 by Serhiy Storchaka in branch 'default': Issue #4844: ZipFile now raises BadZipFile when opens a ZIP file with an http://hg.python.org/cpython/rev/e406b8bd7b38 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4844 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17041] Fix tests for build --without-doc-strings
Changes by Michael Foord mich...@voidspace.org.uk: -- nosy: -michael.foord ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17041 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17049] calendar throws UnicodeEncodeError when locale is specified
Roundup Robot added the comment: New changeset af41eca1959e by Serhiy Storchaka in branch '2.7': Issue #17049: Localized calendar methods now return unicode if a locale http://hg.python.org/cpython/rev/af41eca1959e -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17049 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17041] Fix tests for build --without-doc-strings
Roundup Robot added the comment: New changeset df9f8feb7444 by Serhiy Storchaka in branch '2.7': Issue #17041: Fix doctesting when Python is configured with the http://hg.python.org/cpython/rev/df9f8feb7444 New changeset 9c0cd608464e by Serhiy Storchaka in branch '3.2': Issue #17041: Fix doctesting when Python is configured with the http://hg.python.org/cpython/rev/9c0cd608464e New changeset 886f48754f7e by Serhiy Storchaka in branch '3.3': Issue #17041: Fix doctesting when Python is configured with the http://hg.python.org/cpython/rev/886f48754f7e New changeset e6cc582cafce by Serhiy Storchaka in branch 'default': Issue #17041: Fix doctesting when Python is configured with the http://hg.python.org/cpython/rev/e6cc582cafce -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17041 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4844] ZipFile doesn't range check in _EndRecData()
Changes by Serhiy Storchaka storch...@gmail.com: -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4844 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17049] calendar throws UnicodeEncodeError when locale is specified
Serhiy Storchaka added the comment: Committed. Thank you for reports, Robert Xiao and psam. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17049 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17041] Fix tests for build --without-doc-strings
Serhiy Storchaka added the comment: Thank you for review, Stefan Krah. -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17041 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12983] byte string literals with invalid hex escape codes raise ValueError instead of SyntaxError
Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: - serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12983 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14462] In re's named group the name cannot contain unicode characters
Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: docs@python - serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14462 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15881] multiprocessing 'NoneType' object is not callable
Benjamin Peterson added the comment: Philip, if you could backport, that'd be great. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15881 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13169] Regular expressions with 0 to 65536 repetitions raises OverflowError
Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: - serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13169 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17034] Initialization of globals in stringobject.c and bytesobject.c
Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: - serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17034 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16723] io.TextIOWrapper on urllib.request.urlopen terminates prematurely
Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: - serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16723 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17043] Invalid read in test_codecs
Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: - serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17043 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13169] Regular expressions with 0 to 65536 repetitions raises OverflowError
Changes by Brian Curtin br...@python.org: -- nosy: -brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13169 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17034] Initialization of globals in stringobject.c and bytesobject.c
Stefan Krah added the comment: This is mainly about Py_CLEAR(), right? The initializations to NULL should be guaranteed by the C standard. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17034 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13169] Regular expressions with 0 to 65536 repetitions raises OverflowError
Serhiy Storchaka added the comment:
Here are patches for 2.7, 3.2 and updated patch for 3.3+
(test_repeat_minmax_overflow_maxrepeat is changed).
--
Added file: http://bugs.python.org/file28919/re_maxrepeat4-2.7.patch
Added file: http://bugs.python.org/file28920/re_maxrepeat4-3.2.patch
Added file: http://bugs.python.org/file28921/re_maxrepeat4.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13169
___diff -r df9f8feb7444 Lib/sre_compile.py
--- a/Lib/sre_compile.pyThu Jan 31 16:10:15 2013 +0200
+++ b/Lib/sre_compile.pyThu Jan 31 17:18:46 2013 +0200
@@ -13,6 +13,7 @@
import _sre, sys
import sre_parse
from sre_constants import *
+from _sre import MAXREPEAT
assert _sre.MAGIC == MAGIC, SRE module mismatch
diff -r df9f8feb7444 Lib/sre_constants.py
--- a/Lib/sre_constants.py Thu Jan 31 16:10:15 2013 +0200
+++ b/Lib/sre_constants.py Thu Jan 31 17:18:46 2013 +0200
@@ -15,10 +15,6 @@
MAGIC = 20031017
-# max code word in this release
-
-MAXREPEAT = 65535
-
# SRE standard exception (access as sre.error)
# should this really be here?
diff -r df9f8feb7444 Lib/sre_parse.py
--- a/Lib/sre_parse.py Thu Jan 31 16:10:15 2013 +0200
+++ b/Lib/sre_parse.py Thu Jan 31 17:18:46 2013 +0200
@@ -15,6 +15,7 @@
import sys
from sre_constants import *
+from _sre import MAXREPEAT
SPECIAL_CHARS = .\\[{()*+?^$|
REPEAT_CHARS = *+?{
@@ -498,10 +499,18 @@
continue
if lo:
min = int(lo)
+if MAXREPEAT = min = sys.maxsize:
+raise error(the repetition number is too large)
if hi:
max = int(hi)
-if max min:
-raise error, bad repeat interval
+if max min:
+raise error(bad repeat interval)
+if max = MAXREPEAT:
+if max = sys.maxsize:
+raise error(the repetition number is too large)
+max = MAXREPEAT
+if min MAXREPEAT:
+min = MAXREPEAT
else:
raise error, not supported
# figure out which item to repeat
diff -r df9f8feb7444 Lib/test/test_re.py
--- a/Lib/test/test_re.py Thu Jan 31 16:10:15 2013 +0200
+++ b/Lib/test/test_re.py Thu Jan 31 17:18:46 2013 +0200
@@ -1,5 +1,5 @@
from test.test_support import verbose, run_unittest, import_module
-from test.test_support import precisionbigmemtest, _2G
+from test.test_support import precisionbigmemtest, _2G, cpython_only
import re
from re import Scanner
import sys
@@ -847,6 +847,39 @@
self.assertEqual(n, size + 1)
+def test_repeat_minmax_overflow(self):
+# Issue #13169
+string = x * 10
+self.assertEqual(re.match(r.{65535}, string).span(), (0, 65535))
+self.assertEqual(re.match(r.{,65535}, string).span(), (0, 65535))
+self.assertEqual(re.match(r.{65535,}?, string).span(), (0, 65535))
+self.assertEqual(re.match(r.{65536}, string).span(), (0, 65536))
+self.assertEqual(re.match(r.{,65536}, string).span(), (0, 65536))
+self.assertEqual(re.match(r.{65536,}?, string).span(), (0, 65536))
+# 2**128 should be big enough to overflow both SRE_CODE and Py_ssize_t.
+self.assertIsNone(re.match(r.{%d} % 2**128, string))
+self.assertEqual(re.match(r.{,%d} % 2**128, string).span(),
+ (0, 10))
+self.assertIsNone(re.match(r.{%d,}? % 2**128, string))
+self.assertRaises(re.error, re.compile, r.{%d,%d} % (2**129, 2**128))
+
+@cpython_only
+def test_repeat_minmax_overflow_maxrepeat(self):
+try:
+from _sre import MAXREPEAT
+except ImportError:
+self.skipTest('requires _sre.MAXREPEAT constant')
+if MAXREPEAT sys.maxsize:
+self.skipTest('requires _sre.MAXREPEAT = sys.maxsize')
+self.assertIsNone(re.match(r.{%d} % (MAXREPEAT - 1), string))
+self.assertEqual(re.match(r.{,%d} % (MAXREPEAT - 1), string).span(),
+ (0, 10))
+self.assertIsNone(re.match(r.{%d,}? % (MAXREPEAT - 1), string))
+self.assertRaises(re.error, re.compile, r.{%d} % MAXREPEAT)
+self.assertRaises(re.error, re.compile, r.{,%d} % MAXREPEAT)
+self.assertRaises(re.error, re.compile, r.{%d,}? % MAXREPEAT)
+
+
def run_re_tests():
from test.re_tests import tests, SUCCEED, FAIL, SYNTAX_ERROR
if verbose:
diff -r df9f8feb7444 Modules/_sre.c
--- a/Modules/_sre.cThu Jan 31 16:10:15 2013 +0200
+++ b/Modules/_sre.cThu Jan 31 17:18:46 2013 +0200
@@ -524,7 +524,7 @@
Py_ssize_t i;
/* adjust end */
-if (maxcount end - ptr maxcount != 65535)
+if (maxcount end - ptr maxcount != SRE_MAXREPEAT)
[issue17034] Initialization of globals in stringobject.c and bytesobject.c
Serhiy Storchaka added the comment: The initializations to NULL should be guaranteed by the C standard. I don't sure. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17034 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17090] io.TextIOWrapper does not handle UTF-8 encoded streams correctly
New submission from Christoph Rauch:
I have uncovered a strange behavior in io.TextIOWrapper which I think is a bug.
#!/usr/bin/env python
# encoding: utf-8
import csv
import io
raw_file = io.FileIO('utf-8-encoded.csv', 'rb')
stream = io.BufferedReader(raw_file)
stream = io.TextIOWrapper(stream, encoding=UTF-8)
reader = csv.reader(stream, delimiter=;)
cells = 0
for row in reader:
# Cells should contain 4 Unicode characters.
assert all([len(cell.decode('utf-8')) == 4 for cell in row]), row
cells += len(row)
assert cells == 210, cells
This produces a not very useful:
Traceback (most recent call last):
File utf8-textio-test.py, line 15, in module
for row in reader:
UnicodeEncodeError: 'ascii' codec can't encode characters in position 1-4:
ordinal not in range(128)
The only way to let it *not* crash is to set encoding to ascii and errors to
ignore, but this clears out all the characters with ord128, clearly not useful
as well, so I hope this behavior is not intended.
I appended a file with which to test this problem.
--
components: IO
files: utf-8-encoded.csv
messages: 181028
nosy: Christoph.Rauch
priority: normal
severity: normal
status: open
title: io.TextIOWrapper does not handle UTF-8 encoded streams correctly
type: behavior
versions: Python 2.7
Added file: http://bugs.python.org/file28922/utf-8-encoded.csv
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17090
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17034] Use Py_CLEAR() in stringobject.c and bytesobject.c
Stefan Krah added the comment: Yes, it's guaranteed: 6.7.8 Initialization 10) If an object that has automatic storage duration is not initialized explicitly, its value is indeterminate. If an object that has static storage duration is not initialized explicitly, then: - if it has pointer type, it is initialized to a null pointer; - if it has arithmetic type, it is initialized to (positive or unsigned) zero; - if it is an aggregate, every member is initialized (recursively) according to these rules; - if it is a union, the first named member is initialized (recursively) according to these rules. I'm changing the title so that people don't get the impression that anything is wrong with the initialization. The Py_CLEAR() changes are fine of course. -- title: Initialization of globals in stringobject.c and bytesobject.c - Use Py_CLEAR() in stringobject.c and bytesobject.c ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17034 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17090] io.TextIOWrapper does not handle UTF-8 encoded streams correctly
R. David Murray added the comment: As noted in the documentation, the csv module in 2.7 does not handle unicode. You'll have to switch to python3 if you want unicode support in csv. -- nosy: +r.david.murray resolution: - invalid stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17090 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17090] io.TextIOWrapper does not handle UTF-8 encoded streams correctly
Christoph Rauch added the comment: Thanks for the information. Will work around that. Miss-diagnosed the problem. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17090 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17034] Use Py_CLEAR() in stringobject.c and bytesobject.c
Serhiy Storchaka added the comment: Indeed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17034 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7225] fwrite() compiler warnings
Ramchandra Apte added the comment: I'm pretty sure this is invalid now. -- nosy: +ramchandra.apte ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16432] Template strings documentation in Python 3 refers to % substitution in present tense
Ramchandra Apte added the comment: ... as it is not the preferred system. I prefer .format() but I don't think that's true for many people. -- nosy: +ramchandra.apte ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16432 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17091] thread.lock.acquire docstring bug
New submission from Armin Rigo: The docstring of thread.lock.acquire() (or _thread on Python 3) is bogus: it says that if called without argument, the return value is None; it is only if called with a blocking argument that it returns True or False. But since a long time it was always returning a boolean, never None. -- assignee: docs@python components: Documentation keywords: easy messages: 181035 nosy: arigo, docs@python priority: normal severity: normal status: open title: thread.lock.acquire docstring bug versions: Python 2.7, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17091 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4591] 32-bits unsigned user/group identifier
Serhiy Storchaka added the comment: Are there any objections, nitpicks or suggestions? -- assignee: - serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4591 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17092] Disable TIPC in configure
New submission from ddve...@ucar.edu: This is related to Issue17085 and Issue1646 My system is a cluster Red Hat Enterprise Linux Server release 6.2 (Santiago) and it happens to have /usr/include/linux/tipc.h but probably tipc disabled in the kernel for some reasons which I ignore. There is little interest and no time from the sysadministrators to investigate TIPC, or to remove unneeded files or packages. When I configure and build Python 2.7.3, it seems to build correctly. However the test suite crashes as described in Issue17085. Therefore, I want to rebuild Python 2.7.3 with TIPC disabled. Unfortunately, configure seems to ignore all of the followings: ./configure --without-tipc ./configure --without-TIPC HAVE_LINUX_TIPC_H=0 ./configure HAVE_LINUX_TIPC_H=0 ./configure HAVE_LINUX_TIPC_H=0 (for the record, my other configure options are --enable-shared --with-system-expat --prefix=my-path) I also tried to manually editing config.status as follows: --- config.status.orig 2013-01-31 09:24:04.109311726 -0700 +++ config.status 2013-01-31 09:28:28.397660288 -0700 @@ -854,7 +854,7 @@ D[HAVE_SYS_RESOURCE_H]= 1 D[HAVE_NETPACKET_PACKET_H]= 1 D[HAVE_SYSEXITS_H]= 1 -D[HAVE_LINUX_TIPC_H]= 1 +D[HAVE_LINUX_TIPC_H]= 0 D[HAVE_SPAWN_H]= 1 D[HAVE_DIRENT_H]= 1 D[HAVE_TERM_H]= 1 then run it and check that pyconfig.h has #define HAVE_LINUX_TIPC_H 0 (which it did). Running make and make test after this, produces exactly the same issue as described in Issue17085. Is there a way to force configure to ignore TIPC? -- components: Build messages: 181037 nosy: ddve...@ucar.edu priority: normal severity: normal status: open title: Disable TIPC in configure versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16163] Wrong name in Lib/pkgutil.py:iter_importers
Berker Peksag added the comment: Sorry for the delay and thanks for the suggestions Ezio and Nick. Given the lack of proper tests for iter_importers, wouldn't adding a proper test that returns something useful, rather than testing only with a non-existent module be better (this test could be kept, maybe converted to an assertRaises)? I've added a test for iter_importers(). (Note: There's a series of patches from Chris to move the walk_packages test to where it belongs in test_pkgutil, but they won't be applied until after the final 3.2 maintenance release has happened.) Thanks for the info. These patches are in issue 15376, issue 15358, issue 15403 and issue 15415, right? -- Added file: http://bugs.python.org/file28923/issue16163_v3.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16163 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17092] Disable TIPC in configure
Antoine Pitrou added the comment: Why would you disable TIPC? If TIPC crashes the test suite, you probably have a system bug. I would suggest you try to diagnose what happens exactly. (normally, the TIPC tests are skipped if the tipc kernel module isn't loaded) -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17092] Disable TIPC in configure
ddve...@ucar.edu added the comment: Antoine, the exact reason why I want to disable TIPC in configure, is that either the test suite or the TIPC test case or both has/have a bug (not my system). Therefore I suggest that you re-post your comment in Issue17085, and I'll be happy to provide more details that would be off-topic here. However, regardless of my particular needs, disabling TIPC in configure is something useful for a variety of other reasons (e.g. one having a functional TIPC but not wanting to have it enabled in python), and therefore I asked it here. It is customary to have autotools being able to individually select packages that one wants or does not want to use. In fact ./configure --help reports the --without-PACKAGE option which does not work for TIPC and this is the bug of present Issue17092 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17092 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16555] Add es_cu to locale aliases
Berker Peksag added the comment: LGTM. Thanks for the review, Éric. Do you have time to commit the patch? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16555 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2824] zipfile to handle duplicate files in archive
Michael Driscoll added the comment: Whatever became of this? We just stumbled across this bug in our code at work where we accidentally put multiple files of the same name into the zip file and not only does it not overwrite the others, but when you go to access that file name, it grabs the first one that was put in. -- nosy: +michael.driscoll ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2824 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17087] Improve the repr for regular expression match objects
Ezio Melotti added the comment: #13592 is indeed the issue I was thinking about, but apparently that's about _sre.SRE_Pattern, so it's not the same thing. Just showing group(0) should be helpful. Often the interesting group is group(1), so showing only group(0) seems a bit arbitrary. And perhaps the number of groups. If we show only group(0), this might be useful as an indication that there are(n't) other groups. If a string is really long, we can truncate it like reprlib does. That's certainly an option. FWIW I don't usually care about the start/end, and, if included, these values could be included as span=(3,12). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17087 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6972] zipfile.ZipFile overwrites files outside destination path
Changes by Catalin Iacob iacobcata...@gmail.com: -- nosy: +catalin.iacob ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6972 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17093] Make importlib.abc more inheritance-friendly
New submission from Brett Cannon: ABCs, even though they are almost always at the bottom of an inheritance hierarchy, should still do the right thing in the face of being in the middle of an MRO. That means that they should call super() as appropriate. So for methods that return a value, blindly call super(). For methods that do not necessarily return anything (e.g. invalidate_caches()), check if super() as the method and it is callable and if that is true then make the super() call. This is not backwards-compatible as it is new semantics people will rely on, but neither is it a bug but a bad design decision on my part. -- components: Library (Lib) keywords: easy messages: 181044 nosy: brett.cannon priority: low severity: normal stage: test needed status: open title: Make importlib.abc more inheritance-friendly type: behavior versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17093 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17093] Make importlib.abc more inheritance-friendly
Changes by Brett Cannon br...@python.org: -- assignee: - brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17093 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17094] sys._current_frames() reports too many/wrong stack frames
New submission from Stefan Ring: After a fork, the list of thread states contains all the threads from before. It is especially unfortunate that, at least for me, it usually happens that threads created in the forked process reuse the same thread ids, and sys._current_frames will then return wrong stack frames for existing threads because the old entries occur towards the tail of the linked list and overwrite the earlier, correct ones, in _PyThread_CurrentFrames. The attached patch is certainly not the most complete solution, but it solves my problem. With Python 2.7.3 I get: Exception in thread Thread-6: Traceback (most recent call last): File /usr/lib64/python2.7/threading.py, line 551, in __bootstrap_inner self.run() File /usr/lib64/python2.7/threading.py, line 504, in run self.__target(*self.__args, **self.__kwargs) File test-fork-frames.py, line 24, in do_verify assert frame_from_sys is real_frame AssertionError With my patch applied, it passes silently. I can reproduce this on CentOS 6.3 x86_64 as well as Fedora 18 x86_64. -- components: Interpreter Core files: current-frames-cleanup.patch keywords: patch messages: 181045 nosy: Ringding priority: normal severity: normal status: open title: sys._current_frames() reports too many/wrong stack frames type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file28924/current-frames-cleanup.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17094 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17094] sys._current_frames() reports too many/wrong stack frames
Changes by Stefan Ring stefan...@gmail.com: Added file: http://bugs.python.org/file28925/test-fork-frames.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17094 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17076] shutil.copytree failing on xattr-less filesystems (like NFS)
Thomas Wouters added the comment: Updated patch with test. -- Added file: http://bugs.python.org/file28926/shutil.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17076 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17076] shutil.copytree failing on xattr-less filesystems (like NFS)
Changes by Thomas Wouters tho...@python.org: Removed file: http://bugs.python.org/file28898/shutil.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17076 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17076] shutil.copytree failing on xattr-less filesystems (like NFS)
Changes by Thomas Wouters tho...@python.org: Removed file: http://bugs.python.org/file28926/shutil.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17076 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17076] shutil.copytree failing on xattr-less filesystems (like NFS)
Thomas Wouters added the comment: Now really updated the patch. -- Added file: http://bugs.python.org/file28927/shutil.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17076 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17095] Modules/Setup *shared* support broken
New submission from Thomas Wouters: At some point (probably in 3.2) the support for shared modules built using Modules/Setup was broken, for two reasons: - Python no longer considers 'foomodule.so' when looking for a module called 'foo', but Modules/makesetup still appends 'module.so' for a 'foo' module. - Python no longer considers Modules/ to be the exec_prefix (and instead uses what was loaded from the build-info .txt written by setup.py) but the build process still leaves these Modules/Setup-built shared modules in the Modules directory (and it doesn't know about the directory setup.py will make, so it can't really do anything else.) This patch fixes both problems, by making Modules/makesetup name shared library modules 'foo.so' and by adding the Modules subdirectory to sys.path (after the setup.py-provided directory) when running from the build directory. (The existing build process has no problem _installing_ the Modules/Setup-built extension modules, it's just Python that doesn't know how to find them.) -- components: Build files: getpath.diff keywords: patch messages: 181048 nosy: twouters priority: normal severity: normal status: open title: Modules/Setup *shared* support broken versions: Python 3.2, Python 3.3, Python 3.4 Added file: http://bugs.python.org/file28928/getpath.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17095 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17086] backport cross-build patches to the 2.7 branch
Roundup Robot added the comment: New changeset 8ee6d96a1019 by doko in branch '2.7': - Issue #17086: Backport the patches from the 3.3 branch to cross-build http://hg.python.org/cpython/rev/8ee6d96a1019 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17086 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17086] backport cross-build patches to the 2.7 branch
Matthias Klose added the comment: now committed, watching the buildds -- stage: - committed/rejected status: open - pending type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17086 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17093] Make importlib.abc more inheritance-friendly
Changes by Eric Snow ericsnowcurren...@gmail.com: -- nosy: +eric.snow ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17093 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13590] extension module builds fail with python.org OS X installers on OS X 10.7 and 10.6 with Xcode 4.2
Changes by Ned Deily n...@acm.org: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13590 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13592] repr(regex) doesn't include actual regex
Chris Jerdonek added the comment: See also issue 17087 which is essentially the same issue but for match objects. -- nosy: +chris.jerdonek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13592 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17096] the system keyring should be used instead of ~/.pypirc
New submission from Thomas Grainger: Having the password stored in a plain-text configuration file is not great security. A better choice would be to try to use the OS keyring and then fall back to a plaintext file An example implementation of a generic keyring python interface is available at: http://pypi.python.org/pypi/keyring/ -- assignee: eric.araujo components: Distutils2 messages: 181052 nosy: alexis, eric.araujo, graingert, tarek priority: normal severity: normal status: open title: the system keyring should be used instead of ~/.pypirc type: security ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17096 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16809] Tk 8.6.0 introduces TypeError. (Tk 8.5.13 works)
Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16809 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17080] A better error message for float()
Ezio Melotti added the comment: Attached a new patch with tests. I added the quotes around the type and fixed complex() too. -- Added file: http://bugs.python.org/file28929/issue17080-2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17080 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Ezio Melotti added the comment: If there are no comments I'll commit this during the weekend. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6972] zipfile.ZipFile overwrites files outside destination path
Gregory P. Smith added the comment: the patch looks good, thanks! one minor comment in a test but i'll take care of that as i submit. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6972 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17040] Document context manager support for shelf objects
Roundup Robot added the comment: New changeset 935a286b8066 by Ezio Melotti in branch 'default': #17040: document that shelve.open() and the Shelf object can be used as context managers. Initial patch by Berker Peksag. http://hg.python.org/cpython/rev/935a286b8066 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17040 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17040] Document context manager support for shelf objects
Ezio Melotti added the comment: Fixed, thanks for the report and the patch! -- assignee: docs@python - ezio.melotti nosy: +ezio.melotti resolution: - fixed stage: - committed/rejected status: open - closed type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17040 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Chris Jerdonek added the comment: I would like to request again that these changes be proposed and committed in smaller chunks. I have comments of a basic nature that would be much easier to discuss and address in the context of smaller patches. Otherwise, the discussion isn't manageable because too much is up in the air at once. I was waiting for smaller patches before raising these comments. Also, some of my suggestions above weren't addressed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Ezio Melotti added the comment: On the repo I created (https://bitbucket.org/ezio_melotti/devguide-14468) there are separate commits that include smaller changes. The patches attached to this issue are outdated. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16128] hashable documentation error
Roundup Robot added the comment: New changeset 79a021beaf58 by Ezio Melotti in branch '2.7': #16128: clarify that instances of user-defined classes compare equal with themselves. http://hg.python.org/cpython/rev/79a021beaf58 New changeset e84c5cf92b6f by Ezio Melotti in branch '3.2': #16128: clarify that instances of user-defined classes compare equal with themselves. http://hg.python.org/cpython/rev/e84c5cf92b6f New changeset d9255c100971 by Ezio Melotti in branch '3.3': #16128: merge with 3.2. http://hg.python.org/cpython/rev/d9255c100971 New changeset 1890c63f6153 by Ezio Melotti in branch 'default': #16128: merge with 3.3. http://hg.python.org/cpython/rev/1890c63f6153 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Chris Jerdonek added the comment: My understanding is that the commits are all or nothing. In other words, they all need to be reviewed before any are committed. I would like for the patches to be reviewed and committed individually so the review process is more manageable and people can participate more easily. As I commented above, I offered suggestions on how to do this. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16128] hashable documentation error
Ezio Melotti added the comment: I addressed the first comment. The paragraph in datamodel.html looks ok to me, so I left it unchanged. Feel free to reopen the issue if you have a specific suggestion that could improve that section. -- assignee: docs@python - ezio.melotti nosy: +ezio.melotti resolution: - fixed stage: - committed/rejected status: open - closed versions: +Python 2.7, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16128 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Chris Jerdonek added the comment: Also, I would be happy to start that process using the work that you have done. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Ezio Melotti added the comment: Yes, I was planning to collapse them in a single patch and push only that. I don't think they can be further divided. In the moment I add the paragraph about setting up the multiple repos using hg share the old description becomes unnecessary, the instructions needs to be updated, and the FAQs don't need to mention hg share anymore. I made all these things in separate commits to make it easy to review, but they have to be committed together (unless you prefer to have intermediate commits that contained duplicated informations). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Chris Jerdonek added the comment: I see ways that the changes can be proposed and committed incrementally. I can start proposing those. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Ezio Melotti added the comment: I'm not sure what's the point though. The repo on bitbucket provides an easy way to review individual changes, and pushing everything at once prevents history pollution (assuming you consider 8 related changesets as pollution). That's similar to the process we follow for feature branches, except that this is trivial enough that I didn't create a branch. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Chris Jerdonek added the comment: The point is to allow a manageable discussion to take place around points of contention while making forward commit progress along the way. I have suggestions right now, but the current massive batch of changes makes it too unwieldy. The incremental commits I'm proposing wouldn't be pollutive. Each would be forward progress towards what we want with a commit message explaining the change. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14468] Update cloning guidelines in devguide
Ezio Melotti added the comment: The point is to allow a manageable discussion to take place around points of contention That can be done as (possibly inline) comments on bitbucket on the individual commits. while making forward commit progress along the way. I'm not sure how you intend to do that, but feel free to propose what you have in mind. As I see it, there's a bunch of text written assuming that there is a single clone or multiple not shared clones, and all this needs to be replaced and updated. You can probably extract a couple of chunks, but that won't make a difference IMHO. the current massive batch of changes makes it too unwieldy. Maybe you are overestimating it. It's really not so massive: it's 8 changesets, 2 just remove stuff, other 2 just move existing content without adding/removing anything (so there's nothing much to review here). Of the remaining 4 changesets, the first only adds 85 lines, the other 3 change about 20 lines each. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14468 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13756] Python3.2.2 make fail on cygwin
Ezio Melotti added the comment: Is this still an issue on 3.3/3.4? Does the patch still work? -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13756 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13515] Consistent documentation practices for security concerns and considerations
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +christian.heimes type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13515 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9445] Fix undefined symbol errors on VS8.0 build
Ezio Melotti added the comment: Is this issue still valid? -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9445 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
