New submission from Florent Xicluna :
On builder "AMD64 FreeBSD 8.2 3.x" for the TIME_MINYEAR:
==
FAIL: test_negative (test.test_time.TestStrf
New submission from Florent Xicluna :
On builder "x86 FreeBSD 7.2 3.x" :
==
FAIL: test_tzset (test.test_time.TimeTestCase)
--
Traceback (most recent
Changes by Florent Xicluna :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue13309>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
See also issue #13313 on timezone, seen on x86 FreeBSD 7.2
--
___
Python tracker
<http://bugs.python.org/issue13309>
___
___
Florent Xicluna added the comment:
The patch by Petri looks good.
I've uploaded a variant which set the initial mtimes to epoch instead of
creating a _toc_read attribute. The tests are not changed.
--
nosy: +flox
Added file: http://bugs.python.org/file23585/issue13254_v2
Florent Xicluna added the comment:
Re-uploaded, because we can set initialize _last_read to 0 instead of
time.time(). It is more consistent.
--
Added file: http://bugs.python.org/file23586/issue13254_v2.diff
___
Python tracker
<h
Changes by Florent Xicluna :
Removed file: http://bugs.python.org/file23585/issue13254_v2.diff
___
Python tracker
<http://bugs.python.org/issue13254>
___
___
Python-bug
Florent Xicluna added the comment:
Finally, the patch can be only 5 lines...
--
Added file: http://bugs.python.org/file23587/issue13254_v3.diff
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
It fails for very low negative years:
-2147481749 <= year <= -2147483648
(-1<<31) + 1900 <= year <= (-1<<31)
Every other value behaves correctly on this FreeBSD buildbot:
- (-1<<31) + 1900 < year < (+1<<3
Florent Xicluna added the comment:
It fails for very low negative years:
-2147483648 <= year < -2147481748
(-1<<31)<= year < (-1<<31) + 1900
Every other value behaves correctly on this FreeBSD buildbot:
- (-1<<31) + 1900 <= year < (+1<<3
Changes by Florent Xicluna :
--
Removed message: http://bugs.python.org/msg146827
___
Python tracker
<http://bugs.python.org/issue13312>
___
___
Python-bugs-list m
Florent Xicluna added the comment:
I mean formatted with '%Y', of course.
--
___
Python tracker
<http://bugs.python.org/issue13312>
___
___
Python-b
Florent Xicluna added the comment:
I understand that the issue is because the C standard does not specify the
length of the string returned by '%Y'.
The changeset 230f0956aaa3 adds a test to verify that either '%Y' or '%4Y'
returns a 4-digits value usable to pr
Florent Xicluna added the comment:
other test_time related errors are followed with issue 13309, issue 13312 and
issue 13313
--
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
I agree it is a bug. It does not make sense to preserve this behaviour.
I plan to apply the initial patch by Charles-François to 2.7 and 3.x.
--
___
Python tracker
<http://bugs.python.org/issue13
Changes by Florent Xicluna :
--
assignee: -> flox
___
Python tracker
<http://bugs.python.org/issue13140>
___
___
Python-bugs-list mailing list
Unsubscri
Florent Xicluna added the comment:
Failed to build these modules: (3.3 on Snow Leopard)
_tkinter
./cpython/Modules/_tkinter.c: In function ‘AsObj’:
./cpython/Modules/_tkinter.c:996: warning: dereferencing ‘void *’ pointer
./cpython/Modules/_tkinter.c:996: error: invalid use of void expression
Changes by Florent Xicluna :
Removed file: http://bugs.python.org/file23586/issue13254_v2.diff
___
Python tracker
<http://bugs.python.org/issue13254>
___
___
Python-bug
Changes by Florent Xicluna :
--
keywords: -needs review
___
Python tracker
<http://bugs.python.org/issue13254>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue13287>
___
___
Python-bugs-list mailing list
Unsubscri
New submission from Florent Xicluna :
I stopped on this error on buildbot x86 Tiger 3.2.
It looks strange.
test_single_files (test.test_unicode_file.TestUnicodeFiles) ... ERROR
==
ERROR: test_single_files
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue9516>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Florent Xicluna :
The UnicodeWarning is raised on some dict or set operations.
It is not very helpful, and sometimes annoying.
And it is somewhat inconsistent.
# ** warning not raised **
$ python2.7 -c "print u'd\xe9' in {'foo', 'bar'}&
Changes by Florent Xicluna :
--
dependencies: +UnicodeWarning raised on dict() and set()
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
Similar expressions where the warning is raised or not (depending on "latin-1"
comparison):
$ python2.7 -c "print u'd\xe9' in {'foo', 'd\xe9r'}"
False
$ python2.7 -c "print u'd\xe9' in {'
Florent Xicluna added the comment:
This is the expression which raises the warning.
>>> u'compiler.parser' in ['\xab\xd7\xbb', u'\u013f\xd6G']
__main__:1: UnicodeWarning: Unicode equal comparison failed to convert both
arguments to Unicode - interpreting
Florent Xicluna added the comment:
Often sequences or sets have heterogeneous keys, mixing and ,
and in this case there's no easy way to work with them without raising this
UnicodeWarning.
The "logging" module is such an example.
Of course it is only a warning, not a s
Florent Xicluna added the comment:
I suggest to use encoded string as keys in loggerDict.
It should solve both issue #8201 and this one.
Moreover, it seems in line with msg147191 from Martin on issue #13360.
Patch attached.
--
components: +Unicode
dependencies: -UnicodeWarning raised
New submission from Florent Xicluna :
>>> import logging
>>> log = logging.getLogger(any)
Traceback (most recent call last):
File "", line 1, in
File "./Lib/logging/__init__.py", line 1730, in getLogger
return Logger.manager.getLogger(name)
File
Changes by Florent Xicluna :
--
nosy: +vinay.sajip
___
Python tracker
<http://bugs.python.org/issue13361>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue583975>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
keywords: +patch
Added file: http://bugs.python.org/file23622/issue13361_check.diff
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
I've uploaded two proposals:
- first with isinstance(name, str)
- second which is more duck-friendly
Personally, I like ducks.
--
stage: needs patch -> patch review
Added file: http://bugs.python.org/file23623/issue13361_dont_ch
Florent Xicluna added the comment:
btw, changeset a3ba905447ba does not fix the case for:
import logging
log = logging.Logger(any)
--
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
I'm guilty on this one :-)
--
assignee: -> flox
components: +Windows -Interpreter Core
keywords: +buildbot
nosy: +flox
___
Python tracker
<http://bugs.python.org
Florent Xicluna added the comment:
test fails on x86 Windows7 2.7 buildbot
(ok on 3.2 and 3.3)
test_unix_mbox (test.test_mailbox.MaildirTestCase) ...
D:\cygwin\home\db3l\buildarea\2.7.bolen-windows7\build\lib\sqlite3\test\dbapi.py:649:
DeprecationWarning: buffer() not supported in 3.x
b
Florent Xicluna added the comment:
Maybe it is related.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93810
Ambiguous timezone names (AEST vs EST)
--
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
LMT stands for Local Mean Time.
I found a report of someone having an issue parsing timezone with Python 2.6.
Looks quite similar.
http://www.aczoom.com/forums/blockhosts/mar-10-151801-domains-blockhosts5599-error-failed-to-parse-date-for-ip-18911419951
Changes by Florent Xicluna :
--
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue9375>
___
___
Python-bugs-list mailing list
Unsubscri
Florent Xicluna added the comment:
This is a transient failure, other builds are successful.
Maybe the line "time.sleep(2.01 + self._box._skewfactor)" could be changed to
"time.sleep(2.5 + self._box._skewfactor)" in
test_mailbox.TestMaildir.test_reread.
Closing because
New submission from Florent Xicluna :
Seen on Windows 7 builder.
http://www.python.org/dev/buildbot/all/builders/x86%20Windows7%203.x/builds/3949
This build is considered by buildbot.
Actually, the exit code should not be 0.
(...)
[360/360/4] test_descr
324 tests OK.
4 tests failed
Florent Xicluna added the comment:
Then we'll live with it, or work around when it's possible.
For the purists, hopefully we have Python 3 which allows to mix bytes and
strings in a set().
--
resolution: -> rejected
status: o
Changes by Florent Xicluna :
--
Removed message: http://bugs.python.org/msg147102
___
Python tracker
<http://bugs.python.org/issue12392>
___
___
Python-bugs-list m
Florent Xicluna added the comment:
Done by Eric, thank you.
Because of a typo, the message was attached to the wrong ticket.
New changeset 8ea34a74f118 by Éric Araujo in branch '2.7':
Add missing versionadded (fixes #12392)
http://hg.python.org/cpython/rev/8ea34a74f118
--
Changes by Florent Xicluna :
--
nosy: +flox
versions: +Python 3.3 -Python 3.2
___
Python tracker
<http://bugs.python.org/issue1677872>
___
___
Python-bugs-list m
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13378>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Florent Xicluna :
The unicodedata docstring says "5.2" multiple times.
Modules/unicodedata.c: unicodedata -- Provides access to the Unicode 5.2 data
base.
Modules/unicodedata.c: Data was extracted from the Unicode 5.2
UnicodeData.txt file.
Modules/unicodeda
Florent Xicluna added the comment:
Updated with documentation.
--
nosy: +effbot, fdrake, skip.montanaro
Added file: http://bugs.python.org/file23648/issue13291_xmlrpc_v2.diff
___
Python tracker
<http://bugs.python.org/issue13
Changes by Florent Xicluna :
Removed file: http://bugs.python.org/file23648/issue13291_xmlrpc_v2.diff
___
Python tracker
<http://bugs.python.org/issue13297>
___
___
Pytho
Florent Xicluna added the comment:
Ooops wrong patch.
--
Added file: http://bugs.python.org/file23649/issue13297_xmlrpc_bytes_v2.diff
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
I would change the last sentence with something like:
+ unicodedata -- Provides access to the Unicode database.
+ Data was extracted from the UnicodeData.txt file.
+ The current version number is reported in unidata_version constant.
LGTM
Florent Xicluna added the comment:
Maybe a flag "use_builtin_types" is preferred?
It should implies both `bytes` and `datetime.datetime` are used for presenting
data received.
I don't see a use case where we would like to have `bytes` for binary data but
keep `xmlrpc.clien
Florent Xicluna added the comment:
See issue #13297 for a similar case with bytes.
Should we implement a "use_builtin_types" flag which supersedes "use_datetime"?
--
dependencies: +xmlrpc.client could accept bytes for input and output
__
Florent Xicluna added the comment:
This patch v3 implements the proposal of use_builtin_types flag.
In this case the use_datetime flag becomes obsolete.
Please comment.
--
Added file: http://bugs.python.org/file23653/issue13297_xmlrpc_bytes_v3.diff
Florent Xicluna added the comment:
This is the proposed patch which could be applied after issue #13297 is solved.
--
title: use_datetime in SimpleXMLRPCServer -> use_builtin_types in
SimpleXMLRPCServer
Added file: http://bugs.python.org/file23654/issue2979_xmlrpc_server.d
Changes by Florent Xicluna :
--
components: +XML
title: use_builtin_types in SimpleXMLRPCServer -> use_builtin_types in
xmlrpc.server
___
Python tracker
<http://bugs.python.org/iss
Florent Xicluna added the comment:
This patch proposes an implementation of the feature.
>>> from xml.etree import ElementTree as ET
>>> ET.tostring(ET.Element('{http://localhost/house}iq'), encoding="unicode",
>>> namespaces={'http:
Changes by Florent Xicluna :
--
nosy: +scoder
___
Python tracker
<http://bugs.python.org/issue13378>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue3974>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
Thank you for the investigation, and the bug report to the glibc team.
I propose to close it as "won't fix".
--
resolution: -> wont fix
stage: test needed -> committed/rejected
status: open -> pending
__
New submission from Florent Xicluna :
Sometimes we want to check the exact type of an object.
The method assertIsInstance could be misleading in such case.
The current workaround is:
assertIs(type(obj), some_class)
However we can add an argument to the method to keep the benefit of having a
Changes by Florent Xicluna :
Added file: http://bugs.python.org/file23661/grep_test_is_instance.log
___
Python tracker
<http://bugs.python.org/issue13387>
___
___
Pytho
Changes by Florent Xicluna :
Added file: http://bugs.python.org/file23662/grep_test_exact_type.log
___
Python tracker
<http://bugs.python.org/issue13387>
___
___
Pytho
Florent Xicluna added the comment:
At least in the standard library test suite, it should be useful.
When the test is stricter, it catches errors earlier.
I remember when assertIsInstance was made available (issue #7031), we started
to rewrite some expressions
self.assertEqual(type(result
Florent Xicluna added the comment:
I would say that this one is clear too:
aelf.assertTrue(isinstance(obj, cls))
except that the failure message is not very friendly:
AssertionError: False is not true
If we keep assertIsInstance, more people will continue to misuse it just
because the
Florent Xicluna added the comment:
Thank you for your comments.
Uploaded a new version.
--
Added file: http://bugs.python.org/file23665/issue13297_xmlrpc_bytes_v4.diff
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
> +1 on a doc addition (I can even volunteer a patch)
I agree we can highlight the difference between assertIs(type(obj), cls) and
assertIsInstance(obj, cls) in the documentation.
Let's forget this patch and keep it simple.
--
assignee:
Florent Xicluna added the comment:
Patch updated with documentation.
--
nosy: +eric.araujo
stage: patch review -> commit review
Added file: http://bugs.python.org/file23695/issue2979_xmlrpc_server_v2.diff
___
Python tracker
<http://bugs.pyth
Florent Xicluna added the comment:
IIUC, it means that the library/application should not use the bytes API if it
intends to be supported on major platforms.
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13
Changes by Florent Xicluna :
--
components: +Windows
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue13412>
___
___
Python-bugs-list mai
Changes by Florent Xicluna :
--
nosy: +flox, mark.dickinson
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/issue13410>
___
___
Python-
Florent Xicluna added the comment:
With Darwin 10.8.0 x86_64, I confirm the behavior described in first message.
$ python2.7 -V
Python 2.7.2
$ python2.7 -i xx.py
22
22
>>>
TypeError: int() argument must be a string or a number, not 'Foo'
>>> '%d'
Florent Xicluna added the comment:
Thank you Stefan for the comments.
I've added the prefix collision detection, and removed the **kw argument.
(+ tests)
--
Added file:
http://bugs.python.org/file23702/issue13378_non_global_namespaces_v2
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue9102>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue13309>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Florent Xicluna :
--
priority: low -> normal
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue13126>
___
___
Python-bugs-
Changes by Florent Xicluna :
--
type: -> behavior
versions: +Python 3.3 -Python 2.6, Python 3.1
___
Python tracker
<http://bugs.python.org/issue8913>
___
_
Florent Xicluna added the comment:
this was implemented with ticket #13201.
It will be available in version 3.3.
--
nosy: +flox
resolution: -> out of date
stage: -> committed/rejected
status: open -> closed
superseder: -> Implement comparison operators for range
Florent Xicluna added the comment:
collName is probably not what you expect.
You can print repr(collName), repr(currColl) to verify this.
It is not a bug on Python side.
--
nosy: +flox
resolution: -> works for me
stage: -> committed/rejected
status: open ->
Changes by Florent Xicluna :
--
status: pending -> closed
___
Python tracker
<http://bugs.python.org/issue13427>
___
___
Python-bugs-list mailing list
Unsubscri
New submission from Florent Xicluna :
http://docs.python.org/library/sys.html#sys.setrecursionlimit
http://docs.python.org/dev/library/sys.html#sys.setrecursionlimit
Doc for Python 2.7 says:
"A user may need to set the limit higher when she has ..."
Doc for Python 3.3 says:
"A u
Florent Xicluna added the comment:
This explanation is enough. Thanks.
--
resolution: works for me -> invalid
stage: needs patch -> committed/rejected
status: pending -> closed
___
Python tracker
<http://bugs.python.or
Changes by Florent Xicluna :
--
nosy: +flox
type: -> performance
___
Python tracker
<http://bugs.python.org/issue11379>
___
___
Python-bugs-list mai
Changes by Florent Xicluna :
--
components: +XML
___
Python tracker
<http://bugs.python.org/issue11379>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
thank you for this fix.
I agree a posteriori.
--
___
Python tracker
<http://bugs.python.org/issue11886>
___
___
Python-bug
Florent Xicluna added the comment:
Updated with documentation.
Thank you for the review.
I know this does not cover different namespaces in subtree.
But this use case seems very specific. The user could find other means to
achieve it.
--
stage: patch review -> commit review
Ad
New submission from Florent Xicluna :
The example uses PyInstanceObject which is Python 2 only (old-style classes).
http://docs.python.org/dev/extending/newtypes.html#weak-reference-support
--
assignee: docs@python
components: Documentation, Extension Modules
messages: 149183
nosy
Florent Xicluna added the comment:
Of course it's better to have someone else to review the patch.
However in this case, I'm not sure it is a major feature.
BTW, I noticed that effbot is currently marked as *inactive* maintainer
http://docs.python.org/devguide/experts.html#stdlib
If
New submission from Florent Xicluna :
there are still some leftovers of Python 2 old-style classes.
See attached patch.
--
components: Interpreter Core, Library (Lib)
files: oldstyle_leftovers.diff
keywords: patch
messages: 149188
nosy: flox
priority: low
severity: normal
stage: patch
Florent Xicluna added the comment:
Off course the leftovers are mainly in comments and documentation.
See also issue #13574.
--
___
Python tracker
<http://bugs.python.org/issue13
Florent Xicluna added the comment:
I know it won't be committed as-is, but this is the patch with most of the
deprecated things removed.
I skipped all the modules where a veto has been pronounced explicitly.
--
keywords: +patch
Added file: http://bugs.python.org/file
Changes by Florent Xicluna :
--
dependencies: +Change object.__format__(s) where s is non-empty to a TypeError
___
Python tracker
<http://bugs.python.org/issue13
Changes by Florent Xicluna :
--
dependencies: -Change object.__format__(s) where s is non-empty to a TypeError
Added file: http://bugs.python.org/file23928/issue13248_argparse_io_lib2to3.diff
___
Python tracker
<http://bugs.python.org/issue13
Changes by Florent Xicluna :
Removed file: http://bugs.python.org/file23905/issue13248_obsolescence.diff
___
Python tracker
<http://bugs.python.org/issue13248>
___
___
Florent Xicluna added the comment:
I removed object.__format__ from the patch because it is not planned for
removal in 3.3, but in 3.4 (see issue #9856).
I've fixed the documentation *versionchanged* and split the patch in two.
The first is less controversial.
The second might be dela
Changes by Florent Xicluna :
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Florent Xicluna added the comment:
Patch is ready for python 3.4
:-)
--
keywords: +patch
nosy: +flox
Added file: http://bugs.python.org/file23936/issue9856_python-3.4.diff
___
Python tracker
<http://bugs.python.org/issue9
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13624>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Florent Xicluna :
--
nosy: +flox
___
Python tracker
<http://bugs.python.org/issue13555>
___
___
Python-bugs-list mailing list
Unsubscribe:
Florent Xicluna added the comment:
> Is mro_internal's second call to type_mro_modified still needed?
I was about to remove it, however I'm not enough confident on this.
I have to understand how "tp_mro" and "tp_bases" interact i
101 - 200 of 1386 matches
Mail list logo
