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
* tox.ini is outdated and likely not used
* No need for extra pip-install
Dependencies are already installed by the setup script in the venv, and the pip install would install into the user env if not already in the venv.
* Removed traces of isort, black and flake8 since using ruff instead
* Moved requirements into dev dependency-group
* Added pre-commit hook to check that uv.lock is up to date
* Updated README with dependency mangement using uv
* Created dependency-group `ci`
* Fixed wording in README
* Updated dependency management in README
Copy file name to clipboardExpand all lines: README.md
+49-10Lines changed: 49 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -404,7 +404,7 @@ Now lets put this all together. If you examine the device definition above you w
404
404
405
405
# Contribution Guidelines
406
406
407
-
- All code is formatted withblack. The check format script that runs inCI will ensure that code meets this requirement and that it is correctly formatted withblack. Instructions forinstalling blackin many editors can be found here: <https://github.com/psf/black#editor-integration>
407
+
- All code is formatted withruff. The check format script that runs inCI will ensure that code meets this requirement and that it is correctly formatted withruff. Instructions forintegrating ruffin many editors can be found here: <https://docs.astral.sh/ruff/editors/>
408
408
409
409
- Capture the SimpleDescriptor log entries for each endpoint on the device. These can be found in the HA logs after joining a device and they look like this: `<SimpleDescriptor endpoint=1 profile=260 device_type=1026 device_version=0 input_clusters=[0, 1, 3, 32, 1026, 1280, 2821] output_clusters=[25]>`. This information can also be obtained from the zigbee.db if you want to take the time to query the tables and reconstitute the log entry. I find it easier to just remove and rejoin the device. ZHA entity ids are stable for the most part so it _shouldn't_ disrupt anything you have configured. These need to match what the device reports EXACTLY or zigpy will not match them when a device joins and the handler will not be used for the device. You can also obtain this information from the device screen in HA for the device. The `Zigbee Device Signature` button will launch a dialog that contains all of the information necessary to create quirks.
410
410
@@ -449,15 +449,9 @@ You can see a pattern that illustrates how to match a more complex event. In thi
449
449
450
450
Open a terminal at the root of the project and run the setup script: `script/setup` This script will install all necessary dependencies and it will install the precommit hook.
451
451
452
-
The tests use the [pytest](https://docs.pytest.org/en/latest/) framework.
453
-
454
-
### Getting started
455
-
456
-
To get set up, you need install the test dependencies:
457
-
458
-
```bash
459
-
pip install -r requirements_test.txt
460
-
```
452
+
All the dependencies are installed using the locked versions in the `uv.lock`file.
453
+
To keep the environment up to date with the locked versions of the dependencies, run `uv sync` make sure the
0 commit comments