Skip to content

Commit b307b27

Browse files
committed
updated cheat sheet, Makefile
1 parent 1a5220d commit b307b27

File tree

2 files changed

+13
-53
lines changed

2 files changed

+13
-53
lines changed

CHEATSHEET.rst

+10-50
Original file line numberDiff line numberDiff line change
@@ -1,62 +1,25 @@
1-
Finishing setting up your project
2-
=================================
3-
4-
Thanks for using cookiecutter-trio! This is your project now; you can
5-
customize it however you like. Here's some reminders of things you
6-
might want to do to get started:
7-
8-
* Check this into source control (``git init .; git add .; git
9-
commit -m "Initial commit"``)
10-
11-
* Add a CODE_OF_CONDUCT.md
12-
13-
* Add a CONTRIBUTING.md
14-
15-
* Search the source tree for COOKIECUTTER-TRIO-TODO to find other
16-
places to fill in.
17-
* Enable `Read the Docs <https://readthedocs.org>`__. (Note: this
18-
project contains a ``.readthedocs.yml`` file that should be enough
19-
to get things working.)
20-
21-
* Set up continuous integration: Currently, this project is set up to
22-
test on Linux and MacOS using Travis, on Windows using Appveyor, and
23-
to test on PyPy.
24-
25-
If that's what you want, then go to Travis and Appveyor and enable
26-
testing for your repo.
27-
28-
If that's not what you want, then you can trim the list by modifying
29-
(or deleting) ``.travis.yml``, ``.appveyor.yml``, ``ci/travis.sh``.
30-
31-
* Enable `Codecov <https://codecov.io>`__ for your repo.
32-
33-
* File bugs or pull requests on `cookiecutter-trio
34-
<https://github.com/python-trio/cookiecutter-trio>`__ reporting any
35-
problems or awkwardness you ran into (no matter how small!)
36-
37-
* Delete this checklist once it's no longer useful
38-
39-
401
Tips
412
====
423

434
To run tests
445
------------
456

46-
* Install requirements: ``pip install -r test-requirements.txt``
7+
* Install requirements: ``pip install -r ci/test-requirements.txt``
478
(possibly in a virtualenv)
489

49-
* Actually run the tests: ``pytest trio_asyncio``
10+
* Actually run the tests: ``PYTHONPATH=. pytest-3 tests``
5011

5112

5213
To run yapf
5314
-----------
5415

55-
* Show what changes yapf wants to make: ``yapf -rpd setup.py
56-
trio_asyncio``
16+
* Show what changes yapf wants to make:
17+
``yapf3 -rpd setup.py trio_asyncio tests``
5718

58-
* Apply all changes directly to the source tree: ``yapf -rpi setup.py
59-
trio_asyncio``
19+
* Apply all changes directly to the source tree:
20+
``yapf -rpi setup.py trio_asyncio tests``
21+
22+
* Find semantic problems: ``flake8 setup.py trio_asyncio tests``
6023

6124

6225
To make a release
@@ -72,10 +35,7 @@ To make a release
7235

7336
* Double-check it all works, docs build, etc.
7437

75-
* Build your sdist and wheel: ``python setup.py sdist bdist_wheel``
76-
77-
* Upload to PyPI: ``twine upload dist/*``
78-
79-
* Use ``git tag`` to tag your version.
38+
* Upload to PyPI: ``make upload``
8039

8140
* Don't forget to ``git push --tags``.
41+

Makefile

+3-3
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ SPHINXBUILDDIR ?= $(BUILD_DIR)/sphinx/html
3333
ALLSPHINXOPTS ?= -d $(BUILD_DIR)/sphinx/doctrees $(SPHINXOPTS) docs
3434

3535
doc:
36-
sphinx-build -a $(INPUT_DIR) build
36+
sphinx3-build -a $(INPUT_DIR) $(BUILD_DIR)
3737

3838
livehtml: docs
3939
sphinx-autobuild $(AUTOSPHINXOPTS) $(ALLSPHINXOPTS) $(SPHINXBUILDDIR)
@@ -52,8 +52,8 @@ pypi: tag
5252
## version depends on tag, so re-tagging doesn't make sense
5353

5454
upload: pypi
55-
git push --tags
55+
git push-all --tags
5656

5757
update:
58-
pip install -r requirements_dev.txt
58+
pip install -r ci/test-requirements.txt
5959

0 commit comments

Comments
 (0)