Now that we use a single release pipeline, the API itself might not yet be on
PyPI by the time we build jedi, so we build it locally.
We'll still keep the API docs on PyPI so users can have local autocomplete,
but that path is no longer a dependency for building jedi.
Also explain CHANGELOG synchronization with firmware repo.
Releasing API updates is quite a long and error prone process, so the point
that it was limiting our ability to push frequent updates in practice. There
were 5 tag, commit, wait, and proceed steps and you'd have to start over or
force push if a mistake was made.
This keeps all the npm packages as they were, but versions everything from a
single source of truth, which is this project's main version. Everything
builds on a tag on the main repo, much like we did for a regular IDE docs RTD
release.
It also skips the PyPI for jedi as an intermediate step, which isn't really
needed and required us to have this strict order of publication steps.
Some were omitted once EV3 in Pybricks 2.0 was dropped, but they will be included again to prepare for EV3 in Pybricks 4.0.
Enable for Powered UP where relevant, as with UARTDevice.
- Add overloads for broadcast(). It accepts either a single value, or a tuple,
or a list.
- Adjust return type of observe(). It either returns a single value, or a tuple.
* Added missing functions and parameters to documentation.
- AnalogSensor: Missing parameter "custom".
- I2CDevice: Missing parameters "port", "address", "custom", "powered", and "nxt_quirk" with attempted explanation of parameters.
- UARTDevice: Missing default parameter value.
- LWP3Device: Missing "connect" parameter.
- Added missing connect and disconnnect methods.
- XboxController: Missing documentation in constructor and missing methods.
* Minor changes to the documentation
Made it more clear and less verbose when to skip connect to bluetooth devices.
* Implement `Color.__eq__`, fix `Color.__mul__`. This allows testing of color block sorting algorithms with CPython.
* implement `Color.__lshift__` and immutability for completeness.
The sources are hosted on GitHub, so there is not additional information here. Also, the actual docstrings are included in the .py files.
See https://github.com/pybricks/support/issues/1559
Laurens Valk
Frederik LeonhardtandLaurens Valk
Lasse Deleuran
kai-morichandGitHub
JoBeandGitHub
Gabriel CouchenourandGitHub