1790dcba63
* Drop 0001-test_funcs-skip-test_unknown-for-pytest-8.patch fixed upstream in https://github.com/python-attrs/attrs/pull/1249 * Drop 0001-conftest.py-disable-deadline.patch upstream wanted to try doubling the deadline time https://github.com/python-attrs/attrs/pull/1252 from 200 ms default to 400 ms (we saw some times a bit greater than 200 ms) https://www.attrs.org/en/stable/changelog.html 24.2.0 - 2024-08-06 * Deprecations - Given the amount of warnings raised in the broader ecosystem, we’ve decided to only soft-deprecate the hash argument to @define / @attr.s. Please don’t use it in new code, but we don’t intend to remove it anymore. #1330 * Changes - attrs.converters.pipe() (and its syntactic sugar of passing a list for attrs.field()’s / attr.ib()’s converter argument) works again when passing attrs.setters.convert to on_setattr (which is default for attrs.define). #1328 - Restored support for PEP 649 / 749-implementing Pythons – currently 3.14-dev. #1329 24.1.0 - 2024-08-03 * Backwards-incompatible Changes - attrs.evolve() doesn’t accept the inst argument as a keyword argument anymore. Pass it as the first positional argument instead. #1264 - attrs.validators.provides() has been removed. The removed code is available as a gist for convenient copy and pasting. #1265 - All packaging metadata except from __version__ and __version_info__ has been removed from the attr and attrs modules (for example, attrs.__url__). - Please use importlib.metadata or importlib-metadata instead. #1268 - The generated __eq__ methods have been sped up significantly by generating a chain of attribute comparisons instead of constructing and comparing tuples. This change arguably makes the behavior more correct, but changes it if an attribute compares equal by identity but not value, like float('nan'). #1310 * Deprecations - The repr_ns argument to attr.s is now deprecated. It was a workaround for nested classes in Python 2 and is pointless in Python 3. #1263 - The hash argument to @attr.s, @attrs.define, and make_class() is now deprecated in favor of unsafe_hash, as defined by PEP 681. #1323 * Changes - Allow original slotted functools.cached_property classes to be cleaned by garbage collection. Allow super() calls in slotted cached properties. #1221 - Our type stubs now use modern type notation and are organized such that VS Code’s quick-fix prefers the attrs namespace. #1234 - Preserve AttributeError raised by properties of slotted classes with functools.cached_properties. #1253 - It is now possible to wrap a converter into an attrs.Converter and get the current instance and/or the current field definition passed into the converter callable. - Note that this is not supported by any type checker, yet. #1267 - attrs.make_class() now populates the __annotations__ dict of the generated class, so that attrs.resolve_types() can resolve them. #1285 - Added the attrs.validators.or_() validator. #1303 - The combination of a __attrs_pre_init__ that takes arguments, a kw-only field, and a default on that field does not crash anymore. #1319 - attrs.validators.in_() now transforms certain unhashable options to tuples to keep the field hashable. - This allows fields that use this validator to be used with, for example, attrs.filters.include(). #1320 - If a class has an inherited method called __attrs_init_subclass__, it is now called once the class is done assembling. - This is a replacement for Python’s __init_subclass__ and useful for registering classes, and similar. #1321 (From OE-Core rev: b8c45e8accdb7d74646fa15b775034eb3dcbdcd1) Signed-off-by: Tim Orling <tim.orling@konsulko.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.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.