You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+8-13
Original file line number
Diff line number
Diff line change
@@ -9,17 +9,17 @@ http://tinypythonprojects.com/
9
9
There is a directory for each chapter of the book.
10
10
Each directory contains a `test.py` program you can use with `pytest` to check that you have written the program correctly.
11
11
I have included a short README to describe each exercise.
12
-
If you have problems writing code (or if you would like to support this project!), the book contains details about the skills you need.
12
+
If you have problems writing code, see my book for the skills you need.
13
13
14
-
The testing step is integral to writing and solving these challenges as well as to the methodology of the book.
15
-
I advocate a "test-driven development" mentality where we write tests _before_we write code.
16
-
The tests should define what it means for a program to be correct, and then we write programs to satisfy the tests.
14
+
Testing is integral to writing and solving these challenges as well as to the methodology of the book.
15
+
I advocate for "test-driven development" where you write tests _before_you write code.
16
+
The tests should define what it means for a program to be correct, and then you write programs to satisfy the tests.
17
17
In this project, I've written all the tests for you, but I also encourage you to write your own functions and tests.
18
18
You should run the test suite after every change to your program to ensure you are making progress!
19
19
20
20
# Videos
21
21
22
-
I've been making videos for each chapter on my YouTube channel:
22
+
I made videos for each chapter on my YouTube channel:
23
23
24
24
https://www.youtube.com/user/kyclark
25
25
@@ -61,14 +61,9 @@ Here are the videos I've completed so far:
61
61
62
62
# Forking GitHub repo
63
63
64
-
First use the GitHub interface to "fork" this repository into your own account. Then do `git clone` of *your* repository to get a local copy. Inside that checkout, do:
This will allow you to `git pull upstream master` in order to get updates. When you create new files, `git add/commit/push` them to *your* repository. (Please do not create pull requests on *my* repository -- unless, of course, you have suggestions for improving my repo!).
64
+
If you like, you can use the GitHub interface to _fork_ this repository into your own account.
65
+
Then do `git clone` of *your* repository to get a local copy.
0 commit comments