[issue12690] Tix bug 2643483

[Ned Deily]

Ned Deily  added the comment:

I think you are confusing the Tix widget set, an independent Tk-based project, 
with Tkinter, the Python interface to Tk, which is part of Python.  The problem 
you linked to appears to be a Tix issue.  That code is not part of Python.  It 
needs to be addressed by the Tix project.

--
nosy: +ned.deily
resolution:  -> rejected
status: open -> closed
title: tkinter bug 2643483 -> Tix bug 2643483

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12675] tokenize module happily tokenizes code with syntax errors

[Gareth Rees]

Gareth Rees  added the comment:

I'm having a look to see if I can make tokenize.py better match the real 
tokenizer, but I need some feedback on a couple of design decisions. 

First, how to handle tokenization errors? There are three possibilities:

1. Generate an ERRORTOKEN, resynchronize, and continue to tokenize from after 
the error. This is what tokenize.py currently does in the two cases where it 
detects an error.

2. Generate an ERRORTOKEN and stop tokenizing. This is what tokenizer.c does.

3. Raise an exception (IndentationError, SyntaxError, or TabError). This is 
what the user sees when the parser is invoked from pythonrun.c.

Since the documentation for tokenize.py says, "It is designed to match the 
working of the Python tokenizer exactly", I think that implementing option (2) 
is best here. (This will mean changing the behaviour of tokenize.py in the two 
cases where it currently detects an error, so that it stops tokenizing.)

Second, how to record the cause of the error? The real tokenizer records the 
cause of the error in the 'done' field of the 'tok_state" structure, but 
tokenize.py loses this information. I propose to add fields to the TokenInfo 
structure (which is a namedtuple) to record this information. The real 
tokenizer uses numeric constants from errcode.h (E_TOODEEP, E_TABSPACE, 
E_DEDENT etc), and pythonrun.c converts these to English-language error 
messages (E_TOODEEP: "too many levels of indentation"). Both of these pieces of 
information will be useful, so I propose to add two fields "error" (containing 
a string like "TOODEEP") and "errormessage" (containing the English-language 
error message).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12675] tokenize module happily tokenizes code with syntax errors

[Gareth Rees]

Gareth Rees  added the comment:

Having looked at some of the consumers of the tokenize module, I don't think my 
proposed solutions will work.

It seems to be the case that the resynchronization behaviour of tokenize.py is 
important for consumers that are using it to transform arbitrary Python source 
code (like 2to3.py). These consumers are relying on the "roundtrip" property 
that X == untokenize(tokenize(X)). So solution (1) is necessary for the 
handling of tokenization errors.

Also, that fact that TokenInfo is a 5-tuple is relied on in some places (e.g. 
lib2to3/patcomp.py line 38), so it can't be extended. And there are consumers 
(though none in the standard library) that are relying on type=ERRORTOKEN being 
the way to detect errors in a tokenization stream. So I can't overload that 
field of the structure.

Any good ideas for how to record the cause of error without breaking backwards 
compatibility?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12675] tokenize module happily tokenizes code with syntax errors

[Gareth Rees]

Gareth Rees  added the comment:

Ah ... TokenInfo is a *subclass* of namedtuple, so I can add extra properties 
to it without breaking consumers that expect it to be a 5-tuple.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue6695] PyXXX_ClearFreeList for dict, set, and list

[Matthias Troffaes]

Matthias Troffaes  added the comment:

Patch against current tip attached.

I can no longer reproduce the large memory leaks with the current tip (which is 
of course wonderful!), so I guess the second part of the patch (freeing the 
freelists during gc.collect) makes no longer sense.

--
Added file: 
http://bugs.python.org/file22833/py3k-04082011-clearfreelist-dict_set_list.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12677] Turtle, fix right/left rotation orientation

[Sandro Tosi]

Sandro Tosi  added the comment:

As mentioned by Ezio, and I also verified myself, mode() doesn't influence the 
orientation on left()/right() methods (probably it affects some other functs?). 
Following was Ezio and I discussed on IRC, I've updated the 2 patches to add a 
small note that you have to import turtle before trying the mentioned commands.

--
Added file: http://bugs.python.org/file22834/turtle_right-default-v2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12677] Turtle, fix right/left rotation orientation

[Sandro Tosi]

Changes by Sandro Tosi :


Added file: http://bugs.python.org/file22835/turtle_right-2.7-v2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7424] segmentation fault in listextend during install

[rpointel]

rpointel  added the comment:

I changed the value from 1000 to 200, and it crashed the same way, then I 
tested with 20, and it ran into a runtime error but in a different place:

c++ -pthread -L/home/ports/pobj/Python-2.7.1/Python-2.7.1 -Wl,--export-dynamic 
-o python  Modules/python.o  -lpython2.7 -pthread  -lutil   -lm  
/home/ports/pobj/Python-2.7.1/Python-2.7.1/libpython2.7.so.0.0: warning: 
tmpnam() possibly used unsafely; consider using mkstemp()
/home/ports/pobj/Python-2.7.1/Python-2.7.1/libpython2.7.so.0.0: warning: 
tempnam() possibly used unsafely; consider using mkstemp()
/home/ports/pobj/Python-2.7.1/Python-2.7.1/libpython2.7.so.0.0: warning: 
strcpy() is almost always misused, please use strlcpy()
/home/ports/pobj/Python-2.7.1/Python-2.7.1/libpython2.7.so.0.0: warning: 
sprintf() is often misused, please use snprintf()
/home/ports/pobj/Python-2.7.1/Python-2.7.1/libpython2.7.so.0.0: warning: 
strcat() is almost always misused, please use strlcat()
Traceback (most recent call last):
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/site.py", line 553, in 

main()
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/site.py", line 535, in 
main
known_paths = addusersitepackages(known_paths)
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/site.py", line 268, in 
addusersitepackages
user_site = getusersitepackages()
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/site.py", line 243, in 
getusersitepackages
user_base = getuserbase() # this will also set USER_BASE
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/site.py", line 233, in 
getuserbase
USER_BASE = get_config_var('userbase')
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sysconfig.py", line 535, 
in get_config_var
return get_config_vars().get(name)
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sysconfig.py", line 434, 
in get_config_vars
_init_posix(_CONFIG_VARS)
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sysconfig.py", line 282, 
in _init_posix
_parse_makefile(makefile, vars)
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sysconfig.py", line 195, 
in _parse_makefile
_variable_rx = re.compile("([a-zA-Z][a-zA-Z0-9_]+)\s*=\s*(.*)")
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/re.py", line 190, in 
compile
return _compile(pattern, flags)
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/re.py", line 243, in 
_compile
p = sre_compile.compile(pattern, flags)
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sre_compile.py", line 
500, in compile
p = sre_parse.parse(p, flags)
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sre_parse.py", line 673, 
in parse
p = _parse_sub(source, pattern, 0)
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sre_parse.py", line 308, 
in _parse_sub
itemsappend(_parse(source, state))
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sre_parse.py", line 633, 
in _parse
p = _parse_sub(source, state)
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sre_parse.py", line 308, 
in _parse_sub
itemsappend(_parse(source, state))
  File "/home/ports/pobj/Python-2.7.1/Python-2.7.1/Lib/sre_parse.py", line 381, 
in _parse
subpattern = SubPattern(state)
RuntimeError: maximum recursion depth exceeded while calling a Python object
*** Error code 1

Then I tried again with the value set to 100, and it ran into the original 
segfault again.

Thanks for your help.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7424] segmentation fault in listextend during install

[Antoine Pitrou]

Antoine Pitrou  added the comment:

The problem with such issues is that:
- they are not reproduceable by someone of the core team
- they only seem to occur in non-debug mode
- they are probably tied to a specific compiler variant, either because of a 
compiler bug, or some aggressive optimization combined with some misled 
assumption in Python's code

To narrow it down, you could:
- try with other compiler versions
- try with other Python versions from python.org (for example the recent 3.2.1)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12690] Tix bug 2643483

[Ned Deily]

Ned Deily  added the comment:

Ah, I see now that the question is actually about the python.org Windows 
installers which, as a service to the user, pull in the external source of Tix 
during the build.  (Tix is not included in the Python source distribution nor 
with the Mac OS X installers.)  Martin, any interest in adding a Tix patch to 
the installer build?

--
components: +Windows -Tkinter
nosy: +loewis
status: closed -> pending
versions: +Python 2.7, Python 3.2, Python 3.3 -Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7247] test_fcntl_64_bit from test_fcntl.py fails in Python 2.6.4

[Elias Pipping]

Elias Pipping  added the comment:

I had this problem as well. Recompiling my kernel with CONFIG_DNOTIFY=y fixed 
it (Thanks to David Leverton for pointing this out to me).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7424] segmentation fault in listextend during install

[Remi Pointel]

Remi Pointel  added the comment:

Thanks Antoine for your response.
Python 3.2.1 and Python 2.4.6 have been successfully installed (but Python 
2.5.4 and Python 2.7.1 failed).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12691] tokenize.untokenize is broken

[Gareth Rees]

New submission from Gareth Rees :

tokenize.untokenize is completely broken.

Python 3.2.1 (default, Jul 19 2011, 00:09:43) 
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import tokenize, io
>>> t = list(tokenize.tokenize(io.BytesIO('1+1'.encode('utf8')).readline))
>>> tokenize.untokenize(t)
Traceback (most recent call last):
  File "", line 1, in 
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/tokenize.py",
 line 250, in untokenize
out = ut.untokenize(iterable)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/tokenize.py",
 line 179, in untokenize
self.add_whitespace(start)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/tokenize.py",
 line 165, in add_whitespace
assert row <= self.prev_row
AssertionError

The assertion is simply bogus: the <= should be >=.

The reason why no-one has spotted this is that the unit tests for the tokenize 
module only ever call untokenize() in "compatibility" mode, passing in a 
2-tuple instead of a 5-tuple.

I propose to fix this, and add unit tests, at the same time as fixing other 
problems with tokenize.py (issue12675).

--
components: Library (Lib)
messages: 141634
nosy: Gareth.Rees
priority: normal
severity: normal
status: open
title: tokenize.untokenize is broken
type: behavior
versions: Python 3.2, Python 3.3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12691] tokenize.untokenize is broken

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +ezio.melotti
stage:  -> test needed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11572] bring Lib/copy.py to 100% coverage

[Sandro Tosi]

Sandro Tosi  added the comment:

Hi Brandon, I really like to see your patch applied, let's see what I can do (I 
also added Ezio in the loop).

I think you only addressed half of msg132140 : could you please have a look at 
the first Éric's question?

Also, still Éric made a comment on rietveld (you'd access to it clicking on 
'review' next to your patch) so it would be nice if you can reply to that too.

About the ~100% coverage, it's probably me but I can't get more then 67%:

$ ./python -m coverage run --pylib --source=copy Lib/test/regrtest.py test_copy
[1/1] test_copy
1 test OK.
$ ./python -m coverage report | grep copy
Lib/copy 182 6067%

How did you compute the coverage?

--
nosy: +ezio.melotti, sandro.tosi

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12691] tokenize.untokenize is broken

[Sandro Tosi]

Sandro Tosi  added the comment:

Hi Gareth, would you like to provide a patch to fix the bug you spotted and add 
the relative case into the testsuite?

--
nosy: +sandro.tosi

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11572] bring Lib/copy.py to 100% coverage

[Ezio Melotti]

Ezio Melotti  added the comment:

ISTM that the patch is trying to do too many things at once:
1) increase the test coverage, possibly fixing some bugs discovered while doing 
so;
2) refactor the tests to use the correct assert methods;
3) get rid of old code, and do some refactoring in copy.py;

I'm not sure any of the changes in copy.py is necessary to make the test suite 
pass, even after the additions you included in the patch (I haven't tested 
though).  If this is the case, the refactoring/cleanup of copy.py should IMHO 
be committed separately.
For the tests it's probably fine to commit both the additions and the 
refactoring together (i.e., it's not worth wasting time splitting the patch).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12691] tokenize.untokenize is broken

[Gareth Rees]

Gareth Rees  added the comment:

See my last paragraph: I propose to deliver a single patch that fixes both this 
bug and issue12675. I hope this is OK. (If you prefer, I'll try to split the 
patch in two.)

I just noticed another bug in untokenize(): in compatibility mode, if 
untokenize() is passed an iterator rather than a list, then the first token 
gets discarded:

Python 3.3.0a0 (default:c099ba0a278e, Aug  2 2011, 12:35:03) 
[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)] on 
darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from tokenize import untokenize
>>> from token import *
>>> untokenize([(NAME, 'hello')])
'hello '
>>> untokenize(iter([(NAME, 'hello')]))
''

No-one's noticed this because the unit tests only ever pass lists to 
untokenize().

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue9338] argparse optionals with nargs='+' can't be followed by positionals

[wrobell]

wrobell  added the comment:

is there a chance to fix this issue?

--
nosy: +wrobell

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11572] bring Lib/copy.py to 100% coverage

[Sandro Tosi]

Sandro Tosi  added the comment:

After a quick chat with Ezio, we tried to revert the changes to copy.py while 
keeping the ones on test, and the test suite passes.

The next steps would probably be to just commit the diff for test_copy.py and 
see if the changes on copy.py are really worth.

Nick, since this issue is assigned to you, what do you want to do? would you 
like me to handle the test-commit part and still be assigned to you for the 
remaining part?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12691] tokenize.untokenize is broken

[Sandro Tosi]

Sandro Tosi  added the comment:

The general rule would be to have separate patches. But in this case, if we 
have interdipendent changes, then those should be "packed" in a single patch 
(f.e. if changes to tokenize break untokenize, than those parts should be 
joined).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12691] tokenize.untokenize is broken

[Eric Snow]

Changes by Eric Snow :


--
nosy: +ericsnow

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11572] bring Lib/copy.py to 100% coverage

[Brandon Craig Rhodes]

Brandon Craig Rhodes  added the comment:

Ezio and Sandro, thank you very much for your attention to this issue, and for 
helping me split it into manageable chunks! To answer the question about why 
"coverage" does not show as high a total as it ought: it's because coverage 
normally can't see the outer, global scope execution of modules that are 
already imported by the time "coverage" itself can take control and install a 
tracer. I have another patch outstanding that fixes this — we are still working 
on it, but the code works fine — if you want to run "coverage" and see a more 
accurate number: http://bugs.python.org/issue11561

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11561] "coverage" of Python regrtest cannot see initial import of libs

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +ezio.melotti

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11572] bring Lib/copy.py to 100% coverage

[Nick Coghlan]

Nick Coghlan  added the comment:

I'd assigned this to myself since I was discussing it with Brandon when he was 
working on it at the PyCon sprints. Since I certainly don't want to block 
anyone else getting to it, I'm unassigning it - feel free to take it forward :)

IIRC, the copy.py changes were things Brandon and I discussed at the sprints as 
cases where they were legacy code that was no longer needed in Py3k, so it made 
more sense to just delete them rather than add tests to cover them. Definitely 
makes sense to split those changes out into a separate patch, though (easier to 
revert if we later discover the code isn't as useless as we think it is).

--
assignee: ncoghlan -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue7424] segmentation fault in listextend during install

[Jon Buller]

Jon Buller  added the comment:

I recently upgraded my SparcStation20 to NetBSD-current and thought I 
would try installing python again.  I found that both 2.7.1 and whatever 
was the most current 2.5 pkgsrc version as of a few months ago built and 
installed just fine.  I'm sorry I can no longer help debug this, but the 
bug was very repeatable on 2.6 and 2.7 for several years and often 
happened with 2.5 as well. But I can no longer repeat it.  I also can't 
say if it is a GCC bug, a NetBSD kernel or libc bug, or a python bug. I 
was sort of expecting it to be a NetBSD bug since I don't remember ever 
having problems with x86, amd64, or sparc64 NetBSD systems, but I still 
believe it could be just about anywhere.

Jon

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12692] test_urllib2net is triggering a ResourceWarning

[Brett Cannon]

New submission from Brett Cannon :

Specifically, 
test.test_urllib2net.OtherNetworkTests.test_sites_no_connection_close is 
leaving a socket open somewhere, but tracking down exactly whom is to blame is 
a mess since socket.SocketIO.close() explicitly relies on refcounting to shut 
down a socket.

--
components: Tests
messages: 141645
nosy: brett.cannon
priority: low
severity: normal
stage: needs patch
status: open
title: test_urllib2net is triggering a ResourceWarning
type: resource usage
versions: Python 3.3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12693] test.support.transient_internet prints to stderr when verbose is false

[Brett Cannon]

New submission from Brett Cannon :

When verbose mode if OFF, test.support.transient_internet prints out what 
resource was unavailable before raising the ResourceDenied exception. Not sure 
if this is a bug (since it has existed for a while) or it is on purpose and 
just happens to seem counter-intuitive.

Assigning to Victor since it seems to be his code (that Antoine applied).

--
assignee: haypo
components: Tests
messages: 141646
nosy: brett.cannon, haypo
priority: low
severity: normal
status: open
title: test.support.transient_internet prints to stderr when verbose is false

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12540] "Restart Shell" command leaves pythonw.exe processes running

[Roundup Robot]

Roundup Robot  added the comment:

New changeset cc86f4ca5020 by Ned Deily in branch '3.2':
Issue #12540: Prevent zombie IDLE processes on Windows due to changes
http://hg.python.org/cpython/rev/cc86f4ca5020

New changeset c2fd1ce1c6d4 by Ned Deily in branch 'default':
Issue #12540: Prevent zombie IDLE processes on Windows due to changes
http://hg.python.org/cpython/rev/c2fd1ce1c6d4

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue12540] "Restart Shell" command leaves pythonw.exe processes running

[Ned Deily]

Ned Deily  added the comment:

With Eli's concurrence, I have applied the updated patch to 3.2 (for 3.2.2) and 
to default (for 3.3).

--
assignee:  -> ned.deily
resolution:  -> fixed
stage: commit review -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com