[issue3799] Byte/string inconsistencies between different dbm modules

Guido van Rossum <[EMAIL PROTECTED]> added the comment: How hard would it be to fix dbm.dumb to accept strings as well? ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3782] os.write accepts unicode strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Agreed. But we need to tread carefully -- fixing this might break other stuff that has silently relied on it. Better try it ASAP. -- nosy: +gvanrossum ___ Python tracker <[EMAIL

[issue3629] Python won't compile a regex that compiles with 2.5.2 and 30b2

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Figured it out. Does anyone want to review? -- keywords: +needs review, patch Added file: http://bugs.python.org/file11452/fix3629.diff ___ Python tracker <[EMAIL PROTECTE

[issue3799] Byte/string inconsistencies between different dbm modules

Guido van Rossum <[EMAIL PROTECTED]> added the comment: I think this isn't quite right. Ideally a fix should maintain several important properties: (1) Be able to read databases written by Python 2.x. (1a) Write databases readable by Python 2.x. (2) Use the same mapping between st

[issue3629] Python won't compile a regex that compiles with 2.5.2 and 30b2

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Submitted as r66364. I'll merge into 3.0 as well (it's clean merge). -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> <h

[issue3811] Update Unicode database to 5.1.0

Changes by Guido van Rossum <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11458/unnamed ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3811] Update Unicode database to 5.1.0

Guido van Rossum <[EMAIL PROTECTED]> added the comment: 2008/9/10 Martin v. Löwis <[EMAIL PROTECTED]>: > I have now committed the change as r66362 (including the missing > documentation updates), and ported it to 3.0 as r66363 (where I had to > change the flag value and re

[issue3756] re.escape() does not work with bytes()

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Looks fine, except I used frozenset for the _alphanum* variables and reverted to double quotes like the rest of the file. Submitted as r66366. -- assignee: -> gvanrossum resolution: -> accepted status: op

[issue3811] Update Unicode database to 5.1.0

Guido van Rossum <[EMAIL PROTECTED]> added the comment: 2008/9/10 Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: > Code point 0x0370 is now a printable character. > r66381 corrected the failures by simply changing it to 0x0378, until the > next unicodedata upgrade... >

[issue3811] Update Unicode database to 5.1.0

Changes by Guido van Rossum <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11461/unnamed ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue1688] Incorrectly displayed non ascii characters in prompt using "input()" - Python 3.0a2

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Given MvL's review, assuming it fixes the Czech problem, I'm all for applying it. ___ Python tracker <[EMAIL PROTECTED]> <http://

[issue3884] turtle in the tkinter package?

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Agreed. It's toplevel in 2.6. Let's keep it toplevel in 3.x. -- assignee: gvanrossum -> loewis ___ Python tracker <[EMAIL PROTECTED]> <http

[issue3262] re.split doesn't split with zero-width regex

Guido van Rossum <[EMAIL PROTECTED]> added the comment: The problem with doing this per 3.0 is that it's impossible to write a conversion script. I'm okay with adding a flag to enable this behavior though. Please open a new bug with a new patch, preferably one that applies clea

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Hmm... much of the os.path machinery (and os.walk) probably doesn't work with bytes, and neither do fnmatch.py and glob.py, I expect. Plus io.open() refuses bytes for the filename, even though _fileio accepts them. The latte

[issue3959] Add Google's ipaddr.py to the stdlib

New submission from Guido van Rossum <[EMAIL PROTECTED]>: Google just released ipaddr.py, a module that knows how to manipulate IP addresses (both IPv4 and IPv6). I have nothing to do with this module, but I suggest considering it for inclusion in the standard library. It fills a g

[issue3959] Add Google's ipaddr.py to the stdlib

Guido van Rossum <[EMAIL PROTECTED]> added the comment: It would help if I added a link to the Google release: http://code.google.com/p/ipaddr-py/ Description: " An IPv4/IPv6 manipulation library in Python. This library is used to create/poke/manipulate IPv4 and IPv6 addresses a

[issue3959] Add Google's ipaddr.py to the stdlib

Guido van Rossum <[EMAIL PROTECTED]> added the comment: On Wed, Sep 24, 2008 at 9:07 PM, Martin v. Löwis <[EMAIL PROTECTED]> wrote: > Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > I see a list of owners in the code (although it's difficult to infer > re

[issue3826] BaseHTTPRequestHandler depends on GC to close connections

Guido van Rossum <[EMAIL PROTECTED]> added the comment: On Thu, Sep 25, 2008 at 10:57 PM, Gregory P. Smith <[EMAIL PROTECTED]> wrote: > The whole socket._io_refs thing looks like a real design flaw. What is > its actual intended purpose? The original purpose was to su

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: On Fri, Sep 26, 2008 at 5:47 PM, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > Ok. Here's another possibility. It adds another optional parameter to > listdir. If False, bytes strings can be returned. Otherwise, the

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: You can call it a leaky abstraction all you want, but most people think of filenames as text strings most of the time, and we need to somehow support this, at least for users who agree . I agree we also need to support bytes strin

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: On Tue, Sep 30, 2008 at 8:21 AM, Martin v. Löwis <[EMAIL PROTECTED]> wrote: > Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > Here is a patch that solves the issue in a different way: it introduces > sy

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Martin, can you check in your changes to add sys.setfilesystemencoding()? I will check in Victor's changes (with some edits). Together this means that the various suggested higher-level solutions (like returning path-like objec

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: I have committed a somewhat modified version of Victor's latest patch as r66743. Assigning to MvL now for the sys.setfilesystemencoding() commit. Then you can hand it over to the doc folks; something derived from http://wiki

[issue4014] Python-2.6-py2.6.egg-info contains Alpha reference

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Yeah, but I have no idea where I got the info, alas. I would recommend to just delete the Alpha line, but who knows what it means. And should we update this for each alpha or beta release??? -- assignee: gvanrossum -&g

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Reducing priority to critical, it's just docs and tweaks from here. You should also support bytearray() in ntpath: >isinstance(path, (bytes, bytearray)) No, you shouldn't. I changed my mind on this several t

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Assigning to Amaury for Windows fix first. -- assignee: georg.brandl -> amaury.forgeotdarc ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: FWIW, I don't see a need to change macpath.py -- it's only used for MacOS 9 and the occasional legacy app. OSX uses posixpath.py. -- resolution: -> accepted ___ Pyt

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Sorry Amaury, but there's another issue. test_ntpath now fails when run with -bb: == ERROR: test_expandvars (__main__

[issue3187] os.listdir can return byte strings

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Thanks Amaury! On to Georg for doc tweaks. Summary: - all the os.path functions now work on bytes as well, on all platforms - only on Unix (but not OSX) do we recommend using bytes - os.getcwdu() no longer exists - os.getcwdb() r

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

Guido van Rossum added the comment: Phillip, can you fix this in 2.6, 2.7, 3.1 and trunk? (There are certain rules for merging fixes between branches but I don't recall the details. Contact Benjamin or another active core developer via IRC if you need help.) -- nosy: +gvanr

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

Guido van Rossum added the comment: Marking this as release blocker to ensure the (one-line) fix makes it into 2.7 and 3.2. -- priority: high -> release blocker resolution: -> accepted ___ Python tracker <http://bugs.python.org/

[issue4617] SyntaxError when free variable name is also an exception target

Guido van Rossum added the comment: All examples so far (*) have to do with our inability to have properly nested blocks. If we did, I'd make the except clause a block, and I'd issue a syntax warning or error if a nested block shadowed a variable referenced outside it. Ditto for

[issue4617] SyntaxError when free variable name is also an exception target

Guido van Rossum added the comment: On Mon, Feb 22, 2010 at 6:51 PM, Jeremy Hylton wrote: > There's no reason we couldn't revise the language spec to explain that > except clauses and comprehensions are block statements, i.e. > statements that introduce a new block. Howev

[issue4617] SyntaxError when free variable name is also an exception target

Guido van Rossum added the comment: I don't think so. It's very marginal. --Guido (on Android) On Feb 23, 2010 8:52 AM, "Amaury Forgeot d'Arc" wrote: Amaury Forgeot d'Arc added the comment: The above patch adds a new opcode (DELETE_DEREF),

[issue8047] Serialiser in ElementTree returns unicode strings in Py3k

Guido van Rossum added the comment: Hey, can we all try to get along? For anyone who didn't follow the link to r56841, that was mine (though Christian Heimes provided the basis for much of the patch apart from elementtree), and I wrote at the time: """I had to fix a f

[issue8047] Serialiser in ElementTree returns unicode strings in Py3k

Guido van Rossum added the comment: I propose that we continue to see Fredrik as elementtree's "BDFL". If Fredrik wants the API in 3.2 to be changed to be backwards compatible with 2.x, we should do that, and damn the torpedoes (um, 3.1 compatibility). I would do this ASAP;

[issue8122] re.sub doesn't handle properly matches with yes-pattern no-pattern

Guido van Rossum added the comment: You can't use (...) syntax in substitution strings, only \N references. -- nosy: +gvanrossum resolution: -> invalid status: open -> closed ___ Python tracker <http://bugs.python

[issue1771] Remove cmp parameter to list.sort() and builtin.sorted()

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker <http://bugs.python.org/issue1771> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1504] Add 2to3 fixer for (un)bound methods

Guido van Rossum added the comment: Exactly. I'm proposing that we don't bother with people who call types.MethodType(), but we *do* bother converting code that calls new.method(). __ Tracker <[EMAIL PROTECTED]> <http://bugs.p

[issue1414] Fix for refleak tests

Guido van Rossum added the comment: Can you open a separate item for the Tkinter leak so you can close this one? __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1528] Add os.fchmod

Guido van Rossum added the comment: Just check these into the trunk, guys! Great! __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1528> __ ___ Python-bugs-list

[issue1504] Add 2to3 fixer for (un)bound methods

Guido van Rossum added the comment: Aren't there equivalent ways to spell those with the "new" module? How about a fixer for that code (which may be easier to write)? __ Tracker <[EMAIL PROTECTED]> <http://b

[issue1487] PEP 366 implementation

Guido van Rossum added the comment: I think the implementation is fine too (others will have to check it more carefully) but I noticed that the promised functionality of -m doesn't work yet: I created a file Lib/test/foo.py whose sole contents was "from . import test_support".

[issue1497] Patch to remove API to create new unbound methods

Guido van Rossum added the comment: Reducing priority and changing assignee since this is now just waiting for a doc update. -- assignee: gvanrossum -> tiran priority: high -> low __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue1487] PEP 366 implementation

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

[issue1504] Add 2to3 fixer for (un)bound methods

Guido van Rossum added the comment: Does this still need to remain open? -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1504> __ ___

[issue1504] Add 2to3 fixer for (un)bound methods

Guido van Rossum added the comment: > You are right about the rest. Can you start a discussion on the list? Well the only question is where to put these symbols, right? I guess I still like putting them in sys best, for the ones that don't fit in collections. > The last time I tr

[issue1109] Warning required when calling register() on an ABCMeta subclass

Guido van Rossum added the comment: Please roll this back. The error message you added is inappropriate when the parameter to a legitimate register() call is omitted, e.g. collections.Sequence.register() Since we got rid of unbound methods, the infinite recursion is gone; that's a good e

[issue1534] sys.maxfloat patch

Guido van Rossum added the comment: I'd suggest giving it a different name, maybe float_info. sys.maxfloat suggests the value is a float, like sys.maxint and sys.maxunicode. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://b

[issue1520] 'without make' documentation build anomaly

Changes by Guido van Rossum: -- assignee: -> georg.brandl nosy: +georg.brandl priority: -> low __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1520> __

[issue1526] DeprecationWarning in zipfile.py while zipping 113000 files

Guido van Rossum added the comment: Hmm... Seems there's a 16-bit-wide field somewhere. How do other ZIP implementation deal with this? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python

[issue1504] Add 2to3 fixer for (un)bound methods

Guido van Rossum added the comment: > Whatever you say. But shouldn't we make people to use types.MethodType() > or whatever we use as the new module for PyMethod_Type()? People are > going to use types.MethodType() when they see the deprecation warning. Well, if new.method is de

[issue1535] Rename __builtin__ to builtins

Guido van Rossum added the comment: OK Georg, take 'er away! -- assignee: gvanrossum -> georg.brandl resolution: -> accepted __ Tracker <[EMAIL PROTECTED]> <http://bugs.

[issue1535] Rename __builtin__ to builtins

Guido van Rossum added the comment: PS. A note on backporting this to 2.6: I think it's sufficient if "builtins" exists in sys.modules as an alias of "__builtin__" in 2.6. Crys: go ahead and check in the fixer as well. __ Tracker

[issue1487] PEP 366 implementation

Guido van Rossum added the comment: Great, now check it in! On Dec 2, 2007 6:01 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote: > > Nick Coghlan added the comment: > > Posted v2 of the patch, which fixes the problem Guido noted, and > improved the tests to make sure __p

[issue1537] Change GeneratorExit's base class from Exception to BaseException

Guido van Rossum added the comment: looks good to me. Crys, can you do the honors? -- nosy: +gvanrossum resolution: -> accepted __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1537] Change GeneratorExit's base class from Exception to BaseException

Guido van Rossum added the comment: Oops, some tests fail. ctypes and hotshot at least. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1537> __ ___ Python-bugs-

[issue1549] Regression with __hash__ definition and rich comparison operators

Guido van Rossum added the comment: This was done intentionally -- if you define a comparison without defining a hash, the default hash will not match your comparison, and your objects will misbehave when used as dictionary keys. Can you give more details about the Zope issue? I agree that

[issue1537] Change GeneratorExit's base class from Exception to BaseException

Guido van Rossum added the comment: I take it back, that was a build error. After cleaning out the build directory the hotshot and ctypes tests pass. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1538] Avoid string copy when split char doesn't match

Guido van Rossum added the comment: I think this is not quite right; you shouldn't return self unless it is an exact string instance. If it is a subclass of PyString should make a copy. -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED

[issue1545] shutil fails when copying to NTFS in Linux

Guido van Rossum added the comment: There's already an except clause for copystat() that ignores WindowsError in copytree(). If copying this same code into copy2() makes the OP happy I think we can place a similar except clause around the copystat() call in copy2(). -- nosy: +gvanr

[issue1549] Regression with __hash__ definition and rich comparison operators

Guido van Rossum added the comment: You have a point. Can you suggest a patch that fixes this? Question though -- what semantics are used for __lt__ and __gt__ that they don't require overriding __eq__? __ Tracker <[EMAIL PROTECTED]> <http://b

[issue1549] Regression with __hash__ definition and rich comparison operators

Guido van Rossum added the comment: Fair enough. Still, this would go much faster if someone other than myself could be coerced into researching how to fix this (at least the Zope use -- I haven't heard back from the OP). __ Tracker <[EMAIL PROTECTED

[issue1549] Regression with __hash__ definition and rich comparison operators

Guido van Rossum added the comment: Well, the name_op array is used for other purposes. Perhaps the main issue is that the presence of any of these causes the "rich comparison" functionality to be overridden. But please do look into this if you can!

[issue1545] shutil fails when copying to NTFS in Linux

Guido van Rossum added the comment: Hm, that means there's a bug in the existing copytree() code too! Can you check whether WindowsError derives from OSError? If it does, your proposal won't fly. -- resolution: rejected -> status: c

[issue1545] shutil fails when copying to NTFS in Linux

Guido van Rossum added the comment: Not quite, because we only want to ignore WindowsError. Maybe this would work? try: WindowsError except NameError: WindowsError = None try: except os.error, err: if WindowsError is not None or not isinstance(err, WindowsError): raise

[issue1545] shutil fails when copying to NTFS in Linux

Guido van Rossum added the comment: You're right, my code was wrong. Yours will be be correct if you add "else:" in front of the raise. I also still prefer "WindowsError is not None" over just "WindowsError". On Dec 3, 2007 2:25 PM, Raghuram Devarakonda <

[issue1545] shutil fails when copying to NTFS in Linux

Guido van Rossum added the comment: Look at the except clause in copytree(); it does a bit more, collecting the errors and raising them later. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1294] Management of KeyboardInterrupt in cmd.py

Guido van Rossum added the comment: I will look into this for 2.6. No promises. Somebody ought to check whether this does not cause problems for pdb. -- resolution: rejected -> status: closed -> open versions: +Python 2.6 -Python 2.5 __ Tracker &

[issue1400] Py3k's print() flushing problem

Guido van Rossum added the comment: In r59341 I added a flush of stdout and stderr at the end of each command that restores the following behavior: >>> n = sys.stdout.write('X') X>>> I still need to change io.py to properly implement line buffering though; the cur

[issue1067] test_smtplib failures (caused by asyncore)

Guido van Rossum added the comment: Thomas, ping? What do you think of Martin's claim that the fix is incorrect? __ Tracker <[EMAIL PROTECTED]> <http://bugs.python

[issue1539] test_collections: failing refleak test

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

[issue1540] Refleak tests: test_doctest and test_gc are failing

Guido van Rossum added the comment: Hoping to draw Tim into this... He's the only one I know who truly understands these issues... -- assignee: -> tim_one nosy: +tim_one __ Tracker <[EMAIL PROTECTED]> <http://bugs.pyt

[issue1326] "internal" zipimport.zipimporter feature untested

Guido van Rossum added the comment: Which Python version is this for? -- keywords: +patch __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1326> __ ___

[issue1067] test_smtplib failures (caused by asyncore)

Guido van Rossum added the comment: OK, closing. I see plenty of mention of these two modules in the lists, so maybe someone else wants to take a whack at it. I'll post to python-dev. -- keywords: +py3k nosy: -nobody priority: high ->

[issue1336] subprocess.Popen hangs when child writes to stderr

Guido van Rossum added the comment: I'm sorry to ask you to do more work, but could you do me a favor and send this in the form of a svn diff? That file has evolved quite a bit and it's unclear what version you used as a baseline. -- keywor

[issue1400] Py3k's print() flushing problem

Guido van Rossum added the comment: Committed revision 59379. This adds proper line_buffering behavior. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue1559] round() does not

Guido van Rossum added the comment: travelgirl: the 'decimal' module is designed to deal with this. Note that there's a difference between BCD (which can represent decimal numbers exactly) and binary (which can't, in general).

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: I get a segfault when I run it like this: $ ./python.exe Lib/test/regrtest.py -uall test_ssl test_ssl Segmentation fault $ (Without -uall it passes.) __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: I will look at this in an hour or so, after I bring Orlijn to school and drive to work. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: Oops, I just committed revision 59394. Please advise. -- priority: high -> immediate __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: I just reverted it. I put a bit of debugging in the call to _real_close(), and even with Christian's corrections it fails miserably. I prefer leaking. __ Tracker <[EMAIL PROTECTED]> <http://bugs.python

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: I'm giving up on this for now. There are other weird bugs in the code, e.g. this simple piece of code fails: >>> x = urllib.urlopen("https://mail.google.com";).read() Traceback (most recent call last): File "", line 1,

[issue1564] The set implementation should special-case PyUnicode instead of PyString

Changes by Guido van Rossum: -- keywords: py3k nosy: gvanrossum severity: normal status: open title: The set implementation should special-case PyUnicode instead of PyString versions: Python 3.0 __ Tracker <[EMAIL PROTECTED]> <http://bugs.p

[issue1564] The set implementation should special-case PyUnicode instead of PyString

Guido van Rossum added the comment: Would it make any sense at all to refactor the code so that code reuse is automatic? __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1469] SSL tests leak memory

Changes by Guido van Rossum: Removed file: http://bugs.python.org/file8892/unnamed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1469> __ ___ Python-bugs-list

[issue1570] Backport sys.maxsize to Python 2.6

Guido van Rossum added the comment: Maybe suggest this as a GHOP task? -- nosy: +gvanrossum priority: high -> normal __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.o

[issue1469] SSL tests leak memory

Guido van Rossum added the comment: Don't worry, I did back it out before releasing 3.0a2. I believe I hacked your code a bit before checking it in (or after you checked it in, can't remember). Did you see my bug report with a TypeError? __ Track

[issue1469] SSL tests leak memory

Changes by Guido van Rossum: Removed file: http://bugs.python.org/file8845/unnamed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1469> __ ___ Python-bugs-list

[issue1564547] Py_signal_pipe

Guido van Rossum added the comment: I've been told to look at this one more time. -- assignee: -> gvanrossum nosy: +gvanrossum resolution: rejected -> status: closed -> open _ Tracker <[EMAIL PROTECTED]> <http://bugs.

[issue1572] 404 report of SimpleXMLRPCServer is broken

Guido van Rossum added the comment: Is disabling a test the right solution? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1572> __ __

[issue1560] PATCH: Attribute lookup caching

Guido van Rossum added the comment: Are you withdrawing this in favor of #1568? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

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

Guido van Rossum added the comment: We should first decide what should happen. While for command line tools "mv FILE DIR" is established syntax for "mv FILE DIR/`basename FILE`", I'm not at all sure that shutil.move(src, dst) should do the same. I think it sho

[issue1677872] Efficient reverse line iterator

Guido van Rossum added the comment: I'd like to see the doc patches separated out and applied to 2.6 -- they'll automatically merge into 3.0 then. Make that a separate bug please. I like the idea, haven't had time to carefully review the code, but noticed one oddity: >>&

[issue1202] zlib.crc32() and adler32() return value

Guido van Rossum added the comment: How about, in Python 2.6 we make the 64-bit version return a signed value for better compatibility with the 32-bit version, and in Python 3.0 we make both versions return the signed value for better compliance with the standard

[issue1580] Use shorter float repr when possible

Guido van Rossum added the comment: I like this; but I don't have time for a complete thourough review. Maybe Tim can lend a hand? If Tim has no time, I propose that if it works correctly without leaks on at least Windows, OSX and Linux, we check it in, and worry about more review later.

[issue1560] PATCH: Attribute lookup caching

Changes by Guido van Rossum: -- resolution: -> out of date status: open -> closed __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1560> __ __

[issue1560] PATCH: Attribute lookup caching

Guido van Rossum added the comment: That's still ambiguous -- do you want any of those to be closed too? Clearly we're not going to patch 2.4. __ Tracker <[EMAIL PROTECTED]> <http://bugs.p

[issue1581] xmlrpclib.ServerProxy() doesn't use x509 data

Guido van Rossum added the comment: This should be considered for 2.6, not 2.5 (which is in feature freeze). I'm hoping Bill Janssen can review this. -- assignee: -> janssen nosy: +gvanrossum, janssen __ Tracker <[EMAIL PROTEC

[issue1202] zlib.crc32() and adler32() return value

Guido van Rossum added the comment: > Obscure but reasonable. (I suspect you meant to say that py3k should > return the *unsigned* value for better compliance with the standard.) Yes. :) __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

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