Skip to content

Commit f4a997d

Browse files
committed
Make the shell be in code blocks and add a section about building the documentation.
1 parent 8743067 commit f4a997d

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed

doc/sphinx/source/contributing.rst

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,17 +18,23 @@ Getting your development environment set up
1818

1919
Using a virtual environment is probably a good idea. Create a virtual environment with
2020

21+
.. code-block:: bash
22+
2123
$ virtualenv bpython-dev
2224
$ source bpython-dev/bin/activate # this step is necssary every time you work on bpython
2325
<hack on bpython>
2426
$ deactivate # back to normal system environment
2527
2628
Fork bpython in the GitHub web interace, then clone the repo:
2729

30+
.. code-block:: bash
31+
2832
$ git clone git@github.com:YOUR_GITHUB_USERNAME/bpython.git
2933
3034
Next install this development version of bpython:
3135

36+
.. code-block:: bash
37+
3238
$ pip install pygments curtsies greenlet watchdog urwid # install all the dependencies
3339
$ pip install sphinx mock # development dependencies
3440
$ cd bpython
@@ -45,7 +51,20 @@ To run tests:
4551
To build the docs:
4652
------------------
4753

48-
TODO
54+
The documentation is included in the regular `bpython` repository so if you did the
55+
previous step your install can support generating and working on the documentation.
56+
57+
Install `sphinx` (or in your current `virtualenv`). And go to the following directory:
58+
59+
.. code-block:: bash
60+
61+
$ pip install sphinx
62+
$ cd bpython/doc/sphinx/ # assuming you are in the root dir of the bpython project
63+
$ make html
64+
65+
Afterwards you can point your browser to `bpython/doc/source/index.html`. Don't forget
66+
to recreate the HTML after you make changes.
67+
4968

5069
To hack on the site:
5170
--------------------

0 commit comments

Comments
 (0)