@@ -30,12 +30,16 @@ itself. git is easily available for all common operating systems. As the
3030CPython repo is hosted on GitHub, please refer to either the
3131`GitHub setup instructions <https://help.github.com/articles/set-up-git/ >`_
3232or the `git project instructions <https://git-scm.com >`_ for step-by-step
33- installation directions.
33+ installation directions. You may also want to consider a graphical client
34+ such as `TortoiseGit <http://tortoisegit.org/ >`_ or
35+ `GitHub Desktop <https://desktop.github.com/ >`_.
36+
37+ You may also wish to
38+ `set up an SSH key <https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/ >`_
39+ as this will allow you to interact with GitHub without typing a username
40+ and password each time you execute a command, such as ``git pull ``,
41+ ``git push ``, or ``git fetch ``.
3442
35- You may also wish to set up an SSH key as
36- described in the GitHub instructions as this will allow you to interact with
37- GitHub without typing a username and password each time you execute a
38- command, such as `git pull `, `git push `, or `git fetch `.
3943
4044.. _checkout :
4145
@@ -80,17 +84,15 @@ Compiling (for debugging)
8084
8185CPython provides several compilation flags which help with debugging various
8286things. While all of the known flags can be found in the
83- ``Misc/SpecialBuilds.txt ``
84- file, the most critical one is the ``Py_DEBUG `` flag which creates what is
85- known as a "pydebug" build. This flag turns on
86- various extra sanity checks which help catch common issues. The use of the flag
87- is so common that turning on the flag is a basic compile option.
87+ ``Misc/SpecialBuilds.txt `` file, the most critical one is the ``Py_DEBUG `` flag
88+ which creates what is known as a "pydebug" build. This flag turns on various
89+ extra sanity checks which help catch common issues. The use of the flag is so
90+ common that turning on the flag is a basic compile option.
8891
89- You should always
90- develop under a pydebug build of CPython (the only instance of when you
91- shouldn't is if you are taking performance measurements). Even when working
92- only on pure Python code the pydebug build provides several useful checks that
93- one should not skip.
92+ You should always develop under a pydebug build of CPython (the only instance of
93+ when you shouldn't is if you are taking performance measurements). Even when
94+ working only on pure Python code the pydebug build provides several useful
95+ checks that one should not skip.
9496
9597
9698.. _build-dependencies :
@@ -271,7 +273,7 @@ still build properly).
271273Windows
272274'''''''
273275
274- The `readme <https://hg. python.org /cpython/file/default /PCbuild/readme.txt >`_
276+ The `readme <https://github.com/ python/cpython/blob/master /PCbuild/readme.txt >`_
275277included in the solution has more details, especially on what additional
276278software is required to build which parts of Python.
277279
@@ -351,15 +353,8 @@ when trying to build an old (2.x) Python with a new (3.x) Python installed, or
351353vice versa.
352354
353355To overcome this problem, auto-generated files are also checked into the
354- git repository. So if you don't touch the auto-generation scripts, there's
355- no real need to auto-generate anything. A special build target ``touch `` was added (the ``touch ``
356- build target is not designed for git clones and does not support them). Run::
357-
358- make touch
359-
360- Before running the compilation ``make ``. This will tweak the timestamps of the
361- auto-generated files in a way that makes it unnecessary to create them anew and
362- henceforth the compilation should not require an installed Python interpreter.
356+ Git repository. So if you don't touch the auto-generation scripts, there's
357+ no real need to auto-generate anything.
363358
364359Editors and Tools
365360=================
0 commit comments