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:
Also, a friend
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-import
got me thinking
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net:
--
nosy: +rbp
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10351
___
___
Python-bugs-list
Rodrigo Bernardo Pimentel r...@isnomore.net 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
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net:
--
nosy: +rbp
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9063
___
___
Python-bugs-list
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net:
--
nosy: +rbp
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9305
___
___
Python-bugs-list
Rodrigo Bernardo Pimentel r...@isnomore.net 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 standard
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net:
--
nosy: +rbp
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10220
___
___
Python-bugs-list
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net:
--
nosy: +rbp
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5131
___
___
Python-bugs-list
Rodrigo Bernardo Pimentel r...@isnomore.net 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
Rodrigo Bernardo Pimentel r...@isnomore.net 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 rep...@bugs.python.org
Rodrigo Bernardo Pimentel r...@isnomore.net 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
Rodrigo Bernardo Pimentel r...@isnomore.net 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.
--
nosy
New submission from Rodrigo Bernardo Pimentel r...@isnomore.net:
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 *list*. It should read
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net:
Added file: http://bugs.python.org/file18915/alist_doc-3.x.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9891
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net:
--
nosy: +rbp
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2516
___
___
Python-bugs-list
Rodrigo Bernardo Pimentel r...@isnomore.net 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
Rodrigo Bernardo Pimentel r...@isnomore.net 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
Changes by Rodrigo Bernardo Pimentel r...@isnomore.net:
--
nosy: +rbp
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1293741
___
___
Python-bugs
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]
http://bugs.python.org/issue3417
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 implementation at
http
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 this, along
Rodrigo Bernardo Pimentel [EMAIL PROTECTED] added the comment:
+1 for going ahead and writing a fixer.
--
nosy: +rbp
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2805
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 patch for it (svn tag
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' case (on
the switch where
Changes by Rodrigo Bernardo Pimentel [EMAIL PROTECTED]:
--
nosy: +rbp
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2532
__
___
Python-bugs-list mailing list
26 matches
Mail list logo