Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 8 additions & 13 deletions python3_user_transition_guide.rst
Original file line number Diff line number Diff line change
@@ -1,19 +1,14 @@
Python 3 transition guide
=========================

Switching to Python 3 can seem like a daunting task, but this guide will
provide some tips and resources to help make it more straightforward.

Changes you can make today to make the transition easier
--------------------------------------------------------

Writing Python 3 compatible code
================================
Any new code you write can easily be Python 3 compatible! This is the first step
you can take towards switching. Thankfully, the most disruptive changes to the
language have been back-ported to Python 2 so you can ensure that, when writing
you can take towards switching. For scientific scripts, being Python 3 combatible
tends to imply Python 2 compatability.

Thankfully, the most disruptive changes to the
language have been back-ported to Python 2 so you can ensure that when writing
new code that you intend to execute with Python 2, it will be executable in
Python 3 once you switch. To use these back-ported changes, you must import
certain utilities from the built-in ```__future__``
<https://docs.python.org/2/library/__future__.html>`_ package. It is generally
certain utilities from the built-in ``__future__`` package. It is generally
Copy link
Collaborator

@ngoldbaum ngoldbaum Jul 15, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should maintain the inline link to the python docs.

recommended that, if you are still writing Python 2 compatible code, you should
import the following four modules in any code you write::

Expand Down