[issue2719] Backport next()

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: The problem is with the "if you use it consistently" premise. That will not hold in an environment with legacy code, multiple programmers, lots of code in ASPN recipes and published materials, and third-party modules. A patch like this

[issue2723] Truncate __len__() at sys.maxsize

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: Wouldn't it be better to raise OverflowError or somesuch? -- nosy: +rhettinger __ Tracker <[EMAIL PROTECTED]> __ __

[issue2719] Backport next()

Georg Brandl <[EMAIL PROTECTED]> added the comment: IMO having next() in 2.6 helps since if you use it consistently you don't have to care about calling .next() or .__next__(). Also, I don't see how this is different from having e.g. reduce() and functools.reduce() in 2.6. _

[issue2719] Backport next()

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: ISTM, the only value added by next(g) is that it replaces g.next() with a more conventional spelling, g.__next__(). Since 2.6 still has g.next (),I don't see how this backport adds value. It does however create a second way to do it tha

[issue1092502] Memory leak in socket.py on Mac OS X

Mark Hammond <[EMAIL PROTECTED]> added the comment: FYI, #2632 is tracking a regression caused by this change. -- nosy: +mhammond _ Tracker <[EMAIL PROTECTED]> _ ___

[issue2601] [regression] reading from a urllib2 file descriptor happens byte-at-a-time

Changes by Mark Hammond <[EMAIL PROTECTED]>: -- resolution: -> duplicate __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Un

[issue2601] [regression] reading from a urllib2 file descriptor happens byte-at-a-time

Changes by Mark Hammond <[EMAIL PROTECTED]>: -- status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsub

[issue2601] [regression] reading from a urllib2 file descriptor happens byte-at-a-time

Mark Hammond <[EMAIL PROTECTED]> added the comment: For those trying to follow along at home: best I can tell we have 3 other issues on this: #1092502 and #1389051 are dupes of an initial bug, but the fix for those bugs caused regressions reported in this bug and in #2632. To try and reduce conf

[issue2723] Truncate __len__() at sys.maxsize

Changes by Alexander Belopolsky <[EMAIL PROTECTED]>: -- type: -> feature request __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing

[issue2723] Truncate __len__() at sys.maxsize

New submission from Alexander Belopolsky <[EMAIL PROTECTED]>: On Tue, Apr 29, 2008 at 10:36 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: .. > Let's also fix __len__() so that it returns sys.{maxint,maxsize} when > the result doesn't fit in a Py_ssize_t. http://mail.python.org/pipermail/pyt

[issue2526] str.format() :n format does not appear to work for int and float

Eric Smith <[EMAIL PROTECTED]> added the comment: Committed fix in r62586. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2722] os.getcwd fails for long path names on linux

New submission from Jean-Paul Calderone <[EMAIL PROTECTED]>: $ python -c "print len('`pwd`'); import os; print os.getcwd()" 1174 Traceback (most recent call last): File "", line 1, in ? OSError: [Errno 34] Numerical result out of range $ The getcwd man page documents the ERANGE failure and sug

[issue1856] shutdown (exit) can hang or segfault with daemon threads running

Changes by Lars Immisch <[EMAIL PROTECTED]>: -- nosy: +larsimmisch __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscri

[issue2721] unittest.makeSuite undocumented and "obsolete" - but what to use instead?

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- nosy: +purcell __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscr

[issue2721] unittest.makeSuite undocumented and "obsolete" - but what to use instead?

New submission from Paul Winkler <[EMAIL PROTECTED]>: A comment in unittest.py says "these functions should be considered obsolete". But I've seen a lot of code in the wild still using unittest.makeSuite(MyTestCase)... in fact it's used frequently in the python standard library tests. And I don'

[issue2349] Py3K warn against assigning to True/False

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: As I looked over the code again, I realized that it doesn't help to just do a normal warning while compiling because the line number isn't supplied. You have to use PyWarn_Explicit for that (see the warning about backquotes). Since the file

[issue2714] Unable to start IDLE on Windows Server 2003 x64 Edition w/ SP2

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Check whether the TCL_DIR or TK_DIR environment variables are set. If so, unset them. __ Tracker <[EMAIL PROTECTED]> __ __

[issue2720] make compiling struct be passed around to all ast helpers

Christian Heimes <[EMAIL PROTECTED]> added the comment: +1 for the feature -- nosy: +tiran __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-lis

[issue2720] make compiling struct be passed around to all ast helpers

New submission from Benjamin Peterson <[EMAIL PROTECTED]>: This patch causes struct *compiling to be passed around to all of the ast helper functions. Since most functions already take it, this makes it more consistent as a whole. Also, the filename (from compiling->c_filename) is needed to issue

[issue2409] regrtest should not just skip imports that fail

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- type: -> behavior __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsu

[issue2690] Precompute range length

Facundo Batista <[EMAIL PROTECTED]> added the comment: Fair enough, specially if in the documentation of range() we put "if you want a unbound, no limit, number generator, use itertools.count()" (or something well written in english ;) ). Thanks! __ Tracker <[EMA

[issue2719] Backport next()

New submission from Georg Brandl <[EMAIL PROTECTED]>: Backporting 3.0's next() builtin. There's no change w.r.t. __next__/next, that is tracked in #2336. -- assignee: gvanrossum components: Interpreter Core files: nextbackport.diff keywords: 26backport, patch messages: 65980 nosy: georg

[issue1652] subprocess should have an option to restore SIGPIPE to default action

Georg Brandl <[EMAIL PROTECTED]> added the comment: Martin, what do you think? -- assignee: -> loewis __ Tracker <[EMAIL PROTECTED]> __ ___ Pyt

[issue2693] IDLE doesn't work with Tk 8.5

Greg Couch <[EMAIL PROTECTED]> added the comment: Starting over: The goal of this patch is to get Tk 8.5 to work with Python 2.5's Idle. It currently fails with a ValueError, "invalid literal for int() with base 10: '(72,'" (the 72 changes depending on what was typed in). The root cause of bug

[issue2053] IDLE - standardize dialogs

Tal Einat <[EMAIL PROTECTED]> added the comment: uploaded a single comprehensive patch file Added file: http://bugs.python.org/file10140/IDLE_standardize_dialogs.080429.patch __ Tracker <[EMAIL PROTECTED]> _

[issue2714] Unable to start IDLE on Windows Server 2003 x64 Edition w/ SP2

Gregory Dai <[EMAIL PROTECTED]> added the comment: Martin Loewis had me start IDLE from a DOS prompt. The backtrace pointed to an improper installation of tcl. On Mon, Apr 28, 2008 at 4:25 PM, Facundo Batista <[EMAIL PROTECTED]> wrote: > > Facundo Batista <[EMAIL PROTECTED]> added the comment:

[issue2714] Unable to start IDLE on Windows Server 2003 x64 Edition w/ SP2

Gregory Dai <[EMAIL PROTECTED]> added the comment: After removing my Ruby installation, I got the following: " C:\lang\Python25>Lib\idlelib\idle.py Traceback (most recent call last): File "C:\lang\Python25\Lib\idlelib\idle.py", line 21, in idlelib.PyShell.main() File "C:\lang\Python25\l

[issue1496032] test_float segfaults with SIGFPE on FreeBSD 6.0 / Alpha

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Adding -mieee didn't fix the math and cmath problems. Should I revert the change in r62499, or leave it in? It seems to me that having -mieee is a good thing on the whole. The main reason to not want IEEE 754 conformance would be speed.

[issue2685] Add -mieee to compile flags, when available

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Done in r62499 -- resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ __

[issue2717] tempfile.mkstempf

Nick Coghlan <[EMAIL PROTECTED]> added the comment: The delete flag on NamedTemporaryFile is new for 2.6, so it isn't surprising people aren't familiar with it. The other advantage of using NamedTemporaryFile is that its name attribute is set correctly, which isn't the case when using mkstemp dir

[issue2718] Logging.basicConfig ignores level=0

Vinay Sajip <[EMAIL PROTECTED]> added the comment: Already fixed in SVN. Change was: "if level:" -> "if level is not None:" in basicConfig(). -- nosy: +vsajip resolution: -> duplicate status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue2718] Logging.basicConfig ignores level=0

New submission from Jeroen van der Ham <[EMAIL PROTECTED]>: logging.basicConfig seems to ignore level=0: >>> import logging >>> logging.basicConfig(level=0) >>> logging.getLogger().getEffectiveLevel() 30 >>> import logging >>> logging.basicConfig(level=10) >>> logging.getLogger().getEffectiveL

[issue1652] subprocess should have an option to restore SIGPIPE to default action

Colin Watson <[EMAIL PROTECTED]> added the comment: 2.6 is fine if that's what the release process dictates; I don't want it to be lost, that's all. __ Tracker <[EMAIL PROTECTED]> __ __

[issue1180] Option to ignore or substitute ~/.pydistutils.cfg

Phillip J. Eby <[EMAIL PROTECTED]> added the comment: Oh, I thought you meant that it overrides *which* config files -- i.e., implied that it was handling --no-user-config. __ Tracker <[EMAIL PROTECTED]>

[issue2717] tempfile.mkstempf

Skip Montanaro <[EMAIL PROTECTED]> added the comment: Nick> What does this offer over using NamedTemporaryFile(delete=False)? Nothing I suppose. I wasn't aware of the similarity of the two (I always use mkstemp()) or the delete arg to NamedTemporaryFile, and assumed Guido's complaint about mkst

[issue2717] tempfile.mkstempf

Nick Coghlan <[EMAIL PROTECTED]> added the comment: What does this offer over using NamedTemporaryFile(delete=False)? -- nosy: +ncoghlan __ Tracker <[EMAIL PROTECTED]> __ _

[issue2717] tempfile.mkstempf

Changes by Skip Montanaro <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10136/mkstempf.diff __ Tracker <[EMAIL PROTECTED]> __ ___ Python

[issue2717] tempfile.mkstempf

Skip Montanaro <[EMAIL PROTECTED]> added the comment: Thanks. New patch attached. Added file: http://bugs.python.org/file10137/mkstempf.diff __ Tracker <[EMAIL PROTECTED]> __

[issue2690] Precompute range length

Nick Coghlan <[EMAIL PROTECTED]> added the comment: It also isn't what range() and xrange() are used for now in 2.x. range() returns an actual list, hence is limited to sequences that fit in a reasonable amount of memory, and xrange() doesn't support values greater than sys.maxint at all (as it u

[issue1950] Potential overflows due to incorrect usage of PyUnicode_AsString.

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: BTW: The API PyUnicode_AsString() is pretty useless by itself - there's no way to access the size information of the returned string without again going to the Unicode object. I'd suggest to remove the API altogether and not only deprecat

[issue2717] tempfile.mkstempf

André Malo <[EMAIL PROTECTED]> added the comment: It should catch OSError on fdopen, close fd and reraise, I think. -- nosy: +ndparker __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1950] Potential overflows due to incorrect usage of PyUnicode_AsString.

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: @@ -2195,7 +2200,7 @@ } return Py_None; } - len = lastdot - start; + len = (size_t)(lastdot - start);

[issue2712] enhanced ioctl

ndbecker <[EMAIL PROTECTED]> added the comment: OK. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.