Florent Xicluna added the comment:
You're right. I've misinterpreted the figures.
Only 2.6 and 2.7 are affected --> closing the issue.
--
resolution: -> invalid
status: open -> closed
___
Python tracker
<http://bugs
Florent Xicluna added the comment:
Duplicate of #8087
--
nosy: +flox
resolution: -> duplicate
status: open -> closed
superseder: -> Unupdated source file in traceback
___
Python tracker
<http://bugs.python.or
New submission from Florent Xicluna:
When two implementations give the same result, I use to run micro benchmarks to
give me an hint.
I just noticed that attrgetter is slower than a lambda here:
$ python3.3 -m timeit -s 'from operator import attrgetter; n1 =
attrgetter("__na
Changes by Florent Xicluna :
--
title: operator.attrgetter is slow -> operator.attrgetter is slower than a
lambda
___
Python tracker
<http://bugs.python.org/issu
Changes by Florent Xicluna :
--
nosy: +flox, haypo
___
Python tracker
<http://bugs.python.org/issue17170>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue17044>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue16997>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
components: -Windows
___
Python tracker
<http://bugs.python.org/issue17137>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Confirmed on OSX 64bits with Mark's sample.
$ python3.3
Python 3.3.0 (default, Jan 24 2013, 08:28:09)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" for
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue16991>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +eli.bendersky, flox
___
Python tracker
<http://bugs.python.org/issue17138>
___
___
Python-bugs-list mailing list
Unsub
Changes by Florent Xicluna :
--
keywords: +3.3regression
nosy: +flox, haypo
___
Python tracker
<http://bugs.python.org/issue17137>
___
___
Python-bugs-list mailin
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue3982>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue16076>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
components: +XML
nosy: +eli.bendersky, flox
___
Python tracker
<http://bugs.python.org/issue16089>
___
___
Python-bugs-list mailin
Florent Xicluna added the comment:
you're probably right.
I will continue to use assertSequenceEqual for my use cases.
Actually, what confused me is that these assertions are True:
class T(tuple): pass
class L(list): pass
assertEqual(T('ab'), tuple('ab'))
assertEqual(
Changes by Florent Xicluna :
--
components: +Library (Lib)
nosy: +eli.bendersky, flox
___
Python tracker
<http://bugs.python.org/issue15811>
___
___
Python-bug
New submission from Florent Xicluna:
When writing unittest, I noticed that I need to uses assertSequenceEqual
explicitly when comparing sequences of different kinds.
If I only use the plain assertEqual, it does not generate pretty diffs.
On second thought, I think it could be fixed in
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue8323>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Thank you for digging into this. I close the issue.
I discover now that this kind of problem is quite common in the Mac world.
Other references:
http://news.ycombinator.com/item?id=3879194
http://www.markvanda.net/apple/mac-os-x-memory-issues
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue15661>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
> All of this clearly points towards malloc not releasing allocated memory to
> the system.
> This is perfectly fine and not a bug in either Python or the system.
So it means there's no reliable way to measure the memory consumption of the
prog
Florent Xicluna added the comment:
Though, I cannot reproduce on Debian Squeeze (2.6.6 deb or 2.7 from source) or
Ubuntu (2.7.2+ or 3.2).
Someone on OS X might confirm the same issue.
This is python 2.7.3 installed from source (using perlbrew) and GCC 4.2.1.
The output of the script is
Florent Xicluna added the comment:
I don't mean perlbrew, but homebrew (an OS X package manager to install from
source).
--
___
Python tracker
<http://bugs.python.org/is
New submission from Florent Xicluna:
Hello,
I noticed a large memory consumption in my application.
I tracked it down to be a problem with garbage collection of generator locals.
The issue was noticed in 2.6 first. Then I reproduced it in 2.7.
The test case finds some leak in 3.3 too, it seems
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue15562>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Python 3.2 was already fixed with changeset ba014543ed2c.
It would be nice to have some tests, though.
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue15
Florent Xicluna added the comment:
Changeset ba014543ed2c (3.2a4) references this issue.
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue1553
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue15500>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: -flox, loewis
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Florent Xicluna added the comment:
The documentation for porting is already clear about using "-3" switch.
http://docs.python.org/dev/howto/pyporting.html#eliminate-3-warnings
The argparse module is different because it is not in the stdlib in 2.6, and
you can stay with optparse if
Florent Xicluna added the comment:
It was answered in the previous message by Georg, on the related issue:
http://bugs.python.org/issue6964#msg93032
> Bottom line: move over to the types module *before* running 2to3.
(the thread is very short, and clearly states that there'
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue11051>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue9548>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue13612>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Either the documentation or the implementation should be fixed in 3.3, because
they do not match.
--
nosy: +eli.bendersky
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue9
Florent Xicluna added the comment:
Proposed as won't fix for the 2.x series.
--
resolution: -> wont fix
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.pyt
Florent Xicluna added the comment:
The behavior seems acceptable in 2.7 too.
>>> int('\0')
Traceback (most recent call last):
File "", line 1, in
ValueError: invalid literal for int() with base 10: ''
>>> int('\01')
Traceback
Florent Xicluna added the comment:
Yet another issue with the filesystem on the same buildbot: see issue 9772.
--
resolution: -> works for me
stage: needs patch ->
status: open -> closed
superseder: -> test_pep277 failure on AMD64 debian paral
Changes by Florent Xicluna :
--
nosy: +orsenthil
___
Python tracker
<http://bugs.python.org/issue12411>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +orsenthil
versions: +Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/issue1573931>
___
___
Python-bug
Changes by Florent Xicluna :
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/issue12321>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
keywords: +easy
nosy: +eli.bendersky
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue12322>
___
___
Pytho
Changes by Florent Xicluna :
--
nosy: +eli.bendersky
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue12323>
___
___
Python-bugs-list mailin
Florent Xicluna added the comment:
See also issue 13378 which proposes custom namespace maps for serializing.
--
components: +XML
nosy: +eli.bendersky
versions: +Python 3.4 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue8
Changes by Florent Xicluna :
--
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue6625>
___
___
Python-bugs-list mai
Changes by Florent Xicluna :
--
assignee: effbot ->
nosy: +eli.bendersky
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/
Changes by Florent Xicluna :
--
assignee: effbot ->
components: +XML
versions: +Python 3.4 -Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.org/iss
Changes by Florent Xicluna :
--
versions: +Python 3.4 -Python 3.3
___
Python tracker
<http://bugs.python.org/issue3783>
___
___
Python-bugs-list mailing list
Unsub
Florent Xicluna added the comment:
I propose to close this as won't fix.
The upgrade to ElementTree 1.3 brought some consistency when dealing with
Unicode and encodings.
The reported behavior was only seen in Python 2.7, when using bytes improperly.
--
nosy: +eli.bend
Changes by Florent Xicluna :
--
versions: +Python 3.4 -Python 3.3
___
Python tracker
<http://bugs.python.org/issue9771>
___
___
Python-bugs-list mailing list
Unsub
Florent Xicluna added the comment:
It needs tests to demonstrate the issue in 3.x, and an updated patch.
--
nosy: +hynek, pitrou
stage: patch review -> test needed
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue1
Florent Xicluna added the comment:
> That appears to be a bug in the NFS server.
So, it's not a Python bug.
--
resolution: -> works for me
status: open -> closed
___
Python tracker
<http://bugs.pyt
Florent Xicluna added the comment:
This warning is not specific to the _elementtree module.
See related issue #9566.
--
nosy: +eli.bendersky
resolution: -> duplicate
status: open -> closed
superseder: -> Compilation warnings under x6
Florent Xicluna added the comment:
Attached file is a copy of the remaining warnings on the AMD64 Windows7 SP1 3.x
builder.
--
keywords: +buildbot
nosy: +flox
Added file: http://bugs.python.org/file26465/warnings64.log
___
Python tracker
<h
Changes by Florent Xicluna :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue5504>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Florent Xicluna :
--
versions: +Python 3.4 -Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/issue8273>
___
___
Python-bugs-list mailin
Florent Xicluna added the comment:
This refactoring between cgi and email modules is languishing for few years.
Any thought?
--
status: open -> languishing
versions: +Python 3.4 -Python 3.2
___
Python tracker
<http://bugs.python.org/iss
Florent Xicluna added the comment:
probably related to issue #5154 mentioned in previous comment:
http://bugs.python.org/issue9610#msg114000
--
resolution: -> wont fix
status: open -> closed
___
Python tracker
<http://bugs.python.org/
Changes by Florent Xicluna :
--
nosy: +eli.bendersky
versions: +Python 3.3 -Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.org/issue7214>
___
___
Florent Xicluna added the comment:
does it require action in 3.3, where the C implementation is active by default?
--
___
Python tracker
<http://bugs.python.org/issue7
Changes by Florent Xicluna :
Removed file: http://bugs.python.org/file18445/unnamed
___
Python tracker
<http://bugs.python.org/issue7214>
___
___
Python-bugs-list mailin
Florent Xicluna added the comment:
Test test_pprint fixed with changesets 29642f82bbcc and 79d44f4920d9.
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issu
Florent Xicluna added the comment:
I just broke tests :(
--
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue14998>
___
___
Python-
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue2919>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Thank you for this patch.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Florent Xicluna added the comment:
Thanks for this patch.
I've reviewed the issue and merged the patch of issue #14998 which fixes both
cases.
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
superseder: -> pprint._safe_key i
Florent Xicluna added the comment:
Confirmed on python 3.2 and 3.3.
--
keywords: +easy
nosy: +flox
stage: -> needs patch
type: -> behavior
versions: +Python 3.2, Python 3.3 -Python 3.1
___
Python tracker
<http://bugs.python.org/i
Florent Xicluna added the comment:
Actually, I discovered "python -m test.pystone" during the talk of Mike Müller
at EuroPython. http://is.gd/fasterpy
Even if they are suboptimal for true benchmarks, they should probably be
mentioned somewhere.
In the same paragraph, there should
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue15368>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Florent Xicluna :
The benchmarking tools "pystones" and "pybench" which are shipped with the
Python standard distribution are not documented.
The only information is in the what's-new for Python 2.5:
http://docs.python.org/dev/whatsnew/2.5.h
Changes by Florent Xicluna :
--
versions: +Python 3.4 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue9102>
___
___
Python-bugs-list mailing list
Unsub
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue14797>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue15320>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Well, it fixes the behavior of ElementTree in some multi-threaded cases,
provided you pass the namespace map as an argument of the serializer call.
The fix implements an optional argument for this use case.
As a side effect, it makes it easier to work with
Changes by Florent Xicluna :
--
assignee: ronaldoussoren ->
components: -Macintosh
nosy: -ronaldoussoren
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python
Florent Xicluna added the comment:
Do we merge the patch for 3.3?
I'm +1 on this (patch submitted 8 months ago, backward compatible and reviewed).
--
nosy: +eli.bendersky
___
Python tracker
<http://bugs.python.org/is
Florent Xicluna added the comment:
The other changes are in the patch "issue13248_obsolescence_v3.diff".
AFAIU, they will not be removed in 3.3, in order to facilitate transition from
Python 2.
*asyncore*
shortcut "dispatcher.*" for "dispatcher.socket.*" at
Changes by Florent Xicluna :
Removed file:
http://bugs.python.org/file26297/issue13248_io_max_buffer_size.diff
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
Something like 127.42.42.42 might be more reliable, because it does not depend
on the LAN configuration, only on the local loopback settings.
It is in 127.0.0.0/8 but not in 127.0.0.0/32.
Tested OK here.
127.0.0.0/8 - This block is assigned for use as the
Florent Xicluna added the comment:
actually, this is the mapping table I have, when it fails with [Errno 13]
Permission denied:
$ ifconfig |grep inet
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff00
inet
Florent Xicluna added the comment:
This was this test which was failing:
def testConnectTimeout(self):
# Choose a private address that is unlikely to exist to prevent
# failures due to the connect succeeding before the timeout.
# Use a dotted IP address to avoid
Florent Xicluna added the comment:
probably a temporary network issue: i cannot reproduce it now.
--
resolution: -> works for me
status: open -> pending
___
Python tracker
<http://bugs.python.org/i
Florent Xicluna added the comment:
happened on 10.6, 64 bits, with a fresh build.
== CPython 3.3.0b1 (default:5b71f5891c54, Jul 7 2012, 17:47:30) [GCC 4.2.1
(Apple Inc. build 5666) (dot 3)]
== Darwin-10.8.0-i386-64bit little-endian
--
___
Python
New submission from Florent Xicluna :
There's a warning running test_builtin
$ ./python.exe -m test.regrtest -u all -v test_builtin
== CPython 3.3.0b1 (default:5b71f5891c54, Jul 7 2012, 17:47:30) [GCC 4.2.1
(Apple Inc. build 5666) (dot 3)]
== Darwin-10.8.0-i386-64bit little-e
Changes by Florent Xicluna :
--
assignee: -> ronaldoussoren
components: +Macintosh
nosy: +ronaldoussoren
___
Python tracker
<http://bugs.python.org/issu
New submission from Florent Xicluna :
I have this repeatable failure on OSX.
$ time ./python.exe -m test.regrtest -uall -W test_timeout
[1/1] test_timeout
testBlockingThenTimeout (test.test_timeout.CreationTestCase) ... ok
testFloatReturnValue (test.test_timeout.CreationTestCase) ... ok
Florent Xicluna added the comment:
Eric, I will check but I thought they were not documented.
--
___
Python tracker
<http://bugs.python.org/issue13248>
___
___
Florent Xicluna added the comment:
Few warnings when building trunk (on 10.6):
./Modules/_ctypes/libffi_osx/x86/x86-ffi64.c:49: warning: function declaration
isn’t a prototype
./Modules/_ctypes/libffi_osx/x86/x86-ffi64.c:379: warning: function declaration
isn’t a prototype
--
nosy
Florent Xicluna added the comment:
I cannot reproduce with 3.3 on Snow Leopard (default options, default compiler).
$ ./python.exe -m test.regrtest test_unittest
[1/1] test_unittest
1 test OK.
[158600 refs]
== CPython 3.3.0b1 (tip:9807de61191c, Jul 7 2012, 10:54:30) [GCC 4.2.1 (Apple
Inc
Florent Xicluna added the comment:
Issue #11796 marked as duplicate of this one.
However the issue described in #11796 does not involve exec/execfile.
It is about scopes for list comprehension like this one.
Another doc patch should probably be written to cover the case described in
#11796
Changes by Florent Xicluna :
--
nosy: +Trundle, anikom15, daniel.urban, flox, jonathan.hartley, josmiley,
michael.foord, mjs0, rhettinger
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
It looks as a duplicate of issue 13557.
I close this one, because a doc patch is attached on the other.
--
resolution: -> duplicate
status: open -> closed
superseder: -> exec of list comprehension fails on
Changes by Florent Xicluna :
Added file: http://bugs.python.org/file26301/issue13248_obsolescence_v3.diff
___
Python tracker
<http://bugs.python.org/issue13248>
___
___
Changes by Florent Xicluna :
Removed file: http://bugs.python.org/file23929/issue13248_obsolescence_v2.diff
___
Python tracker
<http://bugs.python.org/issue13248>
___
___
Florent Xicluna added the comment:
For the implementation part, there's something which already plays with the BOM
in the tokenize module.
See tokenize.open(), which uses tokenize.detect_encoding() to read the BOM in
some cases.
--
nosy:
Changes by Florent Xicluna :
Removed file:
http://bugs.python.org/file23928/issue13248_argparse_io_lib2to3.diff
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
Do we agree to remove the "max_buffer_size" from the "io" module in 3.3?
This argument is unused, and deprecated. Just dead code.
See attachment.
--
Added file: http://bugs.python.org/file26297/issue13248_io_
Changes by Florent Xicluna :
--
nosy: +flox
stage: needs patch -> patch review
___
Python tracker
<http://bugs.python.org/issue8881>
___
___
Python-bugs-lis
Florent Xicluna added the comment:
Thanks. Fixed in trunk too, changeset b4322ad1fec4
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
101 - 200 of 1386 matches
Mail list logo
