1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
|
# Development
Notes on how to develop guizero (on Windows).
## Setup
Upgrade pip:
```
python -m pip install pip --upgrade
```
Install / upgrade pre-requisites:
```
pip install mkdocs mkdocs-bootswatch wheel twine virtualenv pytest pillow setuptools --upgrade
```
## Python library
Uninstall previous versions of guizero:
```
pip uninstall guizero
```
Create a virtual environment (not essential, but a good idea!):
```
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
```
Activate your virtual environment:
```
source bin/activate
```
Checkout and install guizero for development:
```
git clone https://github.com/lawsie/guizero
cd guizero
git checkout dev
pip install -e .
```
When you have finished your development, deactivate your virtual environment:
```
source bin/deactivate
```
## Tests
If running the tests inside a virtual environment you will need to install pytest in that virtual environment.
```
pip install pytest
```
To run all the automated tests:
```
cd guizero\tests
pytest -v
```
To run a specific test:
```
cd guizero\tests
pytest -v [test_filename.py]
```
_Note - tkinter can error when running the tests usually when the interpreter doesn't start properly, it doesn't seem to like being initialised and destroyed hundreds of times, I suspect a file locking issue as you don't see the problem on Linux. So sometimes you might get a test fail with an error like `This probably means that tk wasn't installed properly.`. Just re-run the last failed errors! `pytest --lf -v`_
## Documents
Test documents by serving up MkDocs:
```
cd guizero\docs-src
mkdocs serve
```
Open [http://127.0.0.1:8000/](http://127.0.0.1:8000/)
|
