[issue10461] Use with statement throughout the docs
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10461 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10434] Document the rules for public names
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10434 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10299] Add index with links section for built-in functions
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. The column cells are a little wider but they are still OK at 800x600. Éric how do you like this version? I could also drop the header altogether, but I don't like the headless table too much. -- Added file: http://bugs.python.org/file19648/issue10299-2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10299 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9198] Should repr() print unicode characters outside the BMP?
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +belopolsky ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9198 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10450] Fix markup in Misc/NEWS
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10450 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9424] Disable unittest.TestCase.assertEquals and assert_ during a regrtest run
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://bugs.python.org/issue9424 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9424] Disable unittest.TestCase.assertEquals and assert_ during a regrtest run
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9424] Disable unittest.TestCase.assertEquals and assert_ during a regrtest run
Ezio Melotti ezio.melo...@gmail.com added the comment: Committed in r86596. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9424 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10488] Improve documentation for 'float' built-in.
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 this is the best place where to include it, and I think it might be confusing for unexperienced users. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10488 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9424] Disable unittest.TestCase.assertEquals and assert_ during a regrtest run
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://bugs.python.org/issue9424 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9424] Disable unittest.TestCase.assertEquals and assert_ during a regrtest run
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10087] HTML calendar is broken
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10087 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10509] PyTokenizer_FindEncoding can lead to a segfault if bad characters are found
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10521 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10299] Add index with links section for built-in functions
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10518] Bring back callable()
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 it for 3.3. Also if isinstance(obj, collections.Callable) is correct in what it does, it's trivial to do something like: def callable(obj): return isinstance(obj, collections.Callable) If it goes in the `iscallable` name suggested on python-dev might be better (IMHO). At least people will realize that it's something new and don't assume that the old callable() has been there all the time (it also clear that it returns a boolean and reads better in e.g. `if iscallable(obj): ...`). (The patch should also include an entry in the table at the top of functions.rst now that I committed #10299 in r86732.) -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10518 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10299] Add index with links section for built-in functions
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://bugs.python.org/issue10299 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build
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 Py_UNICODE_ISALPHA.
The attached patch is a proof of concept of this approach and returns True for
'\N{OLD ITALIC LETTER A}'.isalpha() on a narrow build.
It still has a number of issues that should be addressed (check for narrow
builds, check for lone surrogates, check for high surrogate at the end of a
string, fix compiler warnings ...) but it should be good enough as a PoC.
I would also suggest to introduce a set of macros to handle surrogates (e.g.
detect, combine) and use it in all the functions that need to work with them.
--
keywords: +patch
Added file: http://bugs.python.org/file19809/issue10521-isalpha.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10521
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +amaury.forgeotdarc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10521 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9424] Deprecate assertEquals, assertNotEquals, assert_, assertAlmostEquals, assertNotAlmostEquals
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 - closed title: Disable unittest.TestCase.assertEquals and assert_ during a regrtest run - Deprecate assertEquals, assertNotEquals, assert_, assertAlmostEquals, assertNotAlmostEquals ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9424 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10535] Enable warnings by default in unittest
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: * if the argument is passed always use it as a filter (e.g. default, ignore, all, ...) for warnings; * if the argument is not passed and sys.warnoptions is not [] (i.e. python has been called with -W something) don't do anything (i.e. use the warnings specified by -W); * if the argument is not passed and sys.warnoptions is [], use 'default' (i.e. show warnings). In order to prevent floods of warnings when the deprecated assertEquals, assert_, etc. are used (see #9424), a new type of warning could be created (e.g. _UnittestDeprecationWarning) and filtered so that these warnings are printed only once. -- assignee: ezio.melotti messages: 122411 nosy: brett.cannon, ezio.melotti, michael.foord priority: normal severity: normal stage: needs patch status: open title: Enable warnings by default in unittest type: feature request ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10535 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9424] Deprecate assertEquals, assertNotEquals, assert_, assertAlmostEquals, assertNotAlmostEquals
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 mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10273] Clean-up Unittest API
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-specific methods are described[0] and added a reference in the assertEqual description[1]. I also clarified that usually there's no need to call them directly even thought I don't see why they shouldn't do it if they want to use a specific test. * Changing assertRegexpMatches to assertRegex And assertNotRegexpMatches - assertNotRegex, assertRaisesRegexp - assertRaisesRegex, assertWarnsRegexp - assertWarnRegex? Will the *Regexp forms be deprecated too? [0]: http://docs.python.org/dev/py3k/library/unittest.html#type-specific-methods [1]: http://docs.python.org/dev/py3k/library/unittest.html#unittest.TestCase.assertEqual -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10273 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10299] Add index with links section for built-in functions
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 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10299 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10299] Add index with links section for 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 all the functions that makes enough sense (e.g. put together int/dict/list/set/etc, getattr/setattr/delattr, but then it's difficult to add more groups without maxing them too small). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10299 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10273] Clean-up Unittest API
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://bugs.python.org/issue10273 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10535] Enable warnings by default in unittest
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, regardless of what methods are used and how many times. I'm also thinking that it might be better to include the name of the deprecated method in the message and use three filters for fail* methods, assert* methods, and the assert*Regexp* methods that will be deprecated. This will show at worst 3 warnings per module, but the assert*Regexp* and the fail* methods are not so common, so it shouldn't be too nosy. One limitation of the patch is that the per-module special-casing for unittest is not affect by the `warnings` argument, but it can be changed when -W is used and no `warnings` arg is passed. Regrtest doesn't seem to use unittest, so it should be fixed separately (probably needs another issue). -- keywords: +patch stage: needs patch - patch review Added file: http://bugs.python.org/file19821/issue10535.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10535 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10521] str methods don't accept non-BMP fillchar on a narrow Unicode build
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 on
both builds, it will look the same too;
2) trying to keep the same len() will generate different results and it won't
work in case of odd width like 'foo'.center(surrogate_pair, 5) because you
can't put half surrogate.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10521
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10552] Tools/unicode/gencodec.py error
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10552 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7663] UCS4 build incorrectly translates cases for non-BMP code points
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
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 conventions, but wouldn't that lead users to think that this macro is for wide builds and that they have to use Py_UCS2_* macros for narrow builds? If these macros are supposed to abstract the build type maybe they should have a neutral prefix. (But if the conventions we use say otherwise I guess the best we can do is to document it properly). * in order to make the macro easier to understand, please rename it to Py_UCS4_READ_CODE_POINT(); that's a little more typing, but still a lot less than without the macro :-) The term code point is not entirely correct here. High and low surrogates are code points too. The right term should be 'scalar value' (but that might be confusing). The 'READ' bit sounds fine though, maybe 'READ_NEXT'? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7663] narrow build incorrectly translates cases for non-BMP code points
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://bugs.python.org/issue7663 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10542] Py_UNICODE_NEXT and other macros for surrogates
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 on codepoints[1]; 3) if it contains both it will be half and half (i.e. scalar values if the surrogates are in pair, or falling back on codepoints if they aren't); (for strings without surrogates, iterating on scalar values or codepoints is the same). Is this semantic correct for all (or at least most of) the places where the macro will be used? Would a stricter version (that rejects lone surrogates and iterates on scalar values only) be useful in addition or in alternative to Py_UNICODE_NEXT? [0]: http://unicode.org/glossary/#unicode_scalar_value [1]: http://unicode.org/glossary/#code_point -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10557] Malformed error message from float()
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, line 1, in module
ValueError: invalid literal for float(): ½
I.e. float should do the C equivalent of:
try:
s = arg.encode('decimal')
except UnicodeEncodeError:
raise ValueError('Invalid liter for float(): {}'.format(arg))
Note that int() and Decimal() supports non-ascii chars too.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10557
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10557] Malformed error message from float()
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 be fixed to display the string correctly, but I don't know what will be affected from that (and if it will make things worse or better). The UnicodeError can be fixed in PyFloat_FromString (floatobject.c:174). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10557 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10559] NameError in tutorial/interpreter
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 understand what importing a module means he can just execute the command as is. -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10559 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10500] Palevo.DZ worm msix86 installer 3.x installer
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://bugs.python.org/issue10500 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10535] Enable warnings by default in unittest
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 message in the patch -- I will probably do it in a separate commit; 3) The patch touches a few unrelated unittest/test/test_*.py files that were checking for the number of args explicitely; 4) In order to test the different combinations of flags/args I created a new _test_warnings.py file called from test_runner.py via subprocess; 5) unittest warnings are now printed only once even when 'always' is passed as an arg, but not when it's set with -W (this somehow addresses the limitation described in my previous message); -- Added file: http://bugs.python.org/file19867/issue10535-2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10535 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10535] Enable warnings by default in unittest
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10535] Enable warnings by default in unittest
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10572] Move unittest test package to Lib/test
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 will accept only security fixes soon and only the few developers that work on unittest will be affected. -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10572 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10575] makeunicodedata.py does not support Unihan digit data
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10575 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10535] Enable warnings by default in unittest
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://bugs.python.org/issue10535 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10273] Clean-up Unittest API
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10594] Typo in PyList_New doc.
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10594 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5587] vars() no longer has a useful __repr__
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 rep...@bugs.python.org http://bugs.python.org/issue5587 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10669] Remove Deprecation Warnings
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10669] Document Deprecation Warnings and how to fix
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, or the Overriding __eq__ blocks inheritance of __hash__ in 3.x reported by the OP). Listing new deprecations in the what's new it's a good idea, but otherwise a clear message (that also suggests how to fix the problem) and a deprecation note in the doc (using the '.. deprecated::' directive) should be enough. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10669 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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...@bugs.python.org http://bugs.python.org/issue2771 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2771 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
Changes by Ezio Melotti ezio.melo...@gmail.com: -- priority: release blocker - ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2771 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2771] test issue
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8040] It would be nice if documentation pages linked to other versions of the same document
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 .../release31-maint/library/fractions.html .../release27-maint/library/fractions.html .../release26-maint/library/fractions.html This could be addressed with a config file that is not kept under version control (and possibly with default values used when this file is not present). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8040 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10573] Consistency in unittest assert methods: order of actual, expected
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 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10712] 2to3 fixer for deprecated unittest method names
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] and the assert*Regexp*-assert*Regex* changes are missing; 2) unless 2to3 provides a way to specify a target version (e.g. 3.2 rather than just 3.x), the missing renamings can't be included; 3) the patch is against 2.7 but I'm not sure in what versions could/should be included, or if the fixer should (also|only) go on PyPI; 4) this fixer is useful from 3.1 to 3.2 too, is there a way to use it with 3.x versions only? 5) doc is still missing; -- files: issue10712.diff keywords: needs review, patch messages: 124054 nosy: benjamin.peterson, ezio.melotti, georg.brandl, michael.foord priority: normal severity: normal stage: patch review status: open title: 2to3 fixer for deprecated unittest method names type: feature request versions: Python 2.7, Python 3.2 Added file: http://bugs.python.org/file20062/issue10712.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10712 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10716] Modernize pydoc to use CSS
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 of redefining. I usually limit myself to * { margin: 0; padding: 0;
} and possibly specify specific values when necessary. Minor differences with
different browsers can be perfectly fine in lot of cases.
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10716
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10659] Hook scripts for immediate doc build system
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10659 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5587] vars() no longer has a useful __repr__
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 rep...@bugs.python.org http://bugs.python.org/issue5587 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10573] Consistency in unittest assert methods: order of actual, expected
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 might suggest the opposite. In the output message I left expected and actual because imho it makes sense there (e.g. key, expected: 3, actual: 5). This could be changed to expected/got or something else. - assertCountEqual(expected, actual, msg=None) + assertCountEqual(actual, expected, msg=None) This changes the order of the args and as a consequence the list of 'missing' and 'unexpected' elements will be swapped. The tests don't check the error message so they all pass without modification. It should be noted that this method didn't exist in 3.1. However 2.7 has the equivalent assertItemsEqual with the args swapped, so maybe it should be documented somewhere that while porting from 2.7 to 3.2 the order of the args should be changed accordingly. - assertDictEqual(expected, actual, msg=None) + assertDictEqual(dict1, dict2, msg=None) This is just a doc change, the actual method already uses d1 and d2 as args and their order doesn't seem to matter. The other methods (mainly the assert*Equal) are just documented with generic first/second or foo1/foo2. The doc for these methods could be changed to use actual/expected as a preferred order. -- keywords: +patch Added file: http://bugs.python.org/file20103/issue10573.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10573 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10573] Consistency in unittest assert methods: order of actual, expected
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...@bugs.python.org http://bugs.python.org/issue10573 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10716] Modernize pydoc to use CSS
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) should be preferred to named colors (e.g. gray);
4) some selectors and properties don't work with older browsers (e.g. E F or
min-width);
5) there are a few empty dl.*{} that I would remove (unless you plan to fill
them later);
6) the style I prefer for CSS is:
selector {
property: value;
}
Regarding the HTML:
1) using an HTML 4.01 strict doctype would be better;
2) all the style-related attributes and elements should be removed (e.g
bgcolor, valign, font);
3) using .red { color: red; } is not a good idea. Classes' names should
describe the role of the element (e.g. header, entry) and not their style
(otherwise when you want to change the page with a blue theme you'll end up
with a .red { color: blue; }). If the colors are passed directly to the HTML
they should be removed and left to the CSS(s) only. I don't know the code well
enough to say if this is doable and/or if it requires a deprecation first;
4) the lis in html_header() should be closed, same for all the other elements
that support a closing tag, even if optional (e.g. dt, dd);
There are also some minor incontinences in the indentantion, e.g.:
+link_list = ['a href=%s.html%s/a' % (name, name)
+for name in sys.builtin_module_names
+if name != '__main__']
+contents = [html.index_columns('Built-in modules',
+link_list, css_class='section modules')]
+link_list = ['a href=%s.html%s/a' % (name, name)
+ for name in sorted(Helper.keywords.keys())]
(the contents one is indented correctly), and some extra space after the '('.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10716
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5846] Deprecate obsolete functions in unittest
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 mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4819] Misc/cheatsheet needs updating
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 -- keywords: +gsoc nosy: +ezio.melotti type: - feature request ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4819 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4819] Misc/cheatsheet needs updating
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...@bugs.python.org http://bugs.python.org/issue4819 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10936] Simple CSS fix for left margin at docs.python.org
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 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10936 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9196] Improve docs for string interpolation %s re Unicode strings
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) The Python 2 doc for unicode() says[0]: For objects which provide a __unicode__() method, it will call this method without arguments to create a Unicode string. For all other objects, the 8-bit string version or representation is requested and then converted to a Unicode string using the codec for the default encoding in 'strict' mode. The doc for .__unicode__() says[1]: Called to implement unicode() built-in; should return a Unicode object. When this method is not defined, string conversion is attempted, and the result of string conversion is converted to Unicode using the system default encoding. This is consistent with unicode() doc (but it doesn't mention that 'strict' is used). It also says that the method *should* return unicode, but it can also returns a str that gets coerced by unicode(). The doc for .__str__() says[2]: Called by the str() built-in function and by the print statement to compute the “informal” string representation of an object. [...] The return value must be a string object. This is wrong because the return value can be unicode too (this has been changed at some point, it used to be true on older versions). That said, some of the behaviors described by Craig (e.g. __str__ that returns unicode) are not documented and documenting them might save some confusion. However these weird behaviors are most likely errors and the fact that there are no exception is just because Python 2 is not strict with str/unicode. I think a better way to solve the problem is to document clearly how these methods should be used (i.e. if __unicode__ should be preferred over __str__, if it's necessary to implement both, what they should return, etc.). [0]: http://docs.python.org/library/functions.html#unicode [1]: http://docs.python.org/reference/datamodel.html#object.__unicode__ [2]: http://docs.python.org/reference/datamodel.html#object.__str__ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9196 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10573] Consistency in unittest assert methods: order of actual, expected
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. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10573 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10936] Simple CSS fix for left margin at docs.python.org
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-width; 2) like 1) but also collapse the sidebar automatically when its width gets smaller than the min-width; 3) leave a fixed width but make the sidebar mouse-resizable (that will conflict with the collapsibility though and is less trivial to do); -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10936 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10936] Simple CSS fix for left margin at docs.python.org
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 of the sidebar is given by the margin-left of the bodywrapper, and there's no min-margin-left property that can be used instead; The font size can probably be changed to fit the width of the sidebar, but the min-width problem remains (I'm thinking about small screens -- e.g. smartphones -- where the sidebar would end up having a width of ~130-160px (I haven't (yet) tested it there though)). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10936 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10775] assertRaises as a context manager should accept a 'msg' keyword argument.
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10775 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10675] unittest should have an assertChanges context manager
Changes by Ezio Melotti ezio.melo...@gmail.com: -- components: +Tests nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10675 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10967] move regrtest over to using more unittest infrastructure
Changes by Ezio Melotti ezio.melo...@gmail.com: -- keywords: +gsoc nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10967 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11071] What's New review comments
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11071 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11049] add tests for test.support
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11049 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10979] setUpClass exception causes explosion with -b
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10979 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11167] Overflow in unicode_hash
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11167 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11234] Possible error in What's new Python3.2(rc3) documentation (sysconfig.get_config_var)
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11234 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11248] Tails of generator get lost under zip()
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://docs.python.org/library/itertools.html#itertools.izip_longest -- nosy: +ezio.melotti resolution: - invalid stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11248 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11248] Tails of generator get lost under zip()
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 should use a try/finally in the generator. Relying on the number of elements of another generator used together with zip() seems very fragile to determine when/if a clean-up should be done (what if the other generator has a different number of elements? what if an exception is raised before it's fully consumed? what if you use the generator in for/while loop and break the loop before reaching the end? ...). c) even if you consider it as a wart, changing it for zip() will break compatibility and it's against the language moratorium. This behavior is also useful if e.g. you have the generators g1 that yields 1 2 3, g2 that yields 4 5 6, and g3 that yields a b c d e f and you want to first zip(g1, g3) and get 1a 2b 3c and then continue with zip(g2, g3) and get 4d 5e 6f. Checking in the first zip() if g3 reached its end or not would mean consuming the 'd', and that would be a worse wart imho. -- nosy: +eric.araujo, georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11248 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11233] clarifying Availability: Unix
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11233 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11272] input() has trailing carriage return on windows
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti, georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11272 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11272] input() has trailing carriage return on windows
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/issue11272 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11272] input() has trailing carriage return on windows
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-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10924] Adding salt and Modular Crypt Format to crypt library.
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 salt values instead of string.ascii_letters; According to the PEP8 there shouldn't be any spaces after the '[' and before the ']' (e.g. method_list = [ METHOD_SHA512, METHOD_SHA256, METHOD_MD5 ] and in the listcomps) and around the = in the function/method declarations/calls (e.g. def crypt(word, salt = None):). -- keywords: +buildbot nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10924 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11283] incorrect pattern in the re module docs for conditional regex
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11283 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
