|
83 | 83 | #. Close your ``cmd.exe`` window and open a new one. You should be able to run
|
84 | 84 | ``west``.
|
85 | 85 |
|
86 |
| -"Error: unexpected keyword argument 'requires_workspace'" |
87 |
| -********************************************************* |
88 |
| - |
89 |
| -This error occurs on some Linux distributions after upgrading to west 0.7.0 or |
90 |
| -later from 0.6.x. For example: |
91 |
| - |
92 |
| -.. code-block:: none |
93 |
| -
|
94 |
| - $ west update |
95 |
| - [... stack trace ...] |
96 |
| - TypeError: __init__() got an unexpected keyword argument 'requires_workspace' |
97 |
| -
|
98 |
| -This appears to be a problem with the distribution's pip; see `this comment in |
99 |
| -west issue 373`_ for details. Some versions of **Ubuntu** and **Linux Mint** are known to |
100 |
| -have this problem. Some users report issues on Fedora as well. |
101 |
| - |
102 |
| -Neither macOS nor Windows users have reported this issue. There have been no |
103 |
| -reports of this issue on other Linux distributions, like Arch Linux, either. |
104 |
| - |
105 |
| -.. _this comment in west issue 373: |
106 |
| - https://github.com/zephyrproject-rtos/west/issues/373#issuecomment-583489272 |
107 |
| - |
108 |
| -**Workaround 1**: remove the old version, then upgrade: |
109 |
| - |
110 |
| -.. code-block:: none |
111 |
| -
|
112 |
| - $ pip3 show west | grep Location: | cut -f 2 -d ' ' |
113 |
| - /home/foo/.local/lib/python3.6/site-packages |
114 |
| - $ rm -r /home/foo/.local/lib/python3.6/site-packages/west |
115 |
| - $ pip3 install --user west==0.7.0 |
116 |
| -
|
117 |
| -**Workaround 2**: install west in a Python virtual environment |
118 |
| - |
119 |
| -One option is to use the `venv module`_ that's part of the Python 3 standard |
120 |
| -library. Some distributions remove this module from their base Python 3 |
121 |
| -packages, so you may need to do some additional work to get it installed on |
122 |
| -your system. |
123 |
| - |
124 |
| -.. _venv module: |
125 |
| - https://docs.python.org/3/library/venv.html |
126 |
| - |
127 | 86 | "invalid choice: 'build'" (or 'flash', etc.)
|
128 | 87 | ********************************************
|
129 | 88 |
|
@@ -203,21 +162,3 @@ The easiest way to resolve this issue is to upgrade west and retry as follows:
|
203 | 162 | you will get the "already in a workspace" error message discussed next).
|
204 | 163 |
|
205 | 164 | #. Run ``west init`` again.
|
206 |
| - |
207 |
| -"already in an installation" |
208 |
| -**************************** |
209 |
| - |
210 |
| -You may see this error when running ``west init`` with west 0.6: |
211 |
| - |
212 |
| -.. code-block:: none |
213 |
| -
|
214 |
| - FATAL ERROR: already in an installation (<some directory>), aborting |
215 |
| -
|
216 |
| -If this is unexpected and you're really trying to create a new west workspace, |
217 |
| -then it's likely that west is using the :envvar:`ZEPHYR_BASE` :ref:`environment |
218 |
| -variable <env_vars>` to locate a workspace elsewhere on your system. |
219 |
| - |
220 |
| -This is intentional; it allows you to put your Zephyr applications in |
221 |
| -any directory and still use west to build, flash, and debug them, for example. |
222 |
| - |
223 |
| -To resolve this issue, unset :envvar:`ZEPHYR_BASE` and try again. |
0 commit comments