af09a399db
Changelog (https://hypothesis.readthedocs.io/en/latest/changes.html): 6.115.3 - 2024-10-16 - This patch fixes a regression from version 6.115.2 where generating values from integers() with certain values for min_value and max_value would error. 6.115.2 - 2024-10-14 - This release improves integer shrinking by folding the endpoint upweighting for integers() into the weights parameter of our IR (issue #3921). If you maintain an alternative backend as part of our (for now explicitly unstable) Alternative backends for Hypothesis, this release changes the type of the weights parameter to draw_integer and may be a breaking change for you. 6.115.1 - 2024-10-14 - This patch improves the performance of from_type() with pydantic.types.condate (issue #4000). 6.115.0 - 2024-10-12 - This improves the formatting of dataclasses and attrs classes when printing falsifying examples. 6.114.1 - 2024-10-10 - This patch upgrades remaining type annotations to Python 3.9 syntax. 6.114.0 - 2024-10-09 - This release drops support for Python 3.8, which reached end of life on 2024-10-07. 6.113.0 - 2024-10-09 - This release adds hypothesis.errors.BackendCannotProceed, an unstable API for use by Alternative backends for Hypothesis. 6.112.5 - 2024-10-08 - This release fixes a regression where hypothesis.stateful.Bundle did not work properly with flatmap functionality (issue #4128). (From OE-Core rev: 0ab451304025f7fdad06345c73233daa47e4f8b9) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.