[issue7904] urlparse.urlsplit mishandles novel schemes

Senthil Kumaran added the comment: Fixed in the r78234 and merged back to other branches. I fell back to RFC's definition of scheme, as anything before the ://. I did not see the need to add s3 specifically as a valid scheme type, because s3 itself is not registered a schemetype. So, the fix sh

[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: Patch and documentation merged to the py3k branch (r78233). Work on this is complete. -- resolution: -> accepted stage: -> committed/rejected status: open -> closed type: -> feature request ___ Python tracker

[issue1540] Refleak tests: test_doctest and test_gc are failing

Jeremy Hylton added the comment: One last thought on this bug. The problem is that after we try to delete garbage, we really can't know much about the state of the objects in the finalizers list. If any of the objects that are cleared end up causing a finalizer to run, then any of the objec

[issue7900] posix.getgroups() failure on Mac OS X

Michael Foord added the comment: I'm not seeing the same issue on my Macbook Pro. I can get all this info from my desktop machine (Mac Pro) when I return from PyCon. -- ___ Python tracker _

[issue1540] Refleak tests: test_doctest and test_gc are failing

Jeremy Hylton added the comment: I spent some time to understand the example script today. The specific issue is that a set of objects get put into the list of unreachable objects with finalizers (both Immutable and Finalizer instances). When Cycle's __dict__ is cleared, it also decrefs Imm

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Matthew Barnett added the comment: On a related note, this doesn't work either: >>> "{-1}".format("x", "y", "z") Traceback (most recent call last): File "", line 1, in "{-1}".format("x", "y", "z") KeyError: '-1' It could return "z". It also rejects a leading '+', but that would be opti

[issue2636] Regexp 2.7 (modifications to current re 2.2.2)

Matthew Barnett added the comment: issue2636-20100219.zip is a new version of the regex module. The regex module should give the same results as the re module for backwards compatibility. The ignorecase bug is now fixed. This new version releases the GIL when matching on str and bytes (str a

[issue3132] implement PEP 3118 struct changes

Meador Inge added the comment: Mark, > I think a lot of this discussion needs to go back to python-dev; with > luck, we can get some advice and clarifications from the PEP authors > there. So the next step is to kick off a thread on python-dev summarizing the questions\problems we have com

[issue7250] wsgiref.handlers.CGIHandler caches os.environ, leaking info between requests

Phillip J. Eby added the comment: What sort of test did you have in mind? To test the desired outcome, it seems we'd need to poison os.environ, reload wsgiref.handlers, remove the poison, and then make sure it didn't get in. That seems a bit like overkill (as well as hard to get right), whi

[issue2636] Regexp 2.7 (modifications to current re 2.2.2)

Vlastimil Brom added the comment: Thanks for fixing the argument positions; unfortunately, it seems, there might be some other problem, that makes my code work differently than the builtin re; it seems, in the character classes the ignorcase flag is ignored somehow: >>> regex.findall(r"[ab]",

[issue7963] Misleading error message from object(arg)

New submission from Alexander Belopolsky : >>> object(1) Traceback (most recent call last): File "", line 1, in TypeError: object.__new__() takes no parameters This is misleading because object.__new__() takes one parameter: >>> object.__new__(object) I suggest changing "object.__new__()

[issue2736] datetime needs an "epoch" method

Alexander Belopolsky added the comment: Victor, As you explain in your own documentation, the proposed method is equivalent to ``(time.mktime(self.timetuple()), self.microsecond)``, so all it does is replacing a less than a one-liner. Moreover, I am not sure time.mktime(self.timetuple()) is

[issue7961] Py3k: decoding empty bytestring with invalid encoding throws no error

Ori Avtalion added the comment: Ignoring the custom utf-8/latin-8 conversion functions, the actual checking if a codec exists is done in Python/codecs.c's PyCodec_Decode. Is that where I should move the aforementioned optimization to? Is it safe to assume that the decoded object is always a st

[issue7961] Py3k: decoding empty bytestring with invalid encoding throws no error

Mark Dickinson added the comment: And PyUnicode_Decode doesn't look up the encoding in the registry either: that's somewhere in PyCodec_Decode. I'm going to butt out now and leave this to those who know the code better. :) -- ___ Python tracker <

[issue7961] Py3k: decoding empty bytestring with invalid encoding throws no error

Mark Dickinson added the comment: I take that back: test_codecs_errors isn't the right function to add these tests to. I actually don't see any current tests for invalid codecs. Part of the problem would be coming up with an invalid codec name in the first place: as I understand it, new c

[issue7961] Py3k: decoding empty bytestring with invalid encoding throws no error

Mark Dickinson added the comment: Thanks for the patch. Rather than remove that optimization entirely, I'd consider pushing it into PyUnicode_Decode. All tests (whether for the standard library or for the core) go into Lib/test, so that would be the right place. test_codecs_errors in Lib/t

[issue1726687] Bug found in datetime for Epoch time = -1

Alexander Belopolsky added the comment: I wonder: with year bounds being checked in gettmarg() and mktime accepting arbitrary values for the rest of the tm structure members (at least it appears to on my Mac), is it possible trigger "mktime argument out of range"? If it is possible, then a un

[issue7961] Py3k: decoding empty bytestring with invalid encoding throws no error

Ori Avtalion added the comment: OK. The attached patch removes the empty string check before decoding. I'm not sure where tests should go, since I can only find them in Lib/test/ and this is not a library change. -- keywords: +patch Added file: http://bugs.python.org/file16254/decode

[issue7434] pprint doesn't know how to print a namedtuple

Raymond Hettinger added the comment: Will ponder this a bit more but will likely close this specific request (leaving open the possibility of a more general rewrite of pprint). -- assignee: -> rhettinger priority: -> low versions: +Python 2.7, Python 3.2 -Python 2.6

[issue7961] Py3k: decoding empty bytestring with invalid encoding throws no error

Mark Dickinson added the comment: Specifically, the behaviour comes from an early check for empty strings in the PyUnicode_FromEncodedObject function: /* Convert to Unicode */ if (len == 0) { Py_INCREF(unicode_empty); v = (PyObject *)unicode_empty; } else

[issue7960] test.support.captured_output has invalid docstring example

New submission from Michael Newman : test.support.captured_output is not covered in the online documents: http://docs.python.org/3.1/library/test.html http://docs.python.org/dev/py3k/library/test.html However, it does have a docstring in "C:\Python31\Lib\test\support.py" (see below). The curren

[issue7959] ctypes memory leak

New submission from Thomas Heller : This little script 'ctypes-leak.py' leaks memory: """ import gc from ctypes import * PROTO = WINFUNCTYPE(None) class Test(object): def func(self): pass def __init__(self): self.v = PROTO(self.func) while 1: try: Test()

[issue7956] unittest.Testcase assertDictContainsSubset with integer keys

Michael Foord added the comment: Thanks for reporting this. I can fix this particular error easily by repr'ing the keys. In the process I've found another fun way of killing this assert method: one = ''.join(chr(i) for i in range(255)) two = u'\uFFFD' first = {'foo':

[issue1578269] Add os.symlink() and os.path.islink() support for Windows

Eric Smith added the comment: At the language summit we okay'd using ctypes in the tests for standard lib modules, specifically for this issue. -- ___ Python tracker ___

[issue1540] Refleak tests: test_doctest and test_gc are failing

Jeremy Hylton added the comment: I'm trying to figure out the attached script. If I run Python 3.0, the script doesn't run because of the undefined gc.DEBUG_OBJECTS. If I just remove that, the script runs without error. Does that mean the problem is fixed? Or is running without an error a

[issue7955] TextIOWrapper Buffering Inconsistent Between _io and _pyio

Andrew McNabb added the comment: I would imagine that this would come up in most programs that read data from a pipe or from a socket (which are binary data) and then output to stdout or stderr. I ran across the problem in my first non-trivial port to Python 3, and it seems like a common cas

[issue7955] TextIOWrapper Buffering Inconsistent Between _io and _pyio

Antoine Pitrou added the comment: I agree this deserves documentation. I'm not convinced it's a common need, though. Usually you either use stdin/stdout in binary mode or in text mode, but you don't interleave both quite frequently. -- assignee: -> georg.brandl components: +Documenta

[issue7955] TextIOWrapper Buffering Inconsistent Between _io and _pyio

Andrew McNabb added the comment: This seems like a common need (particularly for stdout and stderr), and setting `stdout._CHUNK_SIZE = 1` is relying on an implementation detail. 1) Can the documentation for TextIOWrapper be updated to clearly describe this extra buffering (how often buffer.wr

[issue5839] RegOpenKeyEx key failed on Vista 64Bit with return 2

Martin v. Löwis added the comment: Closing because of lack of feedback. -- nosy: +loewis resolution: -> out of date status: open -> closed ___ Python tracker ___ ___

[issue6040] bdist_msi does not deal with pre-release version

Martin v. Löwis added the comment: The problem is that the version number goes into the MSI ProductVersion property, which MUST be numeric, or else Windows will refuse to install the package. So this is not just an arbitrary choice (at least not by bdist_msi). I'm not sure how a strictly nume

[issue7958] test_platform failure on OS X 10.6

Ronald Oussoren added the comment: This test seems to trigger an issue in site.py, adding '-v' to the code that starts the interpreter in test_platform.py gives the following output (amongst a lot more text that doesn't seem to be relevant): 'import site' failed; traceback: Traceback (most re

[issue7957] Tutorial issue regarding the sys module

Lucian Ursu added the comment: Then it must be an issue with my Python. This is what I get. >>> import sys >>> dir(sys) ['__displayhook__', '__doc__', '__excepthook__', '__name__', '__package__', '__stderr__', '__stdin__', '__stdout__', '_clear_type_cache', '_current_frames', '_getframe', 'ap

[issue7957] Tutorial issue regarding the sys module

Georg Brandl added the comment: They exist only in interactive mode. They won't be present if you do e.g. python -c "import sys; print dir(sys)" -- resolution: -> wont fix status: open -> closed ___ Python tracker

[issue7958] test_platform failure on OS X 10.6

New submission from Mark Dickinson : With a 64-bit debug non-framework builds of the trunk and py3k, on OS X 10.6, I'm consistently getting the following failure in test_platform: trunk dickinsm$ ./python.exe Lib/test/regrtest.py -uall test_platform test_platform [18064 refs] 'import site' fail

[issue7957] Tutorial issue regarding the sys module

Ronald Oussoren added the comment: That's odd, they should exist and do for me: Python 2.6.4 (r264:75821M, Oct 27 2009, 19:48:32) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.ps1 '>>> ' >>> sys.ps2 '

[issue7957] Tutorial issue regarding the sys module

New submission from Lucian Ursu : Hello, I've discovered an issue while reading the Python tutorial. In chapter 6.2. "Standard Modules", the tutorial mentions the "sys" module and two of its attributes, ps1='<<<' and ps2='...'. The problem is I can't find these attributes in my version of Pyt

[issue7633] decimal.py: type conversion in context methods

Mark Dickinson added the comment: Tweaked some doctests in r78218: - add integer argument doctest for logical_invert - fix integer literals with a leading zero for the other logical_*** methods, since they're illegal in Python 3. Merged to py3k in r78219. Thanks, everyone! -- resol

[issue6760] patch to subprocess docs to better explain Popen's 'args' argument

Christoph Neuroth added the comment: As recommended by eric.smith on #7950, I'd like to suggest further extending the documentation to include a security warning about (quite easily) possible code injection bugs when using the shell=True parameter (similar to other places in the documentation

[issue7950] subprocess.Popen documentation should contain a good warning about the security implications when using shell=True

Christoph Neuroth added the comment: Good idea :) -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue7950] subprocess.Popen documentation should contain a good warning about the security implications when using shell=True

Eric Smith added the comment: If you want to generate some more discussion, I suggest you close this issue and reopen the other one, since that has more people on the nosy list. -- ___ Python tracker _

[issue7950] subprocess.Popen documentation should contain a good warning about the security implications when using shell=True

Christoph Neuroth added the comment: You're right, that has been improved in regard to how you can do it instead. However, I still think it lacks to mention the security risk involved - compare this to e.g. os.tempnam(), which has a warning in a red box. -- status: closed -> open ___

[issue5604] imp.find_module() mixes UTF8 and MBCS

Ezio Melotti added the comment: Also the test has a few problems: 1) the keys of known_locales are lowercase, but locale_encoding = locale.getpreferredencoding() can return uppercase encodings (e.g. UTF-8); 2) this masks another error: the b'\xe4' is not a valid utf-8 byte and it can be decode

[issue7633] decimal.py: type conversion in context methods

Stefan Krah added the comment: It looks good (I agree on number_class), but I'd change these: - Add raiseit=True to context.copy_decimal() - Remove wrong comment from context.is_infinite() - Add _convert_other(a, raiseit=True) to context.logical_invert() - More whitespace in test_dec

[issue7942] Inconsistent error types/messages for __len__ (and __nonzero__) between old and new-style classes

Paul Boddie added the comment: Actually, in the issue reported, the initial problem occurs in the evaluation of an object in a boolean context (and the subsequent problem occurs with an explicit len invocation): http://www.selenic.com/pipermail/mercurial/2010-February/030066.html Presumably

[issue7956] unittest.Testcase assertDictContainsSubset with integer keys

New submission from Michael Newman : The attached example unit test file shows that assertDictContainsSubset cannot handle error messages that need to show integer keys. Below is the output of the test suite, where "test_mixed_keys_fail" has an error (code mistake), while "test_text_keys_fail"

[issue5604] imp.find_module() mixes UTF8 and MBCS

Florent Xicluna added the comment: Still an issue for some buildbot: http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/1487 http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/1491 It is loosely related with #7712, because now the tests are run in TEM

[issue7712] Add a context manager to change cwd in test.test_support and run the test suite in a temp dir.

Ezio Melotti added the comment: Ported to py3k in r78214. I will think about the cleanups later, they are not so important right now. -- ___ Python tracker ___ _