Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10461
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10434
___
___
Python-bugs
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +belopolsky
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9198
___
___
Python-bugs-list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10450
___
___
Python-bugs
Ezio Melotti ezio.melo...@gmail.com 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 rep...@bugs.python.org
http
Ezio Melotti ezio.melo...@gmail.com added the comment:
I uploaded the patch on http://codereview.appspot.com/3232042 too.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9424
Ezio Melotti ezio.melo...@gmail.com added the comment:
Committed in r86596.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9424
___
___
Python
Ezio Melotti ezio.melo...@gmail.com 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 information is still valuable, I'm not sure
Ezio Melotti ezio.melo...@gmail.com 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 rep...@bugs.python.org
http
Ezio Melotti ezio.melo...@gmail.com added the comment:
Committed in r86690 on py3k, blocked in r86691 and r88692 on 3.1/2.7.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9424
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10087
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10509
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10521
___
___
Python-bugs
Ezio Melotti ezio.melo...@gmail.com 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 rep...@bugs.python.org
http://bugs.python.org/issue10299
Ezio Melotti ezio.melo...@gmail.com 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
Ezio Melotti ezio.melo...@gmail.com added the comment:
Backported in r86735 (3.1) and r86736 (2.7).
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +amaury.forgeotdarc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10521
___
___
Python
Ezio Melotti ezio.melo...@gmail.com 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 ezio.melo...@gmail.com:
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
Ezio Melotti ezio.melo...@gmail.com added the comment:
See #10535.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9424
___
___
Python-bugs-list
Ezio Melotti ezio.melo...@gmail.com 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
Ezio Melotti ezio.melo...@gmail.com 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-functions
Ezio Melotti ezio.melo...@gmail.com 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
Ezio Melotti ezio.melo...@gmail.com 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 rep...@bugs.python.org
http
Ezio Melotti ezio.melo...@gmail.com 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
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10552
___
___
Python-bugs
Ezio Melotti ezio.melo...@gmail.com added the comment:
This is not yet fixed but will be addressed in #10521 and #10542.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7663
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
title: UCS4 build incorrectly translates cases for non-BMP code points -
narrow build incorrectly translates cases for non-BMP code points
___
Python tracker rep...@bugs.python.org
http
Ezio Melotti ezio.melo...@gmail.com 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
Ezio Melotti ezio.melo...@gmail.com 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 recent call last):
File stdin
Ezio Melotti ezio.melo...@gmail.com 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
Ezio Melotti ezio.melo...@gmail.com 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 the user doesn't
Ezio Melotti ezio.melo...@gmail.com 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 rep...@bugs.python.org
http
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
Removed file: http://bugs.python.org/file19867/issue10535-2.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10535
Changes by Ezio Melotti ezio.melo...@gmail.com:
Added file: http://bugs.python.org/file19868/issue10535-2.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10535
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10575
___
___
Python-bugs
Ezio Melotti ezio.melo...@gmail.com 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 rep...@bugs.python.org
http
Ezio Melotti ezio.melo...@gmail.com added the comment:
s/regexp/regex/ done in r86910.
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10273
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10594
___
___
Python-bugs
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
assignee: - d...@python
components: +Documentation
nosy: +d...@python, ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10669
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Ezio Melotti ezio.melo...@gmail.com 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 rep
Ezio Melotti ezio.melo...@gmail.com 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 ezio.melo...@gmail.com:
--
nosy: -ajaksu2, barry, benjamin.peterson, georg.brandl, loewis
versions: -Python 2.6, Python 2.7, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
priority: normal - release blocker
versions: +Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
priority: release blocker - deferred blocker
versions: -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +georg.brandl
priority: deferred blocker - release blocker
versions: +Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: -georg.brandl
priority: release blocker - deferred blocker
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
priority: deferred blocker - release blocker
versions: -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
versions: +Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
priority: release blocker -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
___
___
Python
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
versions: -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +georg.brandl
priority: - release blocker
versions: +Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
priority: release blocker -
versions: -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: -georg.brandl
priority: - release blocker
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +georg.brandl
versions: +Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: -georg.brandl
priority: release blocker -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +georg.brandl
priority: - release blocker
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: -georg.brandl
priority: release blocker -
versions: -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2771
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
assignee: michael.foord - ezio.melotti
nosy: +ezio.melotti
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10573
New submission from Ezio Melotti ezio.melo...@gmail.com:
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
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10659
___
___
Python-bugs
Ezio Melotti ezio.melo...@gmail.com 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 tracker
Ezio Melotti ezio.melo...@gmail.com 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
Ezio Melotti ezio.melo...@gmail.com 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 rep
Ezio Melotti ezio.melo...@gmail.com 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
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5846
___
___
Python-bugs-list
Ezio Melotti ezio.melo...@gmail.com 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
Ezio Melotti ezio.melo...@gmail.com 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 rep
Ezio Melotti ezio.melo...@gmail.com added the comment:
If the width is specified with a percentage, a min-width should be specified
too.
In the py3k doc the sidebar can be collapsed though, so I'm not sure it's worth
changing this. Georg?
--
keywords: +easy
stage: - needs patch
Ezio Melotti ezio.melo...@gmail.com added the comment:
Python 3 checks the return types of __bytes__ and __str__, raising an error if
it's not bytes and str respectively:
str(C())
TypeError: __str__ returned non-string (type bytes)
bytes(C())
TypeError: __bytes__ returned non-bytes (type str
Ezio Melotti ezio.melo...@gmail.com added the comment:
Not all the arg names in the doc match with the actual name of the args
(probably because the methods are expected to be used with positional args
only), that's why the changes affects only the doc
Ezio Melotti ezio.melo...@gmail.com added the comment:
The min-width is necessary in case the CSS is changed to resize the sidebar
dynamically. If it gets too narrow it would start getting unusable and the text
will start overflowing.
Possible alternatives are:
1) use a percentage and min
Ezio Melotti ezio.melo...@gmail.com added the comment:
I did some tests using 20% instead of 230px and found the following problems:
1) while zooming, even if the width of the sidebar doesn't change, the font
size does, overflowing from the sidebar;
2) min-width can't be used because the width
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10775
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
components: +Tests
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10675
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +gsoc
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10967
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11071
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11049
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10979
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11167
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +rhettinger
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11234
___
___
Python-bugs-list
Ezio Melotti ezio.melo...@gmail.com added the comment:
This behavior is documented[0]:
The returned list is truncated in length to the length of the shortest
argument sequence.
You can use izip_longest instead[1].
[0]: http://docs.python.org/library/functions.html#zip
[1]: http
Ezio Melotti ezio.melo...@gmail.com added the comment:
a) that's true, even if the behavior makes sense (when the first generator ends
there's no reason to see what's next in the second). Georg, do you think it
should be documented?
b) if you want to be sure that some clean-up is executed you
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11233
___
___
Python-bugs
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti, georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11272
Ezio Melotti ezio.melo...@gmail.com added the comment:
Confirmed on Python 3.2 (winxp). The problem doesn't seem to exist on 3.1.3.
--
priority: normal - critical
stage: - test needed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +pitrou, v+python
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11272
___
___
Python-bugs
Ezio Melotti ezio.melo...@gmail.com added the comment:
Some buildbots are failing after the commit.
Also in the crypt.py module I still see things that according to msg126453
should be fixed already:
* more statements on the same line (e.g. if salt == None: salt = mksalt());
* the hardcoded
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11283
___
___
Python-bugs
1 - 100 of 5772 matches
Mail list logo
