[issue20208] Clarify some things in porting HOWTO

Rodrigo Bernardo Pimentel added the comment: BTW, there remains another concern I mentioned on G+: """ A note on formatting: I found some of 4th- and 5th-level headings too subtle. For instance, http://docs.python.org/dev/howto/pyporting.html#from-future-import-absolute

[issue20208] Clarify some things in porting HOWTO

Rodrigo Bernardo Pimentel added the comment: I've created a patch that addresses the first criticism (explaining unicode_literals), as well as the first mention of print_function. It also addresses a small concern regarding "map", which I've mentioned in my G+ comment: &q

[issue9063] TZ examples in datetime.rst are incorrect

Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue9063> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10427] 24:00 Hour in DateTime

Rodrigo Bernardo Pimentel added the comment: I was writing tests for this issue, when something struck me: ok, datetime(year, month, day, 24) is valid. But is datetime(year, month, day, 24, 1) valid? Or datetime(year, month, day, 24, 0, 0, 1)? I would say those aren't valid, although

[issue10351] Add autocompletion for keys in dictionaries

Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue10351> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10220] Make generator state easier to introspect

Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue10220> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue9305] Don't use east/west of UTC in date/time documentation

Rodrigo Bernardo Pimentel added the comment: 1. Done (it's on the patch I'm uploading). Sorry. 3. Ok, we've rewritten that sentence. As Henrique mentioned, we're working on a larger patch to make datetime documentation clearer, and we can include a definition of "sta

[issue9305] Don't use east/west of UTC in date/time documentation

Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue9305> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue5131] pprint doesn't know how to print a defaultdict

Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue5131> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3976] pprint._safe_repr is not general enough in one instance

Rodrigo Bernardo Pimentel added the comment: Armin: this has the problem that, if the object you're trying to compare is a class, self.obj.__lt__ expects a different number of parameters (i.e., it expects the instance). See issue 10017 . Testing with "<" works. ---

[issue10017] pprint.pprint raises TypeError on dictionaries with user-defined types as keys

Rodrigo Bernardo Pimentel added the comment: If I'm understanding this correctly, this fails on 3.1 and not (although, actually, it does) on py3k/3.2 because: * pprint._safe_key.__lt__ checks "rv = self.obj.__lt__(other.obj)" and falls back to id comparison if rv is NotImplem

[issue10017] pprint.pprint raises TypeError on dictionaries with user-defined types as keys

Rodrigo Bernardo Pimentel added the comment: FWIW, the problem still occurs on the most recent release31-maint checkout (as of r85323), and does not happen on py3k (3.2a2). -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue10

[issue10047] python-2.6.6 coredump running newspipe

Rodrigo Bernardo Pimentel added the comment: Does this always happen with a particular feed? Could you provide us with a configuration that reproduces the problem? Also, as R. David Murray asked, does this happen with 2.7? -- nosy: +rbp ___ Python

[issue9891] Minor doc typo at datamodel.rst: "list" -> "alist"

Changes by Rodrigo Bernardo Pimentel : Added file: http://bugs.python.org/file18915/alist_doc-3.x.patch ___ Python tracker <http://bugs.python.org/issue9891> ___ ___ Pytho

[issue9891] Minor doc typo at datamodel.rst: "list" -> "alist"

New submission from Rodrigo Bernardo Pimentel : The "Built-in methods" item of the "The standard type hierarchy" section of Doc/reference/datamodels.rst uses a list instance called "alist" as an example, and it says "__self__ is set to the object denoted by *

[issue2516] Instance methods are misreporting the number of arguments

Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue2516> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6583] 2to3 fails to fix test.test_support

Rodrigo Bernardo Pimentel added the comment: Pascal is correct, trunk Doc/library/test.rst still says: "The 2to3 tool will automatically adapt imports when converting your sources to 3.0." Perhaps this should simply be changed to "The 2to3 tool will not automatically convert

[issue7583] Improve explanation of tab expansion in doctests

Rodrigo Bernardo Pimentel added the comment: I've just been bitten by this, and I agree the language in the docs is very inappropriate (made me angry for a minute :)). One suggestion: "While not everyone might believe tabs should mean that, doctests are primarily aimed at document

[issue1293741] doctest runner cannot handle non-ascii characters

Changes by Rodrigo Bernardo Pimentel : -- nosy: +rbp ___ Python tracker <http://bugs.python.org/issue1293741> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3417] make the fix_dict fixer smarter

Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: (I've just realized it's not working properly for fix_dict; I'm fixing it and will drop a note here when it is) ___ Python tracker <[EMAIL PROTECTED]> <ht

[issue3417] make the fix_dict fixer smarter

Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: I haven't managed to successfully complete the summer of code, due to some personal problems, but I'm still working on 2to3 and on confidence ranking for it. There's a bzr branch with its current i

[issue1713041] fix for 1712742: corrects pprint's handling of 'depth'

Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: It seems that somewhere along the road between revision 55144 (where the first patch was generated) and current trunk (revision 63129), PrettyPrinter._format has stopped handling depth! I've attached a patch that fixes

[issue2723] Truncate __len__() at sys.maxsize

Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: I think returning sys.{maxint,maxsize} in this case is a plain lie. That's not practicality, that's giving back false information. Barring drastic language changes (such as having objects representing "infin

[issue2798] Crash on non-Windows if Python runs from a non-ASCII directory

Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: The patch works for me, and I agree the test_xmlrpc is an xmlrpc issue. Perhaps unrelated to this issue, but I think it makes this whole unicode getargs situation fragile: I could not understand why the 'z' cas

[issue2803] heapq.heappush called with too few arguments in sched.py

Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: +1 on the patch. IIRC, there won't be any more bugfix releases for 2.5.x, but, just in case: the patch doesn't work on 2.5 (though the issue lists it as an affected version - and it is!), so I'm uploading a

[issue2805] 2to3 doesn't correct divisions

Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]> added the comment: +1 for going ahead and writing a fixer. -- nosy: +rbp __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2532] file that breaks 2to3 (despite being correct python)

Changes by Rodrigo Bernardo Pimentel <[EMAIL PROTECTED]>: -- nosy: +rbp __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2532> __ ___ Python-bugs