If you want your own Python 2.7.11, or Python 3.5.1, use homebrew and install these Python environments into your /usr/local/bin and /usr/local/lib locations. Then you need a means to switch your Python library paths between the two versions, and away from Apple's Python 2.7.10 environment. If you Google Python version manager, you will get hits for pyenv and others. As a die hard, I patched the discontinued Pythonbrew and still use it to install and manage multiple Python versions, which I can switch to with ease. Any Python solutions that I post in the support communities only use built-in Python modules.
Some of Apple's own products depend on the OS X installed version of Python. Additionally, the Python Scripting Bridge expects Apple's Python. This allows one to write Python-Objective-C code, but only in Apple's Python installation. The PDF watermark action in Automator uses Python, as do many other obscure OS X installed bits.
Python dot org has documentation that talks about differences between Python 2 and 3. I have written Python applications that automatically run correctly under Python 2.7.10, 2.7.11, and Python 3.5.1 without any changes. Some Python 3 features have already been back ported to Python 2.7.11.
To find how to do something in Python, type the following question format in your browser: Python List Comprehensions, or Python merge two lists.