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
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
|
Developer Setup
===============
The source code is hosted on GitHub. Fork the repository with the following
command::
git clone https://github.com/mu-editor/mu.git
**Mu does not and never will use or support Python 2**. You should use Python
3.5 or above.
Windows, OSX, Linux
+++++++++++++++++++
On all platforms except the Raspberry Pi, to create a working development
environment install all the dependencies into your virtualenv via the
``requirements.txt`` file::
pip install -r requirements.txt
.. warning::
Sometimes, having several different versions of PyQt installed on your
machine can cause problems (see
`this issue <https://github.com/mu-editor/mu/issues/297>`_ for example).
Using a virtualenv will ensure your development environment is safely
isolated from such problematic version conflicts.
If in doubt, throw away your virtualenv and start again with a fresh
install from ``requirements.txt`` as per the instructions above.
On Windows, use the venv module from the standard library to avoid an
issue with the Qt modules missing a DLL::
py -3 -mvenv .venv
Running Development Mu
++++++++++++++++++++++
.. note:: From this point onwards, instructions assume that you're using
a virtual environment.
For the debug runner to work, the ``mu-debug`` command must be available (it's
used to launch user's Python script with the debugging scaffolding in place to
communicate with Mu, acting as the debug client). As a result, it's essential
to run the following to ensure this command is available in your virtualenv::
pip install --editable .
To run the local development version of Mu, in the root of
the repository type::
python run.py
An alternative form is to type::
python -m mu
Raspberry Pi
++++++++++++
If you are working on a Raspberry Pi there are additional steps to create a
working development environment:
1. Install required dependencies from Raspbian repository::
sudo apt-get install python3-pyqt5 python3-pyqt5.qsci python3-pyqt5.qtserialport python3-pyqt5.qtsvg python3-dev python3-gpiozero python3-pgzero libxmlsec1-dev libxml2 libxml2-dev
2. Create a virtualenv that uses Python 3 and allows the virtualenv access
to the packages installed on your system via the ``--system-site-packages``
flag::
sudo pip3 install virtualenv
virtualenv -p /usr/bin/python3 --system-site-packages ~/mu-venv
3. Activate the virtual environment ::
source ~/mu-venv/bin/activate
4. Clone mu::
(mu-venv) $ git clone https://github.com/mu-editor/mu.git ~/mu-source
5. With the virtualenv enabled, pip install the Python packages for the
Raspberry Pi via the ``requirements_pi.txt`` file::
(mu-venv) $ cd ~/mu-source
(mu-venv) $ pip install -r requirements_pi.txt
7. Use ``pip`` to install mu without installing the dependencies again::
(mu-venv) $ pip install --editable .
8. Run mu::
python run.py
An alternative form is to type::
python -m mu
.. warning::
These instructions for Raspberry Pi only work with Raspbian version
"Stretch".
Using ``make``
++++++++++++++
There is a Makefile that helps with most of the common workflows associated
with development. Typing ``make`` on its own will list the options thus::
$ make
There is no default Makefile target right now. Try:
make run - run the local development version of Mu.
make clean - reset the project and remove auto-generated assets.
make pyflakes - run the PyFlakes code checker.
make pycodestyle - run the PEP8 style checker.
make test - run the test suite.
make coverage - view a report on test coverage.
make check - run all the checkers and tests.
make dist - make a dist/wheel for the project.
make publish-test - publish the project to PyPI test instance.
make publish-live - publish the project to PyPI production.
make docs - run sphinx to create project documentation.
make translate - create a messages.pot file for translations.
make translateall - as with translate but for all API strings.
Everything should be working if you can successfully run::
make check
(You'll see the results from various code quality tools, the test suite and
code coverage.)
.. note::
On Windows there is a ``make.cmd`` file that works in a similar way to the
``make`` command on Unix-like operating systems.
.. warning::
In order to use the MicroPython REPL via USB serial you may need to add
yourself to the ``dialout`` group on Linux, or, if you're on some versions
of Windows, install the `Windows serial driver <https://os.mbed.com/handbook/Windows-serial-configuration>`_.
Before Submitting
+++++++++++++++++
Before contributing code please make sure you've read :doc:`contributing` and
follow the checklist for contributing changes. We expect everyone participating
in the development of Mu to act in accordance with the PSF's
:doc:`code_of_conduct`.
|
