[issue1643738] Problem with signals in a single-threaded application

Guido van Rossum added the comment: Discussing this with Rhamporyncus (Adam Olson) on #python-dev now. -- assignee: -> gvanrossum nosy: +gvanrossum _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1643738] Problem with signals in a single-threaded application

Guido van Rossum added the comment: Committed revision 59460 to 2.6. Will backport to 2.5 as well. -- resolution: -> accepted _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1643738] Problem with signals in a single-threaded application

Guido van Rossum added the comment: Committed revision 59461 to 2.5. Thanks, Ulisses!! -- status: open -> closed _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: > So, what's the final status of __del__ in py3K? The other bit of leak > is due to _real_close() not being called when a socket is dropped on the > floor (say, you try to connect, fail, and raise the exception back to > the caller, withou

[issue1582] Documentation patch for reversed() and __reversed__()

Guido van Rossum added the comment: Georg, can you handle this? -- assignee: -> georg.brandl nosy: +georg.brandl, gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1583] Patch for signal.set_wakeup_fd

Guido van Rossum added the comment: Thanks! Can you add a doc patch too? Doc/library/signal.rst -- assignee: -> gvanrossum keywords: +py3k versions: +Python 2.6 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: I wonder if Christian Heimes was correct that the ssl object needs GC support? This was part of his patch (which I checked in and then reverted because the other part of it didn't work as advertised). Alternatively, if 's' is involved in a cyc

[issue1583] Patch for signal.set_wakeup_fd

Changes by Guido van Rossum: -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1583> __ ___ Python-bugs-list mailing list Uns

[issue1583] Patch for signal.set_wakeup_fd

Changes by Guido van Rossum: -- keywords: +patch -py3k __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1583> __ ___ Python-bugs-list mailing list Unsubs

[issue1564547] Py_signal_pipe

Guido van Rossum added the comment: Rejected, in favor of #1583 which lets the app choose whether to use a fd or not. We had an extensive #python-dev discussion on this and this time the rejection is irrevocable. -- resolution: -> accepted status: open ->

[issue1564547] Py_signal_pipe

Changes by Guido van Rossum: -- resolution: accepted -> rejected superseder: -> Patch for signal.set_wakeup_fd _ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: Noam, perhaps you can help with this? We checked this in but found a problem: repr(1e5) suddenly returns '1.0'. Can you think of a cause for this? -- status: closed -> open __ Tracker <[EMAIL P

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: > On what platform does it happen? Linux on x86. It seems find on PPC OSX. This suggests it could be a byte order bug. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: (1) Despite Tim's grave language, I don't think we'll need to write our own correctly-rounding float input routine. We can just say that Python won't work correctly unless your float input routine is rounding correctly; a unittest should

[issue1577] shutil.move() does not use os.rename() if dst is a directory

Guido van Rossum added the comment: > Since we already have os.rename, wouldn't it be better for shutil.move() > to be closer to command line 'mv'? I think Facundo's approach should work. I'd rather not do this. It might cause disasters for code that expects the o

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: > > (1a) Perhaps it's better to only do this for Python 3.0, which has a > > smaller set of platforms to support. > > +1 > Does Python depend on a working, valid and non-broken IEEE 754 floating > point arithmetic? Could we

[issue1589] New SSL module doesn't seem to verify hostname against commonName in certificate

Guido van Rossum added the comment: Bill, can you respond? -- assignee: -> janssen nosy: +gvanrossum, janssen __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1587] instancemethod wrapper for PyCFunctions

Guido van Rossum added the comment: I'm tempted to call YAGNI on this. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1587> __ __

[issue1588] str.format() wrongly formats complex() numbers (Py30a2)

Guido van Rossum added the comment: This really is a feature request -- in Python 2.x there is no formatting code for complex numbers at all, and "%.5s" % complex(...) does the same thing. I agree it would be neat to have control over complex numbers using the same formatting languag

[issue1588] str.format() wrongly formats complex() numbers (Py30a2)

Guido van Rossum added the comment: Maybe this would be a good GHOP task? __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1588> __ ___ Python-bugs-list

[issue1590] "make altinstall" installs pydoc, idle, smtpd.py

Guido van Rossum added the comment: Agreed. Please provide a patch. Isn't this a 2.5-2.6 issue as well? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: > Do you know of any system that supports Python and floats but doesn't have IEEE 753 semantics? (Assuming you meant 754.) I'm pretty sure the VAX doesn't have IEEE FP, and it used to run Unix and Python. Ditto for Crays -- unsure if we

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: > Correct rounding is a property that needs to be proved, not tested. I take it your position is that this can never be done 100% correctly so it shouldn't go in? That's disappointing, because the stream of complaints that "round is brok

[issue1587] instancemethod wrapper for PyCFunctions

Guido van Rossum added the comment: OK, you've convinced me. Let's just make it a C API for now. On Dec 11, 2007 10:56 AM, Christian Heimes <[EMAIL PROTECTED]> wrote: > > Christian Heimes added the comment: > > The wrapper is useful for C code which used PyMethod_Ne

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: I'd be willing to require eval(repr(x)) == x only for platforms whose float input routine is correctly rounding. That would make the current patch acceptable I believe -- but I believe you think there's a better way in that case too? What way is t

[issue1596] Broken pipes should be handled better in 2.x

Guido van Rossum added the comment: I'll entertain a patch for 2.6. For 2.5 I think this smells too much like a feature. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: Sounds okay, except that I think that for some folks (e.g. numeric Python users) I/O speed *does* matter, as their matrices are very large, and their disks and networks are very fast. __ Tracker <[EMAIL PROTECTED]>

[issue1597] running test_ctypes 25 times in a row causes it to fail

New submission from Guido van Rossum: In debug mode, on my Ubuntu Linux box, this fails on the last iteration: $ ./python Lib/test/regrtest.py -R:20 test_ctypes test_ctypes beginning 25 repetitions 1234567890123456789012345 test test_ctypes failed -- Traceback (most

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: > If I were in that situation I would prefer to store the binary > representation. But if someone really needs to store decimal floats, > we can add a method "fast_repr" which always calculates 17 decimal > digits. They can just use &qu

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: I've tracked my problem to the GCC optimizer. The default optimizer setting is -O3. When I edit the Makefile to change this to -O1 or -O0 and recompile (only) doubledigits.c, repr(1e5) starts returning '10.0' again. -O2 behaves the same as -

[issue1588] str.format() wrongly formats complex() numbers (Py30a2)

Guido van Rossum added the comment: > I thought Python 3 was meant to be an _improvement_:-) That's why I didn't close the issue but reclassified it. Or did you expect me to implement it overnight? :-) __ Tracker <[EMAIL PROTECTED]> <

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Changes by Guido van Rossum: -- assignee: -> kbk nosy: +kbk __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1601> __ ___ Python-bugs-list mailing li

[issue1600] str.format() produces different output on different platforms (Py30a2)

Guido van Rossum added the comment: Again, a (not unreasonable) feature request. AFAIK %e behaves the same way. I'm sure if you submitted a patch it would be accepted happily. -- nosy: +gvanrossum priority: -> normal __ Tracker <[EMAI

[issue1604] collections.deque.__init__ doesn't initialize

Guido van Rossum added the comment: I agree, I put the list behavior in on purpose. Should be fixed in 2.6, not 2.5 though, since it's a feature. -- assignee: -> rhettinger nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http:

[issue1597] running test_ctypes 25 times in a row causes it to fail

Guido van Rossum added the comment: Thanks! (I agree with Eric Smith that this is mysterious for the innocent bystander.) Also, what about the -33/+33 leaks? I suppose these are harmless, but it would be better if the test reliably didn't report leaks... -- resolution: -&g

[issue1597] running test_ctypes 25 times in a row causes it to fail

Guido van Rossum added the comment: > The minimal code reporting the -33/+33 leaks that I found is simply this: > >os.popen('ls').read() > > Is there a problem in "os.popen(...)", or do I something wrong here? Try this instead: p = os.popen('ls'

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: > Ok, so if I understand correctly, the ideal thing would be to > implement decimal to binary conversion by ourselves. This would make > str <-> float conversion do the same thing on all platforms, and would > make repr(1.1)=='1.1'.

[issue1606] Doc: subprocess wait() may lead to dead lock

Guido van Rossum added the comment: Why not simply reverse the wait() and read() calls? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1605] Semi autogenerated _types module

Guido van Rossum added the comment: But what about static type objects that nevertheless may be exposed to Python (e.g. dict_keyview?). -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1589] New SSL module doesn't seem to verify hostname against commonName in certificate

Changes by Guido van Rossum: -- nosy: -gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1589> __ ___ Python-bugs-list mailing list Unsubs

[issue1612] infinite recursion when using collections.Sequence in a recursive function (Py30a2)

Guido van Rossum added the comment: The bug is in your code; a string is considered a sequence but its elements are also strings (of length 1). -- nosy: +gvanrossum resolution: -> invalid status: open -> closed __ Tracker <[EMAIL PROTECTE

[issue1609] test_re.py fails

Guido van Rossum added the comment: Can't reproduce. Like before, what platform, compiler etc.? Does using ./configure --with-pydebug make a difference? What's the LD_LIBRARY_PATH for? -- nosy: +gvanrossum __ Tracker <[EMAIL PROT

[issue1606] Doc: subprocess wait() may lead to dead lock

Guido van Rossum added the comment: > > Why not simply reverse the wait() and read() calls? > > I don't think it is sufficient if the user uses more than one pipe. The > subprocess.communicate() and _communicate() methods are using threads > (Windows) or select (Unix)

[issue1608] test_str.py crashes

Guido van Rossum added the comment: What hardware and OS? 32 or 64 bit? What optimization level? Debug build or not? NB. Unless you used /Misc/valgrind-python.supp, the valgrind output is useless. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTEC

[issue1611] doctest.testmod gets noisy if called more than once per SystemExit

Guido van Rossum added the comment: I suspect that doctest was simply not intended to be used this way. Maybe Tim remembers more? -- assignee: -> tim_one nosy: +gvanrossum, tim_one __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1613] Makefile's VPATH feature is broken

Guido van Rossum added the comment: Before I try to reproduce this, I remember having problems when switching between using VPATH and not using it in the same subversion workspace. The .o files left behind by one version confuse the other. -- nosy: +gvanrossum

[issue1608] test_str.py crashes

Guido van Rossum added the comment: Looks like expandtabs() has a problem. Can you boil it down to a single call? __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1608] test_str.py crashes

Guido van Rossum added the comment: BTW is this a released version of GCC? If not, you might want to file the bug with the GCC project... __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1614] bug in string method "title"

Guido van Rossum added the comment: That's not going to change. -- nosy: +gvanrossum resolution: -> wont fix status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.

[issue1609] test_re.py fails

Guido van Rossum added the comment: > Without LD_LIBRARY_PATH it would use the system libraries and not the > compiled ones which anyway is not wanted. What system libraries? Does it make a difference if you don't specify either of --enable-unicode=ucs4 \ --with-wctype-functions

[issue1613] Makefile's VPATH feature is broken

Guido van Rossum added the comment: Do you need more help at this point? __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1613> __ ___ Python-bugs-list

[issue1608] test_str.py crashes

Guido van Rossum added the comment: > This is a soon to be released GCC though I won't deny it has > regressions, but note that extra optimizations already uncovered bugs in > other software. And the GCC authors always win these cases, C standard in hand. > And unless I ca

[issue1608] test_str.py crashes

Guido van Rossum added the comment: Actually, looking at the sample code and the string_expandtabs() implementation it's clear what happened: the test for overflow on line 3318 or 3331 or 3339 must have been optimized out by GCC. This is very inconvenient because lots of buffer ove

[issue1608] test_str.py crashes

Guido van Rossum added the comment: Martin, can you look into this? It seems GCC 4.3 disables buffer overflow protection checks. The best short-term solution may be to disable that particular kind of optimization. How? __ Tracker <[EMAIL PROTECTED]>

[issue1608] test_str.py crashes

Guido van Rossum added the comment: Martin, can you look into this? It seems GCC 4.3 disables buffer overflow protection checks. The best short-term solution may be to disable that particular kind of optimization. How? -- assignee: -> loewis nosy: +loe

[issue1608] test_str.py crashes

Guido van Rossum added the comment: > if you can give me a sample testcase I can bug GCC developers, this > doesn't look good from GCC side at all. Btw from my limited C knowledge > marking variables would volatile would prevent optimizations of them. The example would be someth

[issue1608] test_str.py crashes

Guido van Rossum added the comment: > Ok so this is a code bug according to GCC developers see comment 1 & 2 > at http://gcc.gnu.org/PR34454 . I told you you can't win this argument with the GCC devs. We'll have to use -fwrapv or whatever. __

[issue1608] test_str.py crashes

Guido van Rossum added the comment: Can you suggest a patch that adds this permanently, whenever it is supported? __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1608] test_str.py crashes

Guido van Rossum added the comment: GCC 2.96 is still the golden standard for me, and it doesn't like -fwrapv. Please try to come up with a better patch. It should be easy enough to invoke gcc -fwrapv with a dummy program. __ Tracker <[EMAIL PROTECTED

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: Hm, when I run the full test_ssl test suite with ./python Lib/test/regrtest.py -v -uall test_ssl it always hangs in testAsyncoreServer after printing this: testAsyncoreServer (test.test_ssl.ThreadedTests) ... server: new connection from 127.0.0.1:59781

[issue1616] compiler warnings (gcc 2.96)

New submission from Guido van Rossum: I figured this would be useful: /home/guido/p25/Modules/_ctypes/libffi/src/x86/ffi.c:177: warning: function declaration isn't a prototype /home/guido/p25/Modules/_ctypes/libffi/src/x86/ffi.c:194: warning: function declaration isn't a prototype /

[issue1608] test_str.py crashes

Guido van Rossum added the comment: Committed revision 59483 (2.5 branch). Committed revision 59484 (2.6 trunk). Keeping this open since someone still needs to run autoconf to regenerate configure for the 2.6 trunk. -- priority: urgent -> nor

[issue1617] Rare exception in test_urllib2net

New submission from Guido van Rossum: test test_urllib2net failed -- Traceback (most recent call last): File "/tmp/python-test/local/lib/python2.6/test/test_urllib2net.py", line 175, in test_ftp self._test_urls(urls, self._extra_handlers()) File "/tmp/python-test/local/lib

[issue1606] Doc: subprocess wait() may lead to dead lock

Guido van Rossum added the comment: > I believe so, too. The subprocess docs aren't warning about the problem. > I've seen a fair share of programmers who fall for the trap - including > me a few weeks ago. Yes, the docs should definitely address this. > Consider yet ano

[issue1617] Rare exception in test_urllib2net

Guido van Rossum added the comment: Can you log in to the box and reproduce it manually? On Dec 13, 2007 1:49 PM, Neal Norwitz <[EMAIL PROTECTED]> wrote: > > Neal Norwitz added the comment: > > This may happen every time on the MIPS buildbot. Here is a recent run. > > h

[issue1608] test_str.py crashes

Guido van Rossum added the comment: Thomas Heller ran autoconf for the trunk and submitted as r59485. (Thomas, could you run it in the 2.5 branch as well? I seem to have checked in a lot of gratuitous changes by using an older version of autoconf.) -- nosy: +theller resolution

[issue1608] test_str.py crashes

Guido van Rossum added the comment: > """code that has been audited and fixed in the past will again be > vulnerable.""" > > That code wasn't properly audited or fixed if it depended on integer > overflow behavior. Whatever, this is how over

[issue1622] zipfile hangs on certain zip files

Changes by Guido van Rossum: -- keywords: +patch nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1622> __ ___ Python-bugs-list

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: > Good catch. I flipped a bit cleaning up the C code. > > Here's a fixed patch. > > Added file: http://bugs.python.org/file8949/patch-3 Great! Go ahead and check it in. Sorry for deleting the _real_close() earlier BTW.

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: I spoke too soon. In a debug build, this hangs forever during the second iteration: ./python.exe Lib/test/regrtest.py -uall -R1:1 test_ssl Adding -v, it looks like two iterations are carried out perfectly (one must be a trial run, one the warm-up run), but

[issue1624] Remove output comparison for test_pep277

Guido van Rossum added the comment: Crys, can you look into this? -- assignee: -> tiran keywords: +patch nosy: +gvanrossum, tiran __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1628] test_distutils unit test is failing rev:59499

Changes by Guido van Rossum: -- assignee: -> tiran priority: -> high __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1628> __ ___ Python-bugs

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: > Here's an update version where the asyncore test server properly handles > the EOF race condition. Perfect! Check it in. __ Tracker <[EMAIL PROTECTED]> <http://bugs.

[issue1629] Py_Size() should be named Py_SIZE()

Guido van Rossum added the comment: Agreed. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1629> __ ___ Python-bugs-list

[issue1469] SSL tests leak memory

Changes by Guido van Rossum: -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1469> __ ___ Python

[issue1609] test_re.py fails

Guido van Rossum added the comment: Focus on how using --with-wctype-functions changes things and how this could affect the regex implementation. (I wouldn't be surprised if the other failing tests were to to the regex bugs.) __ Tracker <[EMAIL PROTECTED

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: This is what I was thinking of before, although I'd use "%.16g"%f and "%.17g"%f instead of str(f) and repr(f), and I'd use float() instead of eval(). I suspect that it doesn't satisfy Tim Peters though, because this may de

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: [Tim: when I said "bugs" I just meant non-correct rounding. Sorry.] On the educational issue: it's still embarrassingly easy to run into situations where *arithmetic* using floats produces "educational" results. Simplest case I co

[issue1646] Make socket support TIPC.

Guido van Rossum added the comment: I'm okay with adding this, it doesn't add much code and is properly safeguarded by #ifdefs and has a configure.in patch. I haven't reviewed the code though. -- nosy: +gvanrossum __ Tracker <[EMAIL

[issue1651] Limit the max size of PyUnicodeObject->defenc?

Guido van Rossum added the comment: I don't see a patch. And I think you cannot do this without compromising correctness, since _PyUnicode_AsDefaultEncodedString() returns the cached value without incrementing its refcount. (The only refcount that keeps it alive is the cache

[issue1629] Py_Size() should be named Py_SIZE()

Changes by Guido van Rossum: -- resolution: -> accepted __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1629> __ ___ Python-bugs-list mailing li

[issue1631] Send output from subprocess.Popen objects to any object with a write() method

Changes by Guido van Rossum: -- status: pending -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1631> __ ___ Python-bugs-list mailing li

[issue1632] email cannot be imported

Guido van Rossum added the comment: Let's not waste time in the bug tracker debugging some user's broken setup. Let him contact Panda3D's customer support. -- nosy: +gvanrossum resolution: -> invalid status: pending -> closed _

[issue1640] Enhancements for mathmodule

Guido van Rossum added the comment: i suggest abandoning any attempts at implementing math ourselves. I also suggest not combining this with #1635 but reviewing and (eventually) applying the latter first. -- nosy: +gvanrossum __ Tracker <[EM

[issue1635] Float patch for inf and nan on Windows (and other platforms)

Guido van Rossum added the comment: Mostly looks good. Here are some nits. (1) You shouldn't have to add pystrcmp.c to the VC project files since on Windows it isn't used, right? (2) Will the Windows input routine still accept the *old* representations for INF and NAN? IMO that&#

[issue1636] Execfile unable to take arguments beyond 255!

Guido van Rossum added the comment: This comes from line 1845 in ast.c. It has nothing to do with execfile(), it's just a constraint on the generated bytecode. Fixing this would be quite complex, and referring to "this day and age" isn't going to raise its priority. Howe

[issue1637] urlparse.urlparse misparses URLs with query but no path

Guido van Rossum added the comment: Would you mind submitting a proper patch for Python 2.5 and/or 2.6 generated by "svn diff" relative to an (anonymous) checkout, and adding a unit test? Then I'd be happy to accept this and if it makes it in time for the 2.5.2 release we&

[issue1638] %zd configure test fails on Linux

Guido van Rossum added the comment: Please backport. -- assignee: -> tiran nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1638> __

[issue1641] asyncore delayed calls feature

Guido van Rossum added the comment: If you want attention, please post to python-dev if you didn't already. Or widen the audience to python-list if you want to. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python

[issue1645] Fix socketmodule.c:sock_recvfrom_guts() comment.

Guido van Rossum added the comment: Committed revision 59551. -- nosy: +gvanrossum resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue1649] IDLE error: dictionary changed size during iteration

Guido van Rossum added the comment: You can fix this yourself: for operation in list(self._operations.keys()): -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1648] add new function, sys.gettrace

Guido van Rossum added the comment: Why not do the same for its cousin sys.setprofile()? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1635] Float patch for inf and nan on Windows (and other platforms)

Guido van Rossum added the comment: I suggest you check this in (with the Py_HUGE_VAL fix) and then see how much of #1640 we still need. -- resolution: -> accepted __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1635] Float patch for inf and nan on Windows (and other platforms)

Guido van Rossum added the comment: > Historical note: Guido is probably thinking of "the old" pickle and > marshal here, which did have problems with inf and NaN on Windows (as in > they didn't work at all). Michael Hudson changed them to use special > bit patter

[issue1549] Regression with __hash__ definition and rich comparison operators

Changes by Guido van Rossum: -- keywords: +patch __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1549> __ ___ Python-bugs-list mailing list Unsubs

[issue1549] Regression with __hash__ definition and rich comparison operators

Changes by Guido van Rossum: -- priority: high -> normal __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1549> __ ___ Python-bugs-list mailing li

[issue1583] Patch for signal.set_wakeup_fd

Guido van Rossum added the comment: Here's an updated patch that applies smoothly to the current trunk. -- components: +Extension Modules Added file: http://bugs.python.org/file8988/python2.6-set_wakeup_fd4.diff __ Tracker <[EMAIL PROTECTED

[issue1623] Implement PEP-3141 for Decimal

Guido van Rossum added the comment: Sorry, the PEP was approved, just not yet marked as such. :-) Will do so now. -- nosy: +gvanrossum resolution: postponed -> status: pending -> open __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue1623] Implement PEP-3141 for Decimal

Guido van Rossum added the comment: BTW abc.py and _abcoll.py have been backported to 2.6 already, I propose to backport numbers.py and test_abstract_numbers.py as well. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1549] Regression with __hash__ definition and rich comparison operators

Guido van Rossum added the comment: To be honest, I have no idea what pybots is, and how it's affected. Maybe you can get someone else interested in reviewing the code? I'm focusing mostly on Py3k. __ Tracker <[EMAIL PROTECTED]> <htt

<    7   8   9   10   11   12   13   14   15   16   >