As discussed in #10, the two main user/dev sections could be renamed so the first is just 'Useful Python 3 features' and the second is 'Advanced Python 3 features' or something like this.

https://eev.ee/blog/2016/07/31/python-faq-why-should-i-use-python-3/

Just posting this here for cross referencing, feel free to close the issue :-)

It might be a good idea to have a special dedicated page for how to set up Python 2/3 environments and be able to switch between them, for different installation methods. For instance, conda could be the first section in that page, but we could also have MacPorts, homebrew, linux package managers, etc.

See PEP 515 - need to add a section about this to the main new features page. Anyone interested in writing that?

This is a pretty useful Python 3 package for advanced users/developers.

2to3 is no longer the main suggestion people use to update code. Instead, people generally suggest tools like modernize or futurize. See e.g. the CPython docs.

We need to make sure:

• The docs build without warnings
• The examples run

I don't have time to write it up just now, but open(..., mode='x') is a nice addition. It opens a file for writing, raising an error if it already exists. This probably belongs in the advanced section.

https://github.com/OpenAstronomy/python-3-for-scientists/blob/master/python3_user_transition_guide.rst

Looks like the docs now need Sphinx 1.6 to build but RTD uses 1.5. I'll see if there is a way to force 1.6 to be used.