Skip to content

Commit b004dd5

Browse files
committed
Merge branch 'master' of https://github.com/mmasdeu/sage_sample
2 parents ac45680 + 25628bc commit b004dd5

File tree

2 files changed

+20
-16
lines changed

2 files changed

+20
-16
lines changed

.travis-deploy-doc.sh

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ if [[ "${TRAVIS_PULL_REQUEST}" == "false" && "${TRAVIS_BRANCH}" == "${DEPLOY_DOC
1010
fi
1111
chmod 600 .travis_ci_gh_pages_deploy_key
1212
eval `ssh-agent -s`
13-
ssh-add .travis_ci_gh_pages_deploy_key
13+
ssh-add .travis_ci_gh_pages_deploy_key < /dev/null
1414
rm -Rf gh-pages
1515
git clone --depth 1 git@github.com:${DEPLOY_DOC_TO_REPOSITORY}.git --depth 1 --branch=gh-pages gh-pages
1616
BUILT_DOCS_DIR=`cd docs/build/html && pwd`

README.rst

Lines changed: 19 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,16 @@
22
Sage Sample Package
33
===================
44

5-
This package is designed as as simple `SageMath <http://www.sagemath.org>`_ package
5+
This package is designed as a simple `SageMath <http://www.sagemath.org>`_ package
66
example to serve as a good practice reference for package developers. We follow
77
python recommendations and adapt them to the SageMath community. You can find more
88
advanced documentation on python package creation on
99
`How To Package Your Python Code <https://packaging.python.org/>`_.
1010

11+
This is still a work in progress. Once this example will have
12+
stabilized, the plan is to make a
13+
`cookie cutter <https://cookiecutter.readthedocs.io/en/latest/>`_
14+
template out of it.
1115

1216
Installation
1317
------------
@@ -17,15 +21,15 @@ Local install from source
1721

1822
Download the source from the git repository::
1923

20-
$ git clone https://github.com/nthiery/sage_sample.git
24+
$ git clone https://github.com/sagemath/sage_sample.git
2125

2226
Change to the root directory and run::
2327

2428
$ sage -pip install --upgrade --no-index -v .
2529

2630
For convenience this package contains a [makefile](makefile) with this
2731
and other often used commands. Should you wish too, you can use the
28-
shorthand:
32+
shorthand::
2933

3034
$ make install
3135

@@ -85,7 +89,7 @@ configured in ``setup.py`` to run the tests::
8589

8690
This is just calling ``sage -t`` with appropriate flags.
8791

88-
Shorthand:
92+
Shorthand::
8993

9094
$ make test
9195

@@ -98,19 +102,19 @@ The documentation of the package can be generated using Sage's
98102
$ cd docs
99103
$ sage -sh -c "make html"
100104

101-
Shorthand:
105+
Shorthand::
102106

103107
$ make doc
104108

105109
For this to work on your own package, make sure you follow the same
106110
structure as we do here:
107111

108-
* Create a ``docs`` folder containing the exact same ``Makefile`` and a ``source``
109-
folder.
110-
* Copy and paste the ``docs/source/conf.py`` file from this package and update
111-
the few project specific variables at the beginning of the file.
112-
* Create an ``index.rst`` file as well as a ``<module name>.rst`` file for each
113-
module you want on the documentation.
112+
* Create a ``docs`` folder containing the exact same ``Makefile`` and a ``source``
113+
folder.
114+
* Copy and paste the ``docs/source/conf.py`` file from this package and update
115+
the few project specific variables at the beginning of the file.
116+
* Create an ``index.rst`` file as well as a ``<module name>.rst`` file for each
117+
module you want on the documentation.
114118

115119
Travis CI integration
116120
---------------------
@@ -133,12 +137,12 @@ Automatically deploying documentation to GitHub pages using Travis CI
133137

134138
* First do the steps described above to enable Travis CI integration
135139
of your GitHub-hosted project.
136-
140+
137141
* If you don't already have GitHub pages for your project: Create and
138142
checkout a branch ``gh-pages`` in your repository and put an empty
139-
file ``.nojekyll`` in it. (See
140-
https://help.github.com/articles/files-that-start-with-an-underscore-are-missing/)::
141-
Commit it and push it to GitHub::
143+
file ``.nojekyll`` in it (see
144+
https://help.github.com/articles/files-that-start-with-an-underscore-are-missing/).
145+
Then commit it and push it to GitHub::
142146

143147
$ git clone --single-branch --depth 1 https://github.com/USER/PROJECT.git gh-pages
144148
$ cd gh-pages

0 commit comments

Comments
 (0)