edf998161c
Changelog:
=========
- added tag.setter on 'ScalarEvent' and on 'Node', that takes either
a 'Tag' instance, or a str
- fix issue 467, caused by Tag instances not being hashable
- changed the internals of the tag property from a string to a class which allows
for preservation of the original handle and suffix. This should
result in better results using documents with %TAG directives, as well
as preserving URI escapes in tag suffixes.
- fix for issue 464: documents ending with document end marker without final newline
fail to load
- fix issue with inline mappings as value for merge keys
- fix for 468, error inserting after accessing merge attribute on "CommentedMap"
- fix for issue 461 pop + insert on same 'CommentedMap' key throwing error
- Fix for error on edge cage for issue 459
- fix for regression while dumping wrapped strings with too many backslashes removed
- rewrite of "CommentedMap.insert()". If you have a merge key in
the YAML document for the mapping you insert to, the position value should
be the one as you look at the YAML input.
This fixes issue 453 where other
keys of a merged in mapping would show up after an insert
It
also fixes a call to '.insert()' resulting into the merge key to move
to be the first key if it wasn't already and it is also now possible
to insert a key before a merge key (even if the fist key in the mapping).
- fix (in the pure Python implementation including default) for issue 447.
also brought up by brent on
'StackOverflow <https://stackoverflow.com/q/40072485/1307905>'__)
- fix 458, error on plain scalars starting with word longer than width.
- fix for ".update()" no longer correctly handling keyword arguments
- fix issue 454: high Unicode (emojis) in quoted strings always
escaped
- fix issue with emitter conservatively inserting extra backslashes in wrapped
quoted strings
- fix issue 449 where the second exclamation marks got URL encoded
and fixing PR
- fix issue with indent != 2 and literal scalars with empty first line
- updated __repr__ of CommentedMap, now that Python's dict is ordered -> no more
ordereddict(list-of-tuples)
- merge MR 4, handling OctalInt in YAML 1.1
- fix loading of '!!float 42'
- line numbers are now set on 'CommentedKeySeq' and 'CommentedKeyMap' (which
are created if you have a sequence resp. mapping as the key in a mapping)
- plain scalars: put single words longer than width on a line of their own, instead
of after the previous line
- fix for folded scalar part of 421: comments after ">" on first line of folded
scalars are now preserved (as were those in the same position on literal scalars).
- added stacklevel to warnings
- typing changed from Py2 compatible comments to Py3, removed various Py2-isms
License-Update: Copyright year updated to 2023
(From OE-Core rev: a83a1f21c1c1637017d4046b32fc5e558f342add)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.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
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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.