[issue7939] subprocess: call([arg, arg2], shell=True) vs call(arg+" "+arg2, shell=True)

anatoly techtonik added the comment: You are right - I should read the docs, but one of the outstanding features of Python is that in many cases you can test the code faster than read documentation. =) It would help if ["ls", "-la"] example included third argument thus fully covering the conc

[issue7946] Convoy effect with I/O bound threads and New GIL

David Beazley added the comment: The comment on the CPU-bound workload is valid--it is definitely true that Python 2.6 results will degrade as the workload of each tick is increased. Maybe a better way to interpreter those results is as a baseline of what kind of I/O performance is possible

[issue3132] implement PEP 3118 struct changes

Meador Inge added the comment: Hi All, On Sat, Feb 13, 2010 at 5:07 AM, Mark Dickinson wrote: > > Mark Dickinson added the comment: > > Some of the proposed struct module additions look far from straightforward; > I find that section of the PEP significantly lacking in details and > motivati

[issue7946] Convoy effect with I/O bound threads and New GIL

Antoine Pitrou added the comment: Just a quick test under Linux (on a dual quad core machine): - with iotest.py and echo_client.py both running Python 2.7: 25.562 seconds (410212.450 bytes/sec) - with iotest.py and echo_client.py both running Python 3.2: 28.160 seconds (372362.459 bytes/sec)

[issue7949] idle does not handle dark gtk color schemes

Mathias Panzenböck added the comment: I just noticed that the debugger also suffers from this problem. Doing a quick grep over the source reveals even more places that might cause problems (where only the bg or only the fg color is set). I think in ScrolledList.py the background="white" shoul

[issue7948] Complete your registration to Python tracker -- key yAMyUeuHR9LS2Q86aUUs2GO4rujOhgWH

Changes by Brian Curtin : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue7948] Complete your registration to Python tracker -- key yAMyUeuHR9LS2Q86aUUs2GO4rujOhgWH

New submission from panzi : On 02/17/2010 02:35 AM, Python tracker wrote: > To complete your registration of the user "panzi" with > Python tracker, please do one of the following: > > - send a reply to rep...@bugs.python.org and maintain the subject line as is > (the > reply's additional "Re:"

[issue7005] ConfigParser does not handle options without values

Fred L. Drake, Jr. added the comment: Assigning to myself for handling. Bumping to Python 2.7 / 3.2 since support for this syntax variation is a new feature. -- assignee: -> fdrake versions: +Python 2.7, Python 3.2 -Python 2.6 ___ Python tracker

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

R. David Murray added the comment: In the example you give it seems to me that the message for the new style class is more accurate and useful than the message for the old style class. Looking at your mercurial example, it looks like the problem is the same (len returning a long), and again

[issue5088] optparse: inconsistent default value for append actions

R. David Murray added the comment: I agree with Andrew, but I think the optparse documentation should make it clear that this is what happens with a default value for an 'append' action. It is *implied* by the fact that append says it appends to a list, and default says the value is set befo

[issue7930] pydoc.stripid doesn't strip ID in py25, py26, py31

Ezio Melotti added the comment: Fixed in r78207 (trunk), r78208 (release26-maint), r78209 (py3k) and r78210 (release31-maint). After a short discussion on #python-dev I decided to remove the 'if', because it's not necessary and might creates problems with other implementations. -- res

[issue6472] Update ElementTree with upstream changes

Florent Xicluna added the comment: Update the 2.x patch with the last version uploaded to rietveld (patch set 5). Improved test coverage with upstream tests and tests cases provided by Neil on issue #6232. Note: the patch for 3.x is obsolete. -- Added file: http://bugs.python.org/fil

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

Paul Boddie added the comment: I would have expected a more accurate error message for the new-style class. In the original message which brought this to my attention, the cause was not particularly obvious: http://www.selenic.com/pipermail/mercurial/2010-February/030066.html I concede that

[issue7947] Documentation of math.pow, math.hypot, and complex.__abs__

Mark Dickinson added the comment: Hmm. Looking at the docs, there are a number of revisions that would be useful. For example, the docs mention signaling NaNs, but that doesn't make a lot of sense: Python essentially treats all NaNs as quiet. I'll add this to my to-do list. -- _

[issue7947] Documentation of math.pow, math.hypot, and complex.__abs__

Mark Dickinson added the comment: Thanks for reporting this. Rather than documenting corner cases explicitly, maybe it would be enough to point to the C99 standard: the corner cases for the math functions should (modulo bugs) all follow Annex F of the C standard, while the corner cases for

[issue5088] optparse: inconsistent default value for append actions

Andrew McNabb added the comment: I think that optparse is doing the right thing here. I think that your code example should be changed to: import optparse parser = optparse.OptionParser() parser.add_option("-o", "--option", action = "append") options, args = parser.parse_args() if not

[issue7945] typo in operator.isCallable deprecation warning

Georg Brandl added the comment: No, this is correct. isCallable() was deprecated since 2.0, but the replacement was the builtin callable() until 2.6. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue7946] Convoy effect with I/O bound threads and New GIL

New submission from David Beazley : Background --- In order to multitask with threads, a critical part of the Python interpreter implementation concerns the behavior of I/O operations such as read, write, send, and receive. Specifically, whenever an I/O operation is carried out, the inte

[issue7939] subprocess: call([arg, arg2], shell=True) vs call(arg+" "+arg2, shell=True)

R. David Murray added the comment: I think you should reread the Popen docs carefully :) That example should be: call([sys.executable, 'diff.py', 'oldfile', 'newfile']) And there are examples of that call format in the Popen docs, as well as the explanation of exactly how to format the list

[issue7939] subprocess: call([arg, arg2], shell=True) vs call(arg+" "+arg2, shell=True)

anatoly techtonik added the comment: The last one should be: retcode = call([sys.executable, "diff.py oldfile newfile"]) -- ___ Python tracker ___ ___

[issue7939] subprocess: call([arg, arg2], shell=True) vs call(arg+" "+arg2, shell=True)

anatoly techtonik added the comment: Thanks. That should be enough, although I wouldn't mind against more prominent notice to urge users to go and see Popen parameters. I would also add a second example to allow users see the difference. For instance, how to execute another Python script: re

[issue7944] Use the 'with' statement in conjunction with 'open' throughout test modules

Amaury Forgeot d'Arc added the comment: Please use patches to show where the code changed. (I generated one; it looks good to me) I would like this kind of patches applied to CPython. Looking at the Pypy test suite, the following test files seem easy to update: test_bz2 test_dumbdbm test_mailbo

[issue7945] typo in operator.isCallable deprecation warning

New submission from kenneth dombrowski : The operator documentation @ http://docs.python.org/library/operator.html states for operator.isCallable(obj): "Deprecated since version 2.0: Use isinstance(x, collections.Callable) instead.", I believe this should read since version 2.6 kenn...@dev2 ~

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

Martin v. Löwis added the comment: I fail to see the bug in this report. What did you expect to happen instead? -- nosy: +loewis ___ Python tracker ___ __

[issue1212900] Python segfaults on OpenBSD (tested 3.4 and 3.5)

Changes by Martin v. Löwis : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7846] Fnmatch cache is never cleared during usage

Éric Araujo added the comment: Hi Your rationale makes perfect sense. Perhaps add a comment suggesting it’s ok to change the value. Cheers -- ___ Python tracker ___ __

[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule

Thomas Smith added the comment: I'm also getting segfaults in PyMarshal_ReadLastObjectFromFile in Python 2.6.2 (on Ubuntu Jaunty). It's very sporadic, I've been reproducing it by running a minimal script 100,000 times, and getting a few core dumps. There are several Ubuntu bugreports in var

[issue7939] subprocess: call([arg, arg2], shell=True) vs call(arg+" "+arg2, shell=True)

R. David Murray added the comment: You can't even use call or check_call without referencing the Popen constructor documentation, so I'm not sure what you are advocating, Anatoly. We certainly don't want to repeat the Popen documentation in full for each convenience function, and if we aren'

[issue7931] Interpreter does not terminate if daemonized while running multithreaded

Amaury Forgeot d'Arc added the comment: libc.daemon() calls forks(), which duplicates only the main thread. The other thread does not exists in the forked process, and the interpreter blocks while trying to wait for it... Please use os.fork() instead, it has code to forget the threads created

[issue7944] Use the 'with' statement in conjunction with 'open' throughout test modules

New submission from Dave Fugate : Sprinkled throughout CPython's test modules are snippets of code such as the following taken from 2.7A3's test_old_mailbox.py (line 141): box = mailbox.UnixMailbox(open(self._path, 'r')) The key thing to observe here is the file being opened yet never has i

[issue7943] Memory leak due to circular references in ssl.SSLSocket

New submission from Péter Szabó : Here is how to reproduce the leak in Python 2.6.4 and Python 2.7: import gc import socket import ssl sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM) gc.disable() gc.collect() count0 = gc.get_count()[0] for i in xrange(1000): ssl.SSLS

[issue7939] subprocess: call([arg, arg2], shell=True) vs call(arg+" "+arg2, shell=True)

Brian Curtin added the comment: "This module also defines two shortcut functions" I think given that we say the calls are shortcuts, and that their arguments are the same as Popen, I take that to mean that subprocess.call experiences the same situations as subprocess.Popen. If any change has

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

New submission from Paul Boddie : As noted here: http://www.selenic.com/pipermail/mercurial/2010-February/030068.html This is probably documented somewhere, and there may even be a good reason for the difference, but old-style classes raise TypeError when __len__ returns a non-int, whereas ne

[issue7939] subprocess: call([arg, arg2], shell=True) vs call(arg+" "+arg2, shell=True)

anatoly techtonik added the comment: I still do not agree. There should be a note in call() documentation, because users will waste their time experiencing the bug before reading documentation again. If you can't make something just work without rereading the whole doc - that's not pythonic.

[issue7939] subprocess: call([arg, arg2], shell=True) vs call(arg+" "+arg2, shell=True)

anatoly techtonik added the comment: I can't see changes to subprocess.call() docs in issue #6760. I reopen this bug, because call() definitely need a visible note about this significant behavior. I can not reopen #6760 http://docs.python.org/library/subprocess.html#convenience-functions ---

[issue7939] subprocess: call([arg, arg2], shell=True) vs call(arg+" "+arg2, shell=True)

R. David Murray added the comment: If by "fail" you mean "doesn't execute the command in the way I expected", then I believe you will be enlightened by reading the recent updates to the Popen documentation (see issue 6760). -- nosy: +r.david.murray priority: -> normal resolution: ->

[issue7736] os.listdir hangs since opendir() and closedir() do not release GIL

Nikolaus Rath added the comment: Does this patch still need review? Both Martin and Antoine already commented that the patch is ok, so it'd be great if someone could actually apply it... -- ___ Python tracker

[issue1005895] curses for win32

Jason Tishler added the comment: Sorry, but I don't know. I haven't looked at this issue for almost five years! And when I did, I only looked as far to determine it wasn't Cygwin related. -- ___ Python tracker

[issue7334] ElementTree: file locking in Jython 2.5 (OSError on Windows)

Florent Xicluna added the comment: The patch proposed on msg95349: * need tests * not reviewed (yet) -- keywords: +patch nosy: +flox priority: -> normal stage: -> needs patch title: XML file locking in Jython 2.5 (OSError on Windows) -> ElementTree: file locking in Jython 2.5 (OSEr

[issue5217] testExtractDir (test.test_zipfile.TestWithDirectory) fails when python built with srcdir != builddir

Matthias Klose added the comment: this works with 2.7 alpha3, won't fix for 3.0 -- versions: -Python 2.7, Python 3.0 ___ Python tracker ___ _

[issue4151] Separate build dir broken

Matthias Klose added the comment: current status with 2.7 alpha3: FAIL: test_get_python_inc (distutils.tests.test_sysconfig.SysconfigTestCase) -- Traceback (most recent call last): File "/home/packages/python/2.7/python2.7-2

[issue1212900] Python segfaults on OpenBSD (tested 3.4 and 3.5)

Stefan Krah added the comment: It is a stack overflow, which can be prevented by setting #define Py_DEFAULT_RECURSION_LIMIT 150 in Python/ceval.c. Then the program behaves in the same way as on Linux (i.e. it swallows the RuntimeError somewhere). Recommend closing. -- nosy: +skrah _

[issue7582] [patch] diff.py to use iso timestamp

anatoly techtonik added the comment: Ok. Let's commit it at least to 2.7 - I'll create a separate issue for discussion of unified diff format later. -- ___ Python tracker ___ __

[issue7846] Fnmatch cache is never cleared during usage

Andrew Clegg added the comment: Hi, I used a global name for a couple of reasons: it is consistent with the cache itself and the size of the cache being defined in the same place; and because I wanted to allow the value to be modified by users. I used the leading underscore to give a weak in

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

Ronald Oussoren added the comment: A related question: is this issue present in the 3.x trunk? (BTW: feel free to assign all OSX related issues to me) -- assignee: -> ronaldoussoren ___ Python tracker ___

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

Ronald Oussoren added the comment: Michael: * which configure options do you use? * which xcode version do you use? (this shouldn't be relevant, I'm interested in what causes the dot 1 suffix) * If you use --enable-universalsdk: do you have the 10.4 SDK installed (should be installed in