[issue5674] distutils fails to find Linux libs (lib.....so.n)

[R. David Murray]

R. David Murray  added the comment:

Are you sure it isn't your Fedora installation that has the problem?  My
understanding is that the linker name (the libxxx.so name) should exist
and be a symbolic link to the most recent soname (libxxx.N).  So I think
distutils is doing the right thing.

See for example
http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html, the
first section of which (I didn't read the whole thing) matches my
understanding of how this works.

Do you have any doc pointers that says Fedora doesn't work this way?

(Note that the libxxx.so linker name may not be in the same directory as
the sonames or the actual library files.)

--
nosy: +r.david.murray
priority:  -> normal

___
Python tracker 

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

[issue459007] Document sys.path on Windows

[R. David Murray]

Changes by R. David Murray :


--
keywords: +easy
versions: +Python 2.7, Python 3.1

___
Python tracker 

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

[issue1529142] Allowing multiple instances of IDLE with sub-processes

[Kurt B. Kaiser]

Kurt B. Kaiser  added the comment:

r71126.  Thanks to everyone for all the work on this!

Note: I still need to patch the Windows install to
bind .py files to a different command string.  The
-e option now only opens an editor window, but I need
to remove the -n option.

--
resolution:  -> accepted
status: pending -> closed

___
Python tracker 

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

[issue1757831] Allow opening just an editor window

[Kurt B. Kaiser]

Kurt B. Kaiser  added the comment:

r71126

-e only opens edit window, not shell

--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

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

[issue5257] test_zipfle and test_distutils write in the test directories

[Tarek Ziadé]

Tarek Ziadé  added the comment:

done in distutils, will open a specific issue for zip.

--
status: open -> closed

___
Python tracker 

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

[issue5684] test_zipfile writes in its test directory

[Tarek Ziadé]

New submission from Tarek Ziadé :

test_zipfile writes in its test directory, which can be a problem if
this directory is read-only in some installations.

--
messages: 85382
nosy: tarek
priority: low
severity: normal
status: open
title: test_zipfile writes in its test directory
type: behavior
versions: Python 2.6, Python 2.7, Python 3.0, Python 3.1

___
Python tracker 

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

[issue2953] _zip_directory_cache untested and undocumented

[Tarek Ziadé]

Changes by Tarek Ziadé :


--
priority:  -> normal
versions: +Python 2.7, Python 3.1 -Python 2.6

___
Python tracker 

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

[issue4015] [patch] make installed scripts executable on windows

[Tarek Ziadé]

Changes by Tarek Ziadé :


--
priority:  -> normal
type:  -> feature request
versions: +Python 2.7, Python 3.1 -Python 2.6

___
Python tracker 

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

[issue5616] Distutils 2to3 support doesn't have the doctest_only flag.

[Tarek Ziadé]

Changes by Tarek Ziadé :


--
priority:  -> normal

___
Python tracker 

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

[issue5302] Allow package_data globs match directories

[Tarek Ziadé]

Tarek Ziadé  added the comment:

After some discussion at Pycon, I was convinced that MANIFEST.in should
be removed.

I'll send a mail about this in Distutils-SIG and if there's a consensus,
I'll deprecate it and also add glob pattern for package_data.

--
priority:  -> high
versions: +Python 2.7, Python 3.1

___
Python tracker 

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

[issue5685] use tarinfo module in distutils

[Tarek Ziadé]

New submission from Tarek Ziadé :

Currently, Distutils makes a system call to tar files, using the tar
command. Let's use Python's tarinfo module, so we don't rely on the tar
program anymore.

--
assignee: tarek
components: Distutils
messages: 85384
nosy: tarek
priority: high
severity: normal
status: open
title: use tarinfo module in distutils
type: behavior
versions: Python 2.7, Python 3.1

___
Python tracker 

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

[issue5682] Move io-in-c modules into a subdirectory of Modules/

[Antoine Pitrou]

Antoine Pitrou  added the comment:

You should commit. If there is a problem with other Windows build files,
it will certainly be noticed and fixed by a true Windows developer.

--

___
Python tracker 

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

[issue5110] Printing Unicode chars from the interpreter in a non-UTF8 terminal raises an error (Py3)

[STINNER Victor]

Changes by STINNER Victor :


--
nosy:  -haypo

___
Python tracker 

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

[issue5686] Float formatting with no type code produces incorrect output for exponential notation

[Eric Smith]

New submission from Eric Smith :

If no format specifier is supplied to a float, it's supposed to work
like 'g', but with at least one digit after the decimal. This works for
non-exponential notation:

>>> format(1., '')
'1.0'
>>> format(1., 'g')
'1'

But for exponential notation, it does not:
>>> format(1e200, '')
'1e+200'
>>> 
>>> format(1e200, 'g')
'1e+200'

--
assignee: eric.smith
components: Interpreter Core
messages: 85386
nosy: eric.smith
severity: normal
status: open
title: Float formatting with no type code produces incorrect output for 
exponential notation
versions: Python 2.6, Python 2.7, Python 3.0, Python 3.1

___
Python tracker 

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

[issue5686] Float formatting with no type code produces incorrect output for exponential notation

[Eric Smith]

Changes by Eric Smith :


--
type:  -> behavior

___
Python tracker 

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

[issue5686] Float formatting with no type code produces incorrect output for exponential notation

[Eric Smith]

Eric Smith  added the comment:

The documentation doesn't agree with the PEP. The docs at
http://docs.python.org/library/string.html#formatstrings just say '' is
the same as 'g'. It does not draw a distinction between exponential and
fixed output.

The PEP has the "at least one digit after the decimal" language. It also
does not draw a distinction between exponential and fixed output.

--
nosy: +marketdickinson

___
Python tracker 

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

[issue5645] test_memoryio fails for py3k on windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

It looks like there is a disagreement between c-io and py-io as to what
the newline parameter in StringIO means.

I think the c-io version makes more sense (but I'm biased, since I wrote
it), while the py-io results are quite difficult to interpret.

--

___
Python tracker 

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

[issue5645] test_memoryio fails for py3k on windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Can you test with the following patch?

--
keywords: +patch
Added file: http://bugs.python.org/file13610/memio.patch

___
Python tracker 

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

[issue5645] test_memoryio fails for py3k on windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Buildbots should be green for the release.

--
priority:  -> release blocker

___
Python tracker 

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

[issue5645] test_memoryio fails for py3k on windows

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
stage:  -> patch review
type:  -> behavior

___
Python tracker 

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

[issue5686] Float formatting with no type code produces incorrect output for exponential notation

[Mark Dickinson]

Mark Dickinson  added the comment:

I don't really see this as a bug in the behaviour.  I'd always understood 
the purpose of the "at least one digit after the decimal" to be to make it 
possible to visually distinguish floats and integers, in the same way that 
repr and str already do.

>>> repr(1e100)
'1e+100'
>>> repr(1e5)
'10.0'

If an exponent's present then the string's already clearly not an integer, 
so there's no need for the '.0'.

--

___
Python tracker 

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

[issue5687] Docstring typo in _io

[Brian Quinlan]

Changes by Brian Quinlan :


--
components: Extension Modules
files: docstring.diff
keywords: patch
nosy: bquinlan
severity: normal
status: open
title: Docstring typo in _io
versions: Python 3.1
Added file: http://bugs.python.org/file13611/docstring.diff

___
Python tracker 

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

[issue5634] cPickle error in case of recursion limit

[Georg Brandl]

Georg Brandl  added the comment:

Yes, that's true. It should be more generally helpful in there.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

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

[issue5642] multiprocessing.Pool.map() docs slightly misleading

[Georg Brandl]

Georg Brandl  added the comment:

Fixed in r71149.

--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

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

[issue5601] webbrowser doesn't just open browsers

[Georg Brandl]

Georg Brandl  added the comment:

Updated docs in r71150.

--
status: pending -> closed

___
Python tracker 

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

[issue5645] test_memoryio fails for py3k on windows

[Hirokazu Yamamoto]

Hirokazu Yamamoto  added the comment:

I confirmed the patch works.

--

___
Python tracker 

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

[issue5645] test_memoryio fails for py3k on windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Committed in r71151, thanks!

--
resolution:  -> fixed
status: open -> closed

___
Python tracker 

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

[issue3845] memory access before short string when checking suffix

[Matthias Klose]

Matthias Klose  added the comment:

fixed for 2.7, 2.6, 3.1

--
assignee:  -> doko
resolution:  -> fixed
status: open -> closed

___
Python tracker 

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

[issue4375] inspect.getsource doesn't work with PYTHONPATH and source compiled from a different dir

[Georg Brandl]

Georg Brandl  added the comment:

Easily done. :)

--
nosy: +georg.brandl
resolution:  -> out of date
status: open -> closed

___
Python tracker 

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

[issue2578] additional unittest type equality methods

[Michael Foord]

Michael Foord  added the comment:

I'd like to add assertIs and assertNotIs.

We have these at work and I would find them useful whilst writing tests
for another set of changes to unittest I'm currently working on!

--

___
Python tracker 

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

[issue2578] additional unittest type equality methods

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Le samedi 04 avril 2009 à 15:06 +, Michael Foord a écrit :
> Michael Foord  added the comment:
> 
> I'd like to add assertIs and assertNotIs.

Let's call it AssertIsNot (we type "x is not None", not "x not is
None").

--

___
Python tracker 

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

[issue2578] additional unittest type equality methods

[Michael Foord]

Michael Foord  added the comment:

I would *mmuch* prefer assertIsNot but it is not symmetrical with the
other asserts.

--

___
Python tracker 

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

[issue5688] inability to ignore multiline warnings -- request to add re.DOTALL to re.compile

[Matthias Klose]

New submission from Matthias Klose :

[forwarded from http://bugs.debian.org/519454]

"""
As of now, warnings.py provides only re.I flag to re.compile on
warnings.py:160.  Recent python-numpy issues way too many warnings, I
was trying to filter them out using warnings.filterwarnings, but was
unable to filter out multiline warning (numpy.histogram).  Adding
re.DOTALL to re.I should help to resolve the problem and allow users to
match also multiline warning messages.
"""

--
messages: 85402
nosy: doko
severity: normal
status: open
title: inability to ignore multiline warnings -- request to add re.DOTALL to 
re.compile
type: feature request

___
Python tracker 

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

[issue5142] pdb feature request: Ability to skip standard lib modules and other selected packages/modules

[Georg Brandl]

Changes by Georg Brandl :


--
assignee:  -> georg.brandl
nosy: +georg.brandl

___
Python tracker 

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

[issue5687] Docstring typo in _io

[Georg Brandl]

Changes by Georg Brandl :


--
assignee:  -> georg.brandl
nosy: +georg.brandl

___
Python tracker 

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

[issue5689] please support lzma compression as an extension and in the tarfile module

[Matthias Klose]

New submission from Matthias Klose :

GNU tar now supports lzma compression as a compression method. Please
consider adding lzma support to the tarfile module (either by using the
external lzma program or by adding a lzma extension to the standard
library).

lzma extension at http://svn.fancycode.com/repos/python/pylzma/trunk/

lzma is used in many tools (7zip, dpkg, rpm), offers faster
decompression than bzip2, slower compression than gzip and bzip2.

--
components: Extension Modules
messages: 85403
nosy: doko
severity: normal
status: open
title: please support lzma compression as an extension and in the tarfile module
type: feature request

___
Python tracker 

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

[issue5689] please support lzma compression as an extension and in the tarfile module

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
priority:  -> normal
versions: +Python 2.7, Python 3.1

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Michael Foord]

Michael Foord  added the comment:

Patch attached.

No docs, if it is agreed I can apply I'll write docs.

After a long discussion we arrived at some semblance of consensus on the
Testing In Python mailing list that this was a good thing (tm).

Only one -1 (thought that cleanUp should be a method) and Holger Krekel
was only +0 because he thinks changes in unittest should be conservative
(but he isn't actually using it).

Many others were +1 - Fred Drake, Titus Brown, Laura Creighton, Robert
Collins, Jonathan Lange, Kumar McMillan and others.

It provides a clean and simple pattern for the cleaning up of resources
- avoiding the need for nested try finallys and the manual tracking of
resources. It can also avoid the need for duplication of cleanup code.

--
keywords: +patch
Added file: http://bugs.python.org/file13612/unittest-cleanup.diff

___
Python tracker 

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

[issue2578] additional unittest type equality methods

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> I would *mmuch* prefer assertIsNot but it is not symmetrical with the
> other asserts.

Well, apparently assertIsNotNone() has been added, so it would be good
to be symmetrical with that :)

--

___
Python tracker 

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

[issue2578] additional unittest type equality methods

[Benjamin Peterson]

Benjamin Peterson  added the comment:

I found while merging this to Py3k that dicts can't be used in
assertSameElements because they are unorderable in py3k.

--

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Antoine Pitrou]

Antoine Pitrou  added the comment:

I'm not sure why it is called after tearDown. It would be better to call
it before tearDown, so that test cases can also use it to initialize
additional resources and finalize them in a LIFO way wrt the main tearDown.

--
nosy: +pitrou

___
Python tracker 

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

[issue5470] MSI installer misses zipdir.zip file in Lib\test

[Benjamin Peterson]

Benjamin Peterson  added the comment:

I don't think I'm going to let this block today's release. Martin, I
assume you can just apply the patch locally when you are building the
installers?

--
nosy: +benjamin.peterson

___
Python tracker 

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

[issue5690] test_types fails under Windows

[Antoine Pitrou]

New submission from Antoine Pitrou :

Compiled with VS 2008 Express:

test test_types failed -- Traceback (most recent call last):
  File "Z:\py3k\__svn__\lib\test\test_types.py", line 343, in
test_int__format__

test(1234, ',', '1,234')
  File "Z:\py3k\__svn__\lib\test\test_types.py", line 235, in test
self.assertEqual(i.__format__(format_spec), result)
AssertionError: '1234\x00' != '1,234'

--
components: Tests
messages: 85409
nosy: benjamin.peterson, pitrou
priority: release blocker
severity: normal
stage: needs patch
status: open
title: test_types fails under Windows
type: behavior
versions: Python 3.1

___
Python tracker 

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

[issue5410] msvcrt bytes cleanup

[Antoine Pitrou]

Antoine Pitrou  added the comment:

There seems to be a problem with ungetwch():

>>> s = msvcrt.getwch()
# Here I type the Euro sign (€)
>>> ascii(s)
"'\\u20ac'"
>>> msvcrt.ungetwch(s)
>>> u = msvcrt.getwch()
>>> ascii(u)
"'\\xac'"

--
nosy: +pitrou
type:  -> behavior

___
Python tracker 

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

[issue5691] test_collections fails under Windows

[Antoine Pitrou]

New submission from Antoine Pitrou :

This is under Windows XP with VS 2008 Express:

test test_collections failed -- Traceback (most recent call last):
  File "Z:\py3k\__svn__\lib\test\test_collections.py", line 714, in
test_equalit
y
self.assertNotEqual(od1, od2)   # different order implies inequality
AssertionError: OrderedDict([('f', 6), ('e', 5), ('a', 3), ('b', 2),
('c', 1), (
'd', 4)]) == OrderedDict([('a', 3), ('b', 2), ('c', 1), ('d', 4), ('f',
6), ('e'
, 5)])

--
components: Tests
messages: 85411
nosy: pitrou, rhettinger
priority: release blocker
severity: normal
stage: needs patch
status: open
title: test_collections fails under Windows
type: behavior
versions: Python 3.1

___
Python tracker 

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

[issue5391] mmap: read_byte/write_byte and object type

[Benjamin Peterson]

Benjamin Peterson  added the comment:

Fixed in r71174.

--
nosy: +benjamin.peterson
resolution:  -> fixed
status: open -> closed

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Michael Foord]

Michael Foord  added the comment:

I'm agnostic on before / after tearDown, so happy to make that change.

--

___
Python tracker 

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

[issue5690] test_types fails under Windows

[Benjamin Peterson]

Changes by Benjamin Peterson :


--
nosy: +eric.smith

___
Python tracker 

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

[issue5692] test_zipfile fails under Windows

[Antoine Pitrou]

New submission from Antoine Pitrou :

Under Windows XP with VS 2008 Express:

test test_zipfile failed -- Traceback (most recent call last):
  File "Z:\py3k\__svn__\lib\test\test_zipfile.py", line 334, in testExtract
self.assertEqual(writtenfile, correctfile)
AssertionError: 'c:_ziptest1' != 'c:\\_ziptest1'

--
components: Tests
messages: 85414
nosy: pitrou
priority: release blocker
severity: normal
status: open
title: test_zipfile fails under Windows
type: behavior
versions: Python 3.1

___
Python tracker 

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

[issue5691] test_collections fails under Windows

[Benjamin Peterson]

Benjamin Peterson  added the comment:

Fixed in r71176.

--
nosy: +benjamin.peterson
resolution:  -> fixed
status: open -> closed

___
Python tracker 

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

[issue2578] additional unittest type equality methods

[Michael Foord]

Michael Foord  added the comment:

Patch with assertIs and assertIsNot. Docs but nothing in NEWS as already
covered.

Ok to apply?

--
Added file: http://bugs.python.org/file13613/unittest-assertis.diff

___
Python tracker 

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

[issue5691] test_collections fails under Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> Fixed in r71176.

Thanks!

--

___
Python tracker 

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

[issue5690] test_types fails under Windows

[Hirokazu Yamamoto]

Hirokazu Yamamoto  added the comment:

I got SEGV on test_types on VC6, but after clean build, it seems SEGV
was gone. Maybe build problem?

--
nosy: +ocean-city

___
Python tracker 

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

[issue5672] Implement a way to change the python process name

[Martin v. Löwis]

Martin v. Löwis  added the comment:

If somebody would provide a patch that adds prctl to the posix module,
that would be fine with me - we have a long tradition of exposing all
available system calls if somebody wants them.

As for Windows: no, there is no equivalent of prctl. The task manager
often displays the Window title, or else the name of the executable module.

--
nosy: +loewis

___
Python tracker 

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

[issue5690] test_types fails under Windows

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Actually, it works in debug mode, but not in release mode.

--

___
Python tracker 

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

[issue5674] distutils fails to find Linux libs (lib.....so.n)

[Martin v. Löwis]

Martin v. Löwis  added the comment:

I agree with David. The .so name must exist; if it doesn't, your
installation does indeed lack the necessary prerequisite.

Closing as invalid.

--
nosy: +loewis
resolution:  -> invalid
status: open -> closed

___
Python tracker 

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

[issue2578] additional unittest type equality methods

[Michael Foord]

Michael Foord  added the comment:

Patch for Py3k with fallback for comparing unsortable sequences in
assertSameElements.

Removed the expected failure and added another test case to confirm that
this patch works for unsortable sequences that are the same (no fail)
and different (fail).

--
Added file: http://bugs.python.org/file13614/unittest-sameelements.diff

___
Python tracker 

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

[issue5690] test_types fails in non-debug mopde

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Well, actually it also happens under Linux in non-debug mode.

--
title: test_types fails under Windows -> test_types fails in non-debug mopde

___
Python tracker 

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

[issue5690] test_types fails in non-debug mode

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
title: test_types fails in non-debug mopde -> test_types fails in non-debug mode

___
Python tracker 

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

[issue5689] please support lzma compression as an extension and in the tarfile module

[Martin v. Löwis]

Martin v. Löwis  added the comment:

As for an lzma module - I would prefer one that isn't LGPL'ed. Instead,
it should link against a system-provide lzma library (which then might
or might not licensed under lpgl). I would probably exclude the lzma
module from Windows, as distributing the lzma sources along with the
Python binaries is too painful.

--
nosy: +loewis

___
Python tracker 

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

[issue5470] MSI installer misses zipdir.zip file in Lib\test

[Martin v. Löwis]

Martin v. Löwis  added the comment:

Tim, thanks for the patch. Applied in r71179, r71180, r71181 and r71182.
Hope it still goes into the tag.

--
resolution:  -> accepted
status: open -> closed

___
Python tracker 

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

[issue5410] msvcrt bytes cleanup

[Benjamin Peterson]

Benjamin Peterson  added the comment:

I think this can wait until the first beta.

--
nosy: +benjamin.peterson
priority: release blocker -> deferred blocker

___
Python tracker 

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

[issue5692] test_zipfile fails under Windows

[Benjamin Peterson]

Benjamin Peterson  added the comment:

Let's worry about this after the alpha.

--
nosy: +benjamin.peterson
priority: release blocker -> deferred blocker

___
Python tracker 

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

[issue5690] test_types fails in non-debug mode

[Eric Smith]

Changes by Eric Smith :


--
assignee:  -> eric.smith

___
Python tracker 

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

[issue5690] test_types fails in non-debug mode

[Eric Smith]

Eric Smith  added the comment:

Problem was a debug #ifdef in the wrong place. Sorry for not testing in
non-debug mode.

Fixed in r71184.

--
priority: release blocker -> normal
resolution:  -> fixed
stage: needs patch -> 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

[issue5682] Move io-in-c modules into a subdirectory of Modules/

[Alexandre Vassalotti]

Alexandre Vassalotti  added the comment:

Committed in r71185.

Thanks Antoine for the review!

--
resolution:  -> accepted
status: open -> closed

___
Python tracker 

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

[issue5692] test_zipfile fails under Windows

[Hirokazu Yamamoto]

Hirokazu Yamamoto  added the comment:

This happens when running test from root directory. Following patch can
workaround this, but this code is there because it is needed, isn't it?
(Related to #4710?)

Index: Lib/zipfile.py
===
--- Lib/zipfile.py  (revision 71184)
+++ Lib/zipfile.py  (working copy)
@@ -957,11 +957,6 @@
 """Extract the ZipInfo object 'member' to a physical
file on the path targetpath.
 """
-# build the destination pathname, replacing
-# forward slashes to platform specific separators.
-if targetpath[-1:] in (os.path.sep, os.path.altsep):
-targetpath = targetpath[:-1]
-
 # don't include leading "/" from file name if present
 if member.filename[0] == '/':
 targetpath = os.path.join(targetpath, member.filename[1:])


When targetpath is "C:/", targetpath becomes "C:" and os.path.join("C:",
"foo") returns "C:foo" instead of "C:/foo"

--
nosy: +ocean-city

___
Python tracker 

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

[issue2578] additional unittest type equality methods

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Seeing how a change in assertNotEqual unveiled a bug in OrderedDict,
would it be desireable for each of assertEqual and assertNotEqual to
test both the '!=' and '==' operators?

--

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Robert Collins]

Robert Collins  added the comment:

It should run after tearDown so that teardown can do actions that may
require cleanup; because the cleanups run in LIFO you can acquire
resources in setUp and have cleanups clean them up,

--
nosy: +rbcollins

___
Python tracker 

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

[issue5670] Speed up pickling of dicts in cPickle

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc  added the comment:

Sorry, I was wrong. I think I noticed that the case size==1 was handled 
differently, and incorrectly inferred the same for size==0.
(btw, the patch for trunk was not updated)

--

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Robert Collins]

Robert Collins  added the comment:

Actually let me phrase that differently.
standard practice for setUp is
super.setUp()
my_setup_code()

and tearDown is
my_teardown_code()
super.tearDown()

because of the LIFO need.

If you imagine that clean ups are being done in the base class teardown,
at the end of that method, then it becomes a lot more obvious why it
should run after tearDown - because thats the right place, and because
many users may be failing to call the base class tearDown which has
historically done nothing.

--

___
Python tracker 

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

[issue5693] TestSuite.__iter__ is not hookable.

[Robert Collins]

New submission from Robert Collins :

Currently if you alter the way TestSuite iterates one must always
implement countTestCases, run, debug etc. The attached patch would make
this simpler.

If this looks ok I'll write up a test for it.

--
components: Library (Lib)
files: testsuite.patch
keywords: patch
messages: 85435
nosy: rbcollins
severity: normal
status: open
title: TestSuite.__iter__ is not hookable.
type: feature request
Added file: http://bugs.python.org/file13615/testsuite.patch

___
Python tracker 

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

[issue5693] TestSuite.__iter__ is not hookable.

[Michael Foord]

Michael Foord  added the comment:

+1 it's a minor change.

--
nosy: +michael.foord

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Antoine Pitrou]

Antoine Pitrou  added the comment:

teardown

Why should they? It's only an implementation choice, and not a wise one
I would say (precisely because people are used to the fact that the
standard tearDown() method does nothing, and doesn't need to be called).

I explained my proposal in terms of actual use cases, but I don't see
any actual use case of addCleanup() in your argument.

--

___
Python tracker 

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

[issue5693] TestSuite.__iter__ is not hookable.

[Benjamin Peterson]

Benjamin Peterson  added the comment:

This looks correct. Just while your at it, you can fix the if statement
in the debug() method by putting the body on another line.

--
nosy: +benjamin.peterson

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Sorry, roundup screwed the quoting. I was responding to the following
sentence:
“If you imagine that clean ups are being done in the base class teardown”.

--

___
Python tracker 

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

[issue5672] Implement a way to change the python process name

[Marcelo Fernández]

Marcelo Fernández  added the comment:

Fine, I'll try to make a patch based on the procname project in Google
Code. Here are some more links with more approaches to solve this issue
(while I learn how to make a patch :-) )

http://abock.org/2006/02/09/changing-process-name-in-mono/
http://shiny.thorne.id.au/2006/02/changing-python-process-titles.html
http://ubuntuforums.org/showthread.php?t=694331

Regards

--

___
Python tracker 

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

[issue1079] decode_header does not follow RFC 2047

[R. David Murray]

R. David Murray  added the comment:

Tony, I don't think I agree with your reading of the RFC.  IMO, your
inversion of test_rfc2047_without_whitespace is not correct.  '=' is not
a 'special' in RFC[2]822 terms, so the atom does not end at the apparent
end of the encoded word.  I say apparent because if I'm interpreting the
RFC correctly it isn't a valid encoded word.  I presume you are thinking
that once you've got an atom composed of several encoded words, there's
no reason not to parse them into individual words (and I'm inclined to
agree with you), but the RFC BNF doesn't support that interpretation as
far as I can see. That is, there is no indication I could find that an
atom can be composed of multiple encoded words.

The encoded word followed by a 'special' is more subtle.  In section 5,
the RFC says:

 An 'encoded-word' that appears within a 'phrase' MUST be
 separated from any adjacent 'word', 'text' or
'special' by 'linear-white-space'.

This would apply to encoded words in names in To and From headers. But
in other places where an encoded word can appear the requirement of
white-space separation from specials is not asserted.  It's not clear
how to make this RFC compliant without implementing a full BNF parser :(

It would probably be reasonable to fix this case so that a word followed
by a special with no intervening white space was allowed.  I've attached
a test case for the 'special' example based on that idea.

--
nosy: +r.david.murray
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.0, Python 3.1 -Python 2.5
Added file: http://bugs.python.org/file13616/issue1079-test.patch

___
Python tracker 

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

[issue2578] additional unittest type equality methods

[Nick Coghlan]

Nick Coghlan  added the comment:

No, because the rich comparison docs explicitly state that the
interpreter makes no assumptions about the relationship between != and
== (or, more precisely, __eq__ and __ne__).

"""There are no implied relationships among the comparison operators.
The truth of x==y does not imply that x!=y is false. """

(from http://docs.python.org/reference/datamodel.html#basic-customization)

If someone is writing unit tests for comparison methods they should
explicitly test all 6 operations.

--

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Robert Collins]

Robert Collins  added the comment:

On Sat, 2009-04-04 at 22:09 +, Antoine Pitrou wrote:
> Antoine Pitrou  added the comment:
> 
> teardown
> 
> Why should they? It's only an implementation choice, and not a wise one
> I would say (precisely because people are used to the fact that the
> standard tearDown() method does nothing, and doesn't need to be called).
> 
> I explained my proposal in terms of actual use cases, but I don't see
> any actual use case of addCleanup() in your argument.

I was arguing by analogy: if we were to implement addCleanup as
something called at the end of the base class tearDown, then it would
clearly support LIFO tearing down of anything people have done [except
that we can't rely on them having called the base tearDown]. The next
best thing then is to call it from run() after calling tearDown.

If you want a worked example:
---
class TestSample(TestCase):

def setUp(self):
dirname = mkdtemp()
self.addCleanup(shutils.rmtree, dirname, ignore_errors=True)
db = make_db(dirname)
self.addCleanup(db.tearDown)


---

This depends on db being torn down before the rmtree, or else the db
teardown will blow up (and it must be torn down to release locks
correctly on windows).

-Rob

--

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Michael Foord]

Michael Foord  added the comment:

Antoine, Robert suggests calling it after tearDown so that tearDown can
also perform actions that need clean up. Not a common use case but at
least a use case. What do you mean by: 

"so that test cases can also use it to initialize
additional resources and finalize them in a LIFO way wrt the main tearDown"

Can you give an example? You seem to imply that clean up be used to
initialize resources which seems very odd.

--

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Antoine Pitrou]

Antoine Pitrou  added the comment:

>def setUp(self):
> dirname = mkdtemp()
> self.addCleanup(shutils.rmtree, dirname, ignore_errors=True)
> db = make_db(dirname)
> self.addCleanup(db.tearDown)

Sure, but that's an example of doing something which is already doable
without addCleanup (resource allocation in setUp).
I was talking about doing resource allocation in the test methods
themselves, which is /only/ possible using addCleanup, and needs
cleanups to be run before tearDown, not after.

--

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Michael Foord]

Michael Foord  added the comment:

The main use case for addCleanup is resource allocation in tests. Why
does this require clean ups to be executed before tearDown?

--

___
Python tracker 

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

[issue5679] cleanUp stack for unittest

[Antoine Pitrou]

Antoine Pitrou  added the comment:

> The main use case for addCleanup is resource allocation in tests. Why
> does this require clean ups to be executed before tearDown?

If your cleanup relies on something which has been set up during setUp
and will be dropped during tearDown (a database connection, a temp dir,
an ssh session, whatever), then the cleanup must be run before the
teardown.

--

___
Python tracker 

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

[issue1079] decode_header does not follow RFC 2047

[Tony Nelson]

Tony Nelson  added the comment:

The email package does not follow the RFCs in anything to do with header
parsing or decoding.  This is a known deficiency.  So no, I am not
thinking of atoms at all -- and neither is email.header.decode_header()! :-(

Until email.header actually parses headers into atoms and then decodes
atoms, it doesn't matter what parsed atoms would look like.  Currently,
email.header.decode_header() just stumbles through raw text, and doesn't
know if it is looking at atoms or not, or usually even what header the
text came from.

In order to interpret the RFC correctly, email.header.decode_header()
needs either a parser and the name of the header it is decoding, or
parsed header data.  I think the latter is being considered for a
redesign of the email package for 3.1 or 3.2 (3 months to a year or so,
and not for 2.x at all), but until then, it is better to decode every
likely encoded-word than to skip encoded-words that, for example, have a
parenthesis on one side or the other.

--

___
Python tracker 

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

[issue4136] merge json library with latest simplejson 2.0.x

[Benjamin Peterson]

Changes by Benjamin Peterson :


--
priority: deferred blocker -> release blocker

___
Python tracker 

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

[issue5410] msvcrt bytes cleanup

[Benjamin Peterson]

Changes by Benjamin Peterson :


--
priority: deferred blocker -> release blocker

___
Python tracker 

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

[issue5692] test_zipfile fails under Windows

[Benjamin Peterson]

Changes by Benjamin Peterson :


--
priority: deferred blocker -> release blocker

___
Python tracker 

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

[issue5695] test_logging fails when run twice in a row

[Antoine Pitrou]

New submission from Antoine Pitrou :

This happens e.g. when searching for refleaks (the -R option to regrtest).


./python -m test.regrtest test_logging test_logging
Could not find '/home/antoine/py3k/debug/Lib/test' in sys.path to remove it
test_logging
test_logging
test test_logging failed -- Traceback (most recent call last):
  File "/home/antoine/py3k/debug/Lib/test/test_logging.py", line 932, in
test_warnings
file, "Dummy line")
  File "/home/antoine/py3k/debug/Lib/logging/__init__.py", line 1534, in
_showwarning
_warnings_showwarning(message, category, filename, lineno, file, line)
  File "/home/antoine/py3k/debug/Lib/logging/__init__.py", line 1534, in
_showwarning
_warnings_showwarning(message, category, filename, lineno, file, line)
[...]
  File "/home/antoine/py3k/debug/Lib/logging/__init__.py", line 1534, in
_showwarning
_warnings_showwarning(message, category, filename, lineno, file, line)
RuntimeError: maximum recursion depth exceeded

--
assignee: vsajip
components: Library (Lib), Tests
messages: 85454
nosy: pitrou, vsajip
priority: normal
severity: normal
stage: needs patch
status: open
title: test_logging fails when run twice in a row
type: crash
versions: Python 3.1

___
Python tracker 

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

[issue3851] IDLE: Pressing "Home" on Windows places cursor before ">>>" instead of after. Solution offered.

[Terry J. Reedy]

Terry J. Reedy  added the comment:

Bingo.  I can also switch behaviors with Numlock (which I routinely have
engaged).  Neither of us was crazy ;-)  Thank you 'weeble'.

--

___
Python tracker 

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

[issue5410] msvcrt bytes cleanup

[STINNER Victor]

STINNER Victor  added the comment:

> There seems to be a problem with ungetwch()

I tested Visual C++ Express 2008 and it looks like _ungetwch() only 
keep 8 lower bits (like _ungetwch(x & 255)). But it's a bug in 
Microsoft library, not in Python code (I added some printf to be 
sure).

My patch (msvcrt_wchar.patch) makes the situation better, but it's not 
perfect because of a bug in Microsoft's library.

msvcrt.getwch() works correctly with characters with code > 255 (eg. 
euro sign, U+20ac, 8364 in decimal).

--

___
Python tracker 

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

[issue5687] Docstring typo in _io

[Benjamin Peterson]

New submission from Benjamin Peterson :

Thanks! Fixed in r71205.

--
nosy: +benjamin.peterson
resolution:  -> fixed
status: open -> closed

___
Python tracker 

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

[issue1600182] Tix ComboBox entry is blank when not editable

[Tim Wegener]

Tim Wegener  added the comment:

I encountered this bug at my previous place of employment. I've since
moved on, so I don't have access to the code/setup where this originally
occurred. 

I tried to setup a test case to reproduce this, but was thwarted by
another bug, probably related to my Linux distro (Fedora 10):

$ python issue_1600182.py 
Traceback (most recent call last):
  File "issue_1600182.py", line 10, in 
c = Tix.ComboBox()
  File "/usr/lib/python2.5/lib-tk/Tix.py", line 579, in __init__
cnf, kw)
  File "/usr/lib/python2.5/lib-tk/Tix.py", line 307, in __init__
self.tk.call(widgetName, self._w, *extra)
_tkinter.TclError: invalid command name "tixComboBox"

I can't comment further until I resolve this other problem.

--

___
Python tracker 

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

[issue5596] memory leaks in 3.1

[Alexandre Vassalotti]

Alexandre Vassalotti  added the comment:

I have the following tests leaking on my Linux build of py3k:


test_structmembers leaked [102, 102, 102] references, sum=306
test_structmembers leaked [102, 102, 102] references, sum=306
test_structmembers leaked [102, 102, 102, 102] references, sum=408
test_structmembers leaked [102, 102, 102, 102] references, sum=408
test_structmembers leaked [102, 102, 102, 102] references, sum=408
test_structmembers leaked [102, 102, 102, 102] references, sum=408
test_structmembers leaked [102, 102, 102, 102] references, sum=408
test_structmembers leaked [102, 102, 102, 102] references, sum=408
test_structmembers leaked [17, 17, 17, 17] references, sum=68
test_structmembers leaked [102, 102, 102, 102] references, sum=408
test_structmembers leaked [102, 102, 102, 102] references, sum=408
test_structmembers leaked [102, 102, 102, 102] references, sum=408
test_structmembers leaked [102, 102, 102, 102, 102, 102] references, sum=612
test_structmembers leaked [106, 102, 102] references, sum=310
test_structmembers leaked [102, 102, 102] references, sum=306
test_structmembers leaked [106, 102, 102] references, sum=310
test_structmembers leaked [106, 102, 102] references, sum=310
test_docxmlrpc leaked [166, -251, 0] references, sum=-85
test_httpservers leaked [-195, 0, 0] references, sum=-195
test_os leaked [0, 0, 23] references, sum=23
test_popen leaked [-23, 23, -23] references, sum=-23
test_telnetlib leaked [0, 0, 84] references, sum=84
test_threading leaked [-119, 119, -28] references, sum=-28
test_urllib2 leaked [227, 227, 227] references, sum=681
test_urllib2_localnet leaked [-251, 3, 3] references, sum=-245

--
nosy: +alexandre.vassalotti

___
Python tracker 

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

[issue5596] memory leaks in 3.1

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Strange, I don't see any leaks in test_structmembers here.

test_structmembers
beginning 9 repetitions
123456789
.
1 test OK.
[89785 refs]

This is with r71202 on a 64-bit build.

--

___
Python tracker 

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

[issue5694] spurious output in test_distutils

[Antoine Pitrou]

New submission from Antoine Pitrou :

test_distutils produces the following kind of output. It doesn't make it
fail, but is a bit distracting.

test_distutils
removing '/tmp/tmpY0RHnV/foo/build_temp' (and everything under it)
removing '/tmp/tmpY0RHnV/foo/build_lib' (and everything under it)
removing '/tmp/tmpY0RHnV/foo/bdist_base' (and everything under it)
removing '/tmp/tmpY0RHnV/foo/build_scripts' (and everything under it)
removing '/tmp/tmpY0RHnV/foo/build_base'
'/tmp/tmpY0RHnV/foo/build_lib' does not exist -- can't clean it
'/tmp/tmpY0RHnV/foo/bdist_base' does not exist -- can't clean it
'/tmp/tmpY0RHnV/foo/build_scripts' does not exist -- can't clean it

--
components: Tests
messages: 85453
nosy: pitrou, tarek
priority: low
severity: normal
stage: needs patch
status: open
title: spurious output in test_distutils
type: behavior
versions: Python 3.1

___
Python tracker 

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

[issue5596] memory leaks in 3.1

[Alexandre Vassalotti]

Alexandre Vassalotti  added the comment:

Dismiss my last comment. These are the tests actually leaking for my build: 

test_docxmlrpc leaked [85, -6, 0, 39] references, sum=118
test_httpservers leaked [-195, 195, 0, 64] references, sum=64
test_os leaked [23, -23, 0, 23] references, sum=23
test_pipes leaked [0, 0, 0, -23] references, sum=-23
test_popen leaked [0, -23, 0, 0] references, sum=-23
test_urllib2 leaked [227, 227, 227, 227] references, sum=908
test_urllib2_localnet leaked [3, 3, 3, 3] references, sum=12

--

___
Python tracker 

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

[issue5693] TestSuite.__iter__ is not hookable.

[Michael Foord]

Changes by Michael Foord :


--
resolution:  -> accepted
status: open -> closed

___
Python tracker 

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

[issue3873] Unpickling is really slow

[STINNER Victor]

STINNER Victor  added the comment:

alexandre.vassalotti wrote:
> The solution is to add a read buffer to Unpickler (...) 
> would mitigate much of the (quite large) Python function 
> call overhead. (...) cPickle has a performance hack to make it 
> uses cStringIO and PyFile directly (via C function calls). In 
> Python 3, the hack was removed (...)

Yes, unpickler_read() calls Buffered_read() through 
PyObject_Call+PyCFunction_Call which is expensive. And unpickle main 
loop starts with unpickler_read(self, &s, 1): just read *one* byte 
(the "opcode"). If Buffered_read() call is expensive, a solution is to 
avoid calling it (eg. read more bytes and... go backward at the end?).

--
nosy: +haypo

___
Python tracker 

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

[issue3873] Unpickling is really slow

[STINNER Victor]

STINNER Victor  added the comment:

Unladen Swallow has a project to optimize pickle. Currently, it uses 3 
benchmarks: 
  pickle - use the cPickle module to pickle a variety of datasets. 
  pickle_dict - microbenchmark; use the cPickle module to pickle a lot 
of dicts. 
  pickle_list - microbenchmark; use the cPickle module to pickle a lot 
of lists.

--

___
Python tracker 

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