In http://docs.python.org/py3k/using/mac.html#getting-and-installing-macpython and http://docs.python.org/py3k/using/mac.html#distributing-python-applications-on-the-mac .

Thanks for the report.  The whole "Using Python on a Macintosh" section is very out-of-date and needs a major update.

Built with sphinx. No RST errors.

Thank you for the patch, Yuly!  You've made some good improvements to the current page.  Because the current section is so old and out-of-sync with current practices (as you've noted in your changes) and with the nuances of Python on OS X, a more comprehensive restructuring is needed.  I don't think that trying to refine the section interactively is going to be an efficient process but I will definitely use your suggested changes as a basis.  I assume you have signed (or will be signing) the PSF contributor agreement.  Thanks again!  P.S. When submitting patches, don't forget to run patchcheck first (https://docs.python.org/devguide/patch.html#generation).  It will detect and fix trailing whitespace in lines that would otherwise prevent a patch from being committed in the main cpython hg repo.

Ok, I will definitely use that checker next time :) thanks!
Thanks Ned!

I'd like to help out with this issue if I can. This page in the documentation is really showing it's age now.

* I think referring to "OS X" (soon to be "MacOS") instead of "Mac" or "Macintosh" would more accurate.
* The opening paragraph of section 4.1 only refers to OS X 10.8, which was released over 4 years ago.
* Is there any value in listing text editors in section 4.1.1? Editors frequently come-and-go.
* I suspect a large number of Python 3 developers running OS X use http://brew.sh/ - would it be worth mentioning this somewhere?

According to the official tutorial on virtual environment,

"""
This will create the tutorial-env directory if it doesn’t exist, and also create directories inside it containing a copy of the Python interpreter, **the standard library**, and various supporting files.
"""

But according to PEP 405 and the actual behavior of venv, the standard library won't be copied. I'm not sure if I'm having a misunderstanding of this expression.

sorry for posting a wrong message in this issue tracker, this is my first time using the Python issue tracker