Changes by Ezio Melotti :
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Ezio Melotti added the comment:
Do you have any use case for x = 0050?
I don't any reason to adding leading 0s to a literal, but with int() the
situation is different because you might get string with leading 0s from
somewhere else. Also note that the int() function is more flexibl
Ezio Melotti added the comment:
Fixed, thanks for the patch!
--
assignee: docs@python -> ezio.melotti
nosy: +ezio.melotti
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tr
Ezio Melotti added the comment:
If the leading 0s are valid for floats (and complex) literals then int literals
are indeed inconsistent.
If we want consistency with the other literals, it is probably better allowing
them for ints, because removing them from float/complex is not backward
Ezio Melotti added the comment:
I think that's normal, the ^ matches only at the beginning of the string.
--
nosy: +ezio.melotti, mrabarnett
___
Python tracker
<http://bugs.python.org/is
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue12126>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Ezio Melotti :
In case of error (e.g. timeout error), urllib.request leaves the socket open:
import urllib.request as ur
import socket
s = socket.socket()
s.bind(('localhost', 1))
s.listen(0)
socket.setdefaulttimeout(5)
ur.urlopen('http://localhost.lo
Ezio Melotti added the comment:
There are still functions that are not documented, so I think this should stay
open until we documented them (unless they shouldn't be documented -- in that
case it can be closed).
--
___
Python tracker
Ezio Melotti added the comment:
The packaging test (test_pypi_simple.py:test_uses_mirrors) creates a server and
a mirror, starts the mirror only, tries to connect to the server, and then
falls back on the mirror when the server raises a timeout error.
The code in the first message does more
Changes by Ezio Melotti :
--
components: +Library (Lib) -Extension Modules
nosy: +ezio.melotti
versions: +Python 3.3 -Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.org/issue12
Ezio Melotti added the comment:
Can you try to open a Windows terminal (start->run->cmd or win+r on the
keyboard), cd to Python27, execute python.exe and see if it gives any error
message there?
--
nosy: +ezio.melotti
___
Python tracker
Ezio Melotti added the comment:
The patch looks ok to me.
AFAIU the lookup will take care to normalize the name and return latin_N. This
also implies that other names (like 'latin-N', 'LaTiN~~N' and so on) will be
normalized to latin_N and then accepted.
Regarding th
Ezio Melotti added the comment:
Something like:
if name == 'mbcs' and not sys.platform.startswith('win'):
continue
should be enough.
--
___
Python tracker
<http://bu
Ezio Melotti added the comment:
I suggest to:
1) remove the alias for tactis;
2) add the aliases for latin_* and the tests for the aliases;
3) fix the email.charset to use the new aliases instead of its own dict.
2) and 3) should go on 3.3 only, 1) could be considered a bug and fixed on
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue4153>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
Fixed in r86528 (py3k) and r86529 (release31-maint), thanks!
--
nosy: +ezio.melotti
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Ezio Melotti :
--
nosy: +ezio.melotti, michael.foord
___
Python tracker
<http://bugs.python.org/issue10456>
___
___
Python-bugs-list mailing list
Unsub
Changes by Ezio Melotti :
--
nosy: +ezio.melotti, pitrou
___
Python tracker
<http://bugs.python.org/issue10458>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10459>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue9769>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10461>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10434>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
Here's a new patch with a 5 column tables. I had to use some rst trickery to
make a decent header that works both in the HTML and Latex outputs. I put the
title in the middle cell (the 3rd) of the header and left the others empty.
The column cells
Changes by Ezio Melotti :
--
nosy: +belopolsky
___
Python tracker
<http://bugs.python.org/issue9198>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10450>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
The attached patch addresses the point 1) of msg113147.
--
keywords: +patch
Added file: http://bugs.python.org/file19677/issue9424.diff
___
Python tracker
<http://bugs.python.org/issue9
Ezio Melotti added the comment:
I uploaded the patch on http://codereview.appspot.com/3232042 too.
--
___
Python tracker
<http://bugs.python.org/issue9
Ezio Melotti added the comment:
Committed in r86596.
--
___
Python tracker
<http://bugs.python.org/issue9424>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
I would prefer to keep the doc for float() simple, including what it accepts
(numbers and strings) and a few examples like ``'1.2'``, ``'.5'``, ``' +3 '``,
``'inf'``, ``'NaN'``.
Even if the other informatio
Ezio Melotti added the comment:
I merged the patch on 3.1 in r86629 and on 2.7 in r86637.
I would like to propose the following deprecation schedules for the deprecated
fail* and assert* methods:
* for the fail* methods:
add a DeprecationWarning in 3.1 (done in r74096);
remove them in
Ezio Melotti added the comment:
The attached patch (issue9424-2.diff) addresses the point 2) of msg113147.
--
Added file: http://bugs.python.org/file19755/issue9424-2.diff
___
Python tracker
<http://bugs.python.org/issue9
Ezio Melotti added the comment:
Committed in r86690 on py3k, blocked in r86691 and r88692 on 3.1/2.7.
--
___
Python tracker
<http://bugs.python.org/issue9
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10087>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issue10509>
___
___
Python-bugs-list mai
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10521>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
Committed in r86732 on py3k, will backport on 3.1/2.7 if Benjamin is OK with
that.
--
nosy: +benjamin.peterson
___
Python tracker
<http://bugs.python.org/issue10
Ezio Melotti added the comment:
I'm not sure it's worth bringing callable() back at this point.
It would have made more sense for 3.1, but now we already have 2
callable()-less versions of Python if we do it for 3.2 (what about the
moratorium though?) or 3 if we do it for 3.3
Ezio Melotti added the comment:
Backported in r86735 (3.1) and r86736 (2.7).
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Ezio Melotti added the comment:
I think that methods like str.isalpha can and should be fixed. Since
_PyUnicode_IsAlpha now accepts a Py_UCS4, the body of unicode_isalpha can be
changed to convert normal chars and surrogates pairs to a Py_UCS4 before
calling Py_UNICODE_ISALPHA.
The attached
Changes by Ezio Melotti :
--
nosy: +amaury.forgeotdarc
___
Python tracker
<http://bugs.python.org/issue10521>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
Instead of turning warnings on by default in regrtest, it would be better to do
it directly in unittest. I'll close this and open a new issue for that.
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open ->
New submission from Ezio Melotti :
Warnings should be on by default in unittest so that developers can see them
while running the tests even if they are silenced by default in Python.
The plan is to add a "warnings" argument to TestProgram and the default
TextTestRunner:
* if th
Ezio Melotti added the comment:
See #10535.
--
___
Python tracker
<http://bugs.python.org/issue9424>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
> * Moving the docs for type specific equality methods inside the docs for
> assertEqual to emphasize that those get dispatched automatically and need not
> be called directly.
I already fixed this on py3k, adding a section where the type-specific met
Ezio Melotti added the comment:
The last 4 functions are "Non-essential Built-in Functions"[0] so I kept them
at the end of the list to match the order they have in the page.
[0]:
http://docs.python.org/library/functions.html#non-essential-built-in
Ezio Melotti added the comment:
I don't think it's worth changing it. The table still provides a good overview,
and having them at the end won't prevent people to find their doc.
Both the table and the page could be divided in sections though, if we find a
way to group all the
Ezio Melotti added the comment:
If I implement what I suggested in #10535, it will be possible to deprecate
them without too much trouble. I offer to do it after #10535.
--
___
Python tracker
<http://bugs.python.org/issue10
Ezio Melotti added the comment:
Here's a working patch (without docs and tests).
I managed to filter the warnings by message without introducing a new type of
warning. As it is, all the warnings related to deprecated unittest methods are
printed only once per module, regardless of
Ezio Melotti added the comment:
I agree that s.center(char, n).encode('utf-8') should be the same on both the
builds -- even if their len() will be different -- for the following reasons:
1) the string will eventually be encoded, and if they the result is the same on
both build
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10552>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
This is not yet fixed but will be addressed in #10521 and #10542.
--
___
Python tracker
<http://bugs.python.org/issue7
Ezio Melotti added the comment:
> * the Py_UNICODE_JOIN_SURROGATES() macro should use Py_UCS4 as prefix since
> it returns Py_UCS4 values, i.e. Py_UCS4_JOIN_SURROGATES()
> * same for the Py_UNICODE_NEXT() macro, i.e. Py_UCS4_NEXT()
I'm not so familiar with the prefix conventions
Changes by Ezio Melotti :
--
title: UCS4 build incorrectly translates cases for non-BMP code points ->
narrow build incorrectly translates cases for non-BMP code points
___
Python tracker
<http://bugs.python.org/iss
Ezio Melotti added the comment:
AFAIU the macro returns lone surrogates as they are, this means that:
1) if the string contains only surrogate pairs, Py_UNICODE_NEXT will iterate
on scalar values[0];
2) if the string contains only lone surrogates, it will iterate on
codepoints[1];
3) if
Ezio Melotti added the comment:
I think float() should support non-ascii digits but I agree that it would be
better to avoid UnicodeErrors and convert them to ValueErrors so that
>>> float('١٢٣٤.٥٦')
1234.56
and
>>> float('½')
Traceback (most re
Ezio Melotti added the comment:
FWIW the UnicodeError comes from PyUnicode_EncodeDecimal (unicodeobject.c:6212)
and the "ValueError: could not convert string to float" with the buggy � comes
from PyOS_string_to_double (pystrtod.c:316). Maybe PyOS_string_to_double
should be fixed
Ezio Melotti added the comment:
What about "In order to use ``sys.argv`` you have to import the :mod:`sys`
module doing ``import sys``.".
"reference" sounds weird to me, and imho saying "import the module" is ok even
if imports have not been introduced yet. If th
Ezio Melotti added the comment:
I checked both the 3.1.2 and 3.1.3 x86 msi installers on windows xp machine
using Avast and it didn't find anything.
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/is
Ezio Melotti added the comment:
Attached a new patch.
A few comments about it:
1) A new category for UnittestWarnings could still be added to make it easier
to filter warnings using the -W python flags and thus providing more control;
2) I didn't change the deprecation message in the
Changes by Ezio Melotti :
Removed file: http://bugs.python.org/file19867/issue10535-2.diff
___
Python tracker
<http://bugs.python.org/issue10535>
___
___
Python-bug
Changes by Ezio Melotti :
Added file: http://bugs.python.org/file19868/issue10535-2.diff
___
Python tracker
<http://bugs.python.org/issue10535>
___
___
Python-bugs-list m
Ezio Melotti added the comment:
3.1 should also be considered if the tests are moved. In theory this is not a
bug fix so it shouldn't go in 3.1, but in practice it will make merging more
difficult. This might not be a strong argument though, considering that 3.1
will accept only sec
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10575>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
Committed in r86908. I'll leave this open because there still a few things
(proposed in the previous message) that can be changed/improved.
--
___
Python tracker
<http://bugs.python.org/is
Ezio Melotti added the comment:
s/regexp/regex/ done in r86910.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10594>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
Thanks for the patch! Can you include also a test that verifies that the repr
is printed correctly?
(You can take a look at #7310 if you want to see a possible approach.)
--
___
Python tracker
<h
Changes by Ezio Melotti :
--
assignee: -> d...@python
components: +Documentation
nosy: +d...@python, ezio.melotti
___
Python tracker
<http://bugs.python.org/issu
Ezio Melotti added the comment:
The deprecation notes in the doc should be quite easy to find and can be more
verbose, but there are a few cases where the deprecation is not about a
specific function but something more "abstract" (e.g. some syntax change, or
the "Overridin
Changes by Ezio Melotti :
--
versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bug
Ezio Melotti added the comment:
testing autonosy for release managers with release blockers
--
nosy: +barry, benjamin.peterson, ezio.melotti, georg.brandl
priority: normal -> release blocker
___
Python tracker
<http://bugs.python.org/iss
Ezio Melotti added the comment:
Works fine. Now release managers will be added automatically to the nosy list
when the priority of an issue is set to 'release blocker'.
See http://psf.upfronthosting.co.za/roundup/meta/issue363
--
priority: release blocker
Changes by Ezio Melotti :
--
nosy: -ajaksu2, barry, benjamin.peterson, georg.brandl, loewis
versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2
___
Python tracker
<http://bugs.python.org/issue2
Changes by Ezio Melotti :
--
priority: normal -> release blocker
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-
Changes by Ezio Melotti :
--
priority: release blocker -> deferred blocker
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/issue2771>
___
_
Changes by Ezio Melotti :
--
nosy: +georg.brandl
priority: deferred blocker -> release blocker
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/iss
Changes by Ezio Melotti :
--
nosy: -georg.brandl
priority: release blocker -> deferred blocker
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Py
Changes by Ezio Melotti :
--
priority: deferred blocker -> release blocker
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/issue2771>
___
_
Changes by Ezio Melotti :
--
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
priority: release blocker ->
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bugs-list mailing list
Unsubscri
Changes by Ezio Melotti :
--
versions: -Python 3.3
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Ezio Melotti :
--
nosy: +georg.brandl
priority: -> release blocker
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/issue2771>
___
_
Changes by Ezio Melotti :
--
priority: release blocker ->
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bugs-lis
Changes by Ezio Melotti :
--
nosy: -georg.brandl
priority: -> release blocker
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bugs-lis
Changes by Ezio Melotti :
--
nosy: +georg.brandl
versions: +Python 3.2
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bugs-list mailin
Changes by Ezio Melotti :
--
nosy: -georg.brandl
priority: release blocker ->
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bugs-lis
Changes by Ezio Melotti :
--
nosy: +georg.brandl
priority: -> release blocker
___
Python tracker
<http://bugs.python.org/issue2771>
___
___
Python-bugs-lis
Changes by Ezio Melotti :
--
nosy: -georg.brandl
priority: release blocker ->
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/iss
Ezio Melotti added the comment:
If you want to work on this you should also consider that the URLs used on
docs.python.org don't necessary match the directory structure present when
building the doc locally. For example here it would be:
.../py3k/library/fractions.html
.../release31-
Changes by Ezio Melotti :
--
assignee: michael.foord -> ezio.melotti
nosy: +ezio.melotti
stage: -> needs patch
___
Python tracker
<http://bugs.python.org/i
New submission from Ezio Melotti :
The attached patch against 2.7 adds a new fixer to 2to3 that replaces
deprecated unittest method names with the correct ones.
There are a few issues:
1) only the "safe" renamings are included; the
assert[SameElements|ItemsEqual|CountEqual] and th
Ezio Melotti added the comment:
The CSS also has a validation error, some warnings and could be written better
IMHO (specifically I don't like the placement of the {}).
I also don't believe that extensive CSS resets are useful -- they usually just
lead to lot of redefining. I usu
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue10659>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
Fixed in 3.2 (r87368) and 3.1 (r87370), thanks for the patch!
--
assignee: -> ezio.melotti
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tr
Ezio Melotti added the comment:
The attached patch changes the following things
- assertDictContainsSubset(expected, actual, msg=None)
+ assertDictContainsSubset(subset, dictionary, msg=None)
This doesn't change the order of the args, even though the name of the method
might sugges
Ezio Melotti added the comment:
Fixed in r87389. This can be backported to 3.1/2.7 where applicable.
--
stage: needs patch -> commit review
Added file: http://bugs.python.org/file20105/issue10573.diff
___
Python tracker
<http://bugs.pyth
Ezio Melotti added the comment:
A few comments about css_v2.diff:
1) when the value is '0', there's no need to specify the unit (e.g. 0em);
2) when the color is specified the background-color should be specified as well
(and vice versa);
3) hex colors (e.g. #00FF00) should
Changes by Ezio Melotti :
--
nosy: +ezio.melotti
___
Python tracker
<http://bugs.python.org/issue5846>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ezio Melotti added the comment:
I agree that it would be nice to have a cheatsheet somewhere, possibly in the
official doc and not as a plain txt file in Misc/.
FWIW another cheatsheet updated to 2.6 can be found here:
http://rgruet.free.fr/PQR26/PQR2.6.html
--
keywords: +gsoc
nosy
Ezio Melotti added the comment:
Leaving it in the wiki for a while so that the community can update and improve
it might be a good idea, but ultimately I think it should go in the doc.
--
___
Python tracker
<http://bugs.python.org/issue4
1301 - 1400 of 5818 matches
Mail list logo
