Lines Matching full:now

48 - The manifest file format now supports a ``description`` field in each
51 - ``west list --format`` now accepts ``{description}`` in the format
54 - ``west compare`` now always prints information about
64 ``check_output()`` now take any kwargs that can be passed on
72 ``wrn()``, and ``err()`` now all take an ``end`` kwarg, which
75 - ``west.manifest.Project`` now has a ``description`` attribute,
94 - Project names which contain comma (``,``) or whitespace now generate
101 - ``west forall`` now takese a ``--group`` argument that can be used
105 - All west commands will now output log messages from west API modules at
116 - ``west.manifest.Manifest.is_active()`` now respects the
124 - Manifest schema version "1.0" is now available for use in this release. This
141 - The :ref:`west-apis` are now declared stable. Any breaking changes will be
148 - Like the rest of Zephyr, west now requires Python v3.8 or later
151 example, you must now specify ``west update --keep-descendants`` instead of
167 This has been fixed and west now prints a sensible error message in this case.
169 - ``west config`` now fails on malformed configuration option arguments
174 - The west package now contains the metadata files necessary for some static
184 - the ``west.log`` module is now deprecated. This module uses global state,
210 in a confusing way. This has been fixed and west now prints a sensible error
219 - West now prints sensible error messages when the user lacks permission to
230 - The ``west.configuration.Configuration`` class now raises ``MalformedConfig``
247 - You can now associate arbitrary user data with the manifest repository
285 - ``west.manifest.Manifest.validate()``: this now returns the validated data as
300 - ``west.manifest.ManifestImportFailed``: the constructor can now take any
306 The following APIs are now deprecated in favor of using a ``Configuration``
321 - West now works on the `MSYS2 <https://www.msys2.org/>`_ platform.
323 - West manifest files can now contain arbitrary user data associated with each
329 the manifest repository; it now prints ``N/A`` ("not applicable")
342 - ``west status`` now only prints output for projects which have a nonempty
349 now rejected.
361 - The ``WEST_CONFIG_LOCAL`` environment variable now correctly
364 - ``west update --fetch=smart`` (``smart`` is the default) now correctly skips
372 ``west init --manifest-rev`` option value, if given, must now be either a
375 request can no longer be passed to ``--manifest-rev``. Users must now fetch
383 - ``west.manifest.Project.sha()`` now works correctly for tag revisions.
395 - ``west update`` now supports ``--narrow``, ``--name-cache``, and
399 - ``west update`` now supports a ``--fetch-opt`` option that will be passed to
405 - ``west update`` now synchronizes Git submodules in projects by default. This
434 <west-manifest-submodules>` is now optional.
438 - West now checks that the manifest schema version is one of the explicitly
446 - A manifest file's ``group-filter`` is now propagated through an ``import``.
468 - Commands like ``west manifest --resolve`` now correctly include group and
473 - West now warns if you combine ``import`` with ``group-filter``. Semantics for
496 - West manifests now support :ref:`west-manifest-submodules`. This allows you
501 - West manifests now support :ref:`west-manifest-groups`. Project groups can be
506 - ``west update`` no longer updates inactive projects by default. It now
515 These commands also now support ``--all`` arguments to include all
518 - ``west list`` now supports a ``{groups}`` format string key in its
530 west used to let it pass silently. West now rejects such manifests.
544 - The :ref:`west-manifest-import` feature now supports the terms ``allowlist``
557 - Manifest import mappings now support a ``path-prefix:`` key, which places
560 - The west command line application can now also be run using ``python3 -m
565 - ``west init`` now supports an ``--mf foo.yml`` option, which initializes the
567 - ``west list`` now prints the manifest repository's path using the
597 - ``west update --stats`` now prints timing for operations which invoke a
615 - West manifests now support a :ref:`schema version
617 - The "west config" command can now be run outside of a workspace, e.g.
622 - The ``west -vv init`` command now prints the git operations being performed,
624 - The restriction that no project can be named "manifest" is now enforced; the
643 - WestCommand.manifest: this is now settable
644 - west.configuration: callers can now identify the workspace directory
651 - The module now uses the standard logging module instead of west.log
663 - Project: the constructor now takes a topdir argument
667 - Project.sha() now captures stderr
670 West now requires Python 3.6 or later. Additionally, some features may rely on
705 project fails, these commands now continue to operate on the rest of the
706 projects. All of them also now report a nonzero error code from the west
711 - The :ref:`west list <west-built-in-misc>` command now works even when the
716 - Commands and options which operate on git revisions now accept abbreviated
717 SHAs. For example, ``west init --mr SHA_PREFIX`` now works. Previously, the
727 - west.commands.WestCommand instances can now access the parsed
731 - west.manifest.Project.git() now has a capture_stderr kwarg
744 at first. It caused confusion, however, and west is now stable enough to be
752 now simply exits after printing an error message.
755 - A west manifest file's ``projects`` elements can now specify their fetch
787 These manifests can now be written with projects that use ``url``
799 - The ``west list`` command now supports a ``{sha}`` format string key
804 - The command ``west manifest --validate`` can now be run to load and validate
812 positional arguments are now kwargs. A new ``url`` kwarg was also added; if
817 now, namely ``manifest``. The *sections* kwargs in the