Roundup Robot added the comment:
New changeset 863b8e71cfee by Brett Cannon in branch 'default':
Issue #20208: Clarify some things in the Python porting HOWTO.
http://hg.python.org/cpython/rev/863b8e71cfee
--
nosy: +python-dev
___
Python tracker
Changes by Brett Cannon br...@python.org:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20208
___
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 was
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
Brett Cannon added the comment:
There's actually no way to tweak that formatting as that is all done by Sphinx
automatically.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20208
___
New submission from Brett Cannon:
Reported on my G+ share of the latest reworking:
The only part I found confusing is when you first introduce from _future_
import unicode_literals --- it looks like you forgot to explain what it does.
It turns out that you explain it somewhat two paragraphs
Changes by Dmitry Shachnev mity...@gmail.com:
--
nosy: +mitya57
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20208
___
___
Python-bugs-list
