Synchronise master with upstream #135
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Taskflow 6.0.0 had a bug in the database migrations that caused duplicate table name errors during the persistence database tables alembic migration. 6.0.1 was released with a fix[1] for this issue. This patch excludes 6.0.0 in the global requirements to avoid the problem. [1] https://review.opendev.org/c/openstack/taskflow/+/950967 Change-Id: Idd7c61489d4a4fd653ecd66789eeed20a998fe07
The library was added for osprofiler[1]. However its development was abandoned in 2022[1], and we retired the driver [3]. [1] 37521f4 [2] https://github.com/jaegertracing/jaeger-client-python [3] https://review.opendev.org/952373 Change-Id: I28c9ecb10e631c5c639586bd4160590c4aac20bb Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
It was used by barbican but the dependency has been removed by [1]. [1] https://review.opendev.org/937752 Change-Id: I702394b5f925d6a3e1833109a82f9827cdc3088c Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
The library is no longer used by any projects. Change-Id: Ie550cca55e7c5d180701b2b8c2c3eb8752694e19 Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
Adding in upper constraints python-keystoneclient 5.6.0 in case we need to run anything based on python 3.9. Signed-off-by: Arx Cruz <arxcruz@redhat.com> Change-Id: Ifcdece51355722805487f4760911223b553e4c1c
Consumers have chronically looked to our list of tested dependency versions for guidance on what to install, without realizing their use case is different from ours or considering the security implications of that choice. Include a prominent security warning in the README.rst, global-requirements.txt and generated upper-constraints.txt files in hopes of making these risks clearer. Change-Id: If012a379f0c4ec63825a9617972d4579c9c1b413 Signed-off-by: Jeremy Stanley <fungi@yuggoth.org>
Change I5689985fd8ab2a061c04776c5320188343b2f077 removed the only user of these methods. Change-Id: Iba0f75ca0e3efaf6a89baa73ab989c7eaecd440f Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
We not not appear to have ever emitted this header (or rather, set prefix to True). Change-Id: I6e289c91b8efad227778c1a5c4b519458c1aa600 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This is no longer used. Change-Id: I71720113bf00bac881d50bd362bef9214b322952 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Another one we no longer use. Change-Id: Id2b68540db32c6c199cc1c7922fb71e560205163 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: Ibf201417a67c94370f3cdb881e5e1f324b7f47a6 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
- Remove the 'linters' testenv: this battle has been lost - Don't install package for the 'pep8' testenv: it's unnecessary - Remove 'safety' from 'pep8' testenv: the command we were using is deprecated and the new one requires authentication - Fix the 'bindep' testenv so it (once again) skips install of the package and do the same for the 'pep8' and 'babel' testenvs - Stop setting 'basepython': everything is Python 3 nowadays (tox 4 *only* supports that) - Remove a linter from the 'test-requirements.txt' file: these dependencies are managed by tox - Fix some indentation Change-Id: I4805d1ac0fa0209c59f3815352ff9ea54108eca2 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
ValKey is a fork of Redis after its unfortunate license change, and some distros prefer ValKey to Redis. For example CentOS Stream 10 will provide Valkey, not Redis. The client library is required to allow users to replace redis by valkey if they want. - Is the library actively maintained? Yes - Is the library good code? Yes - Is the library python 3 compatible? Yes - Is the library license compatible? Yes, MIT. - Is the library already packaged in the distros we target (Ubuntu latest / Fedora latest)? Yes - Is the function of this library already covered by other libraries in global-requirements.txt? It's currently almost equivalent to redis-py but may diverge at any time. - Is the library required for OpenStack project or related dev or infrastructure setup? (Answer to this should be Yes, of course) Which? oslo.cache, tooz and taskflow. - If the library release is managed by the Openstack release process does it use the cycle-with-intermediary release type? No Change-Id: I42991d966518d7aedd6cb27a857f088eaf0da8d3 Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
... to include the fix for recent Redis and ValKey[1]. [1] jd/pifpaf#203 Change-Id: I0bf46170231224198fa395f0d5f4706044025794 Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
lark is a pure-Python parser toolkit/library.
Is the library actively maintained?
Yes - Last version release was 3 weeks ago (22 September 2025).
Is the library good code?
Yes - The interface for defining a parser and generating a parse tree from
said parser is straight-forward and works as expected. There is a robust
unit test suite included in lark's repository. PRs to lark's codebase
must pass CI checks which include tests for Python 3.{8-12}.
Is the library Python 3 compatible?
Yes - demonstrably so through lark's unit tests.
Is the library license compatible?
Yes - MIT.
Is the library already packaged in the distros we target?
Yes:
- debuntu: https://packages.ubuntu.com/noble/python3-lark
- others: https://pkgs.org/search/?q=lark
Is the function of this library already covered by other libraries
in global-requirements.txt?
Partially yes. Pyparsing exists already but only provides support for PEGs
(Parsing Expression Grammars) whereas lark supports CFGs
(Context-Free Grammars), ambiguous grammars, and builds parse-trees.
Lark is also significantly faster and less memory intensive than
Pyparsing. Based on: https://github.com/goodmami/python-parsing-benchmarks
Is the library required for OpenStack project or related dev or
infrastructure setup? Which?
Yes. Ironic. Lark is being used to parse filter expressions as outlined
in this approved spec for ironic:
https://opendev.org/openstack/ironic-specs/src/branch/master/specs/approved/trait-based-port-scheduling.rst#Filters
If the library release is managed by the Openstack release process does it use
the cycle-with-intermediary release type?
No - N/A
Change-Id: Id4d91b5297b04cf680ed6d52e1c9eb08a8ae3830
Signed-off-by: Clif Houck <me@clifhouck.com>
github-actions
bot
added
automated
priteau
approved these changes
Oct 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains a snapshot of master from upstream master.