summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Revert "Moves supported python runtimes from version 3.8 to 3.10""HEAD5.1.0masterZuul2023-05-081-1/+2
|\
| * Revert "Moves supported python runtimes from version 3.8 to 3.10"Ghanshyam2023-05-051-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit da129b1c53b8f529656c48a26d495a8664a3c901. Keeping Python 3.10 in setup.cfg classifier and zuul.yaml changes. Reason for revert: Needed-By: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/882175 TC has been discussing about re-adding the python 3.8 testing in current master 2023.2 release testing. - https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#l-191 - https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033469.html While governance changes are under review, TC agreed to add py3.8 testing so that we do not see more project/lib dropping python 3.8 and make them uninstalable on python 3.8 - https://meetings.opendev.org/meetings/tc/2023/tc.2023-05-02-18.00.log.html#l-17 - https://review.opendev.org/c/openstack/governance/+/882165 Also adding py3.8 testing back in job https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/882175 Change-Id: Ibf0960703d78ccfcb39421ee4b1cfee2c787d85a
* | Merge "Moves supported python runtimes from version 3.8 to 3.10"Zuul2023-04-112-3/+3
|\ \ | |/
| * Moves supported python runtimes from version 3.8 to 3.10Takashi Kajinami2023-04-102-3/+3
| | | | | | | | | | | | | | | | Within 2023.2 python version 3.9 and 3.10 are the supported python runtimes [1]. [1] https: //review.opendev.org/c/openstack/governance/+/872232 Change-Id: I1a6a349a3fc37c8afcb908d95622176c74ba5fbf
* | Merge "Catch NotADirectoryError error"Zuul2023-04-111-1/+1
|\ \ | |/ |/|
| * Catch NotADirectoryError errorStephen Finucane2022-09-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Per the documentation [1]: exception NotADirectoryError Raised when a directory operation (such as os.listdir()) is requested on something which is not a directory. On most POSIX platforms, it may also be raised if an operation attempts to open or traverse a non-directory file as if it were a directory. Corresponds to errno ENOTDIR. Apparently creating a packaged application can cause this issue. There's no harm in ignoring it so do just that. Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Closes-bug: #1980383 Change-Id: I19b14c7f3b70bee5310cafcaa90fcee9003713c6
* | Update master for stable/2023.1OpenStack Release Bot2023-02-242-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/2023.1. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2023.1. Sem-Ver: feature Change-Id: I9d9ccd7a52c0ca41a433620fedd959243aac5cb6
* | Merge "Remove Extension.extras"5.0.0Zuul2023-01-233-27/+7
|\ \
| * | Remove Extension.extrasStephen Finucane2022-10-043-27/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The behavior of the 'EntryPoint.extras` attribute that this exposes has changed in recent versions of 'importlib_metadata'/'importlib.metadata'. In change Iff536d4f4267efbebc4be1e7e5da8a9fde39f79b we applied a temporary fix to preserve the legacy behavior on these newer versions, however, given that this is actually a deprecated attribute [1], the best long-term option seems to be not exposing things. Do just that. [1] https://packaging.python.org/en/latest/specifications/entry-points/#data-model Change-Id: Id772d9f002e6945666685138bdef8f8ca32b5229 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* | | Order old importlib-metadata results by group4.1.1Ian Wienand2022-10-191-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A Debian Buster-based zuul-jobs test started failing when using stestr recently [1]. Upon further investigation, this is a Python 3.7 environment which is affected by a recent breaking change to importlib_metadata. It seems stevedore worked around this with Ib9c2b0a14edea91e97d122d2ac93b650029f918e, which was released with 3.5.1 -- but I was still seeing the issue. Upon further investigation, the "real_groups" dict being returned here with importlib-metadata 4.12.0 is in buckets by group, e.g. {'group.one': [EntryPoint(name='foo', ... , group='group.one'), EntryPoint(name='bar', ... , group='group.one')], 'group.two': [EntryPoint(name='moo', ... , group='group.two'), EntryPoint(name='goo', ... , group='group.two')], } This current code seems to return a dict with entry-points by thier name, e.g. {'foo': EntryPoint(name='foo', ... , group='group.one), 'bar': EntryPoint(name='bar', ... , group='group.one), 'moo': EntryPoint(name='moo', ... , group='group.two), 'goo': EntryPoint(name='goo', ... , group='group.two) } This reorgansies the fixup routine to put entry-points in a bucket by their group. With this change, stestr is again finding it's command plugins. [1] https://github.com/mtreinish/stestr/issues/336 [2] https://github.com/python/importlib_metadata/issues/409 Change-Id: I3496ab1dfa312b1098a869cdfd9a0c6f81653b28
* | | Merge "Add Python3 antelope unit tests"4.1.0Zuul2022-10-051-1/+1
|\ \ \
| * | | Add Python3 antelope unit testsOpenStack Release Bot2022-09-091-1/+1
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for antelope. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: Ibf3e8d63a7a43e65ac626e50ef42831c4a9b5e41
* | | Merge "Fix compatibility with Python 3.12, importlib-metadata 5.0"Zuul2022-10-052-2/+18
|\ \ \ | | |/ | |/|
| * | Fix compatibility with Python 3.12, importlib-metadata 5.0Stephen Finucane2022-10-042-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | importlib-metadata 5.0 has removed support for dict-style interaction with entrypoints [1]. This is going to eventually affect us when Python 3.12 is released but even before then anyone not properly using upper constraints with an older Python 3.7-based release (the only Python version where we require the third-party importlib-metadata package rather than the stdlib importlib.metadata package) will be bitten. Fix it now to address both. [1] https://github.com/python/importlib_metadata/commit/dde2b9de2973ce1c6fa9ba21dfe81069b0baa77b Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Change-Id: Ib9c2b0a14edea91e97d122d2ac93b650029f918e Closes-Bug: #1991559
* | | Merge "Fix compatibility with Python 3.10, 3.9.11"Zuul2022-10-051-11/+19
|\ \ \ | |/ /
| * | Fix compatibility with Python 3.10, 3.9.11Stephen Finucane2022-10-041-11/+19
| |/ | | | | | | | | | | | | | | | | | | | | | | A fix to 'importlib.metadata' in Python 3.10 [1], later backported to 3.9 and released in 3.9.11 [2], has broken our tests. Fix them. [1] https://github.com/python/cpython/commit/b1e286860742e7ba6fadc75e3ddb6c2899a56919 [2] https://github.com/python/cpython/commit/177be52517da9a876a3f9e670f88c4731b906986 Signed-off-by: Stephen Finucane <stephenfin@redhat.com> Closes-bug: #1966040 Change-Id: Iff536d4f4267efbebc4be1e7e5da8a9fde39f79b
* | Merge "remove unicode from code"Zuul2022-10-032-14/+14
|\ \ | |/ |/|
| * remove unicode from codewangjiaqi072022-08-252-14/+14
| | | | | | | | Change-Id: Ib4c9f766b2844d8a3cdc748fbd9ef98b81aec5a5
* | Update master for stable/zedOpenStack Release Bot2022-09-092-0/+7
|/ | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/zed. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/zed. Sem-Ver: feature Change-Id: I258603f7e7304c3e852d6d47bae5e024e33a90f7
* Fix remaining logic to support Python 3.6/74.0.0Takashi Kajinami2022-06-215-27/+4
| | | | | | | | | ... because this library no longer supports these old versions and requires Python >= 3.8 now[1]. [1] 8efaa1ceb82300cce19acaf3d5ecd969f6dab3e0 Change-Id: I2b229b24425d3afb9159b2479bd9547e3443011f
* Drop python3.6/3.7 support in testing runtimeHervé Beraud2022-05-051-3/+3
| | | | | | | | | | | | In Zed cycle testing runtime, we are targetting to drop the python 3.6/3.7 support, project started adding python 3.8 as minimum, example nova: - https://github.com/openstack/nova/blob/56b5aed08c6a3ed81b78dc216f0165ebfe3c3350/setup.cfg#L13 Also indicates that we support python 3.9. Change-Id: I1bdec397b1ac563b09174763c20e8a91e5f86143
* Add Python3 zed unit testsOpenStack Release Bot2022-03-041-1/+1
| | | | | | | | | | | This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for zed. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: I5fab51857949a743a07d4639f5e0ba114de19eab
* Update master for stable/yogaOpenStack Release Bot2022-03-042-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/yoga. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/yoga. Sem-Ver: feature Change-Id: I732f42ae437931a824aba788bf434f85100f06fa
* Add Python3 yoga unit tests3.5.0OpenStack Release Bot2021-09-101-1/+1
| | | | | | | | | | | This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for yoga. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: Ia489c3d9a47828961b7a8fe736c3bc1ddaaa32cc
* Update master for stable/xenaOpenStack Release Bot2021-09-102-0/+7
| | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/xena. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/xena. Sem-Ver: feature Change-Id: I6195a346563189a6867482950b13eda11e0fb5d2
* Rely on member access, the preferred access since importlib_metadata 4.8.Jason R. Coombs2021-09-011-1/+1
| | | | | Change-Id: I20a7fe4240cf78e6b863951740c2d0fe9aa28132 Closes: #1941991
* Merge "setup.cfg: Replace dashes with underscores"3.4.0Zuul2021-05-261-4/+4
|\
| * setup.cfg: Replace dashes with underscoresmaaoyu2021-05-041-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1]. Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead [1] https://github.com/pypa/setuptools/commit/a2e9ae4cb Change-Id: I394e12bf1816e4e23e4f547db4bae89547af7989
* | Merge "Fix formatting of release list"Zuul2021-05-261-12/+12
|\ \ | |/ |/|
| * Fix formatting of release listPierre Riteau2021-04-161-12/+12
| | | | | | | | Change-Id: I86d06e8b665e4440f6c67e1de8cd3a217ac1d166
* | Merge "Add Python3 xena unit tests"Zuul2021-04-161-1/+1
|\ \
| * | Add Python3 xena unit testsOpenStack Release Bot2021-03-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for xena. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: Ib5e435c53f7719b6e64a550c0aec6a2d0d576839
* | | Remove lower-constraints remnantswu.shiming2021-04-162-34/+0
| |/ |/| | | | | | | | | These were missed in change: I62d911111b54976a9df726c48f593a52e275fe6c Change-Id: I4f07ec3617d5e73abbabd45234fe4e67ec395fdb
* | Merge "Update master for stable/wallaby"Zuul2021-04-152-0/+7
|\ \ | |/
| * Update master for stable/wallabyOpenStack Release Bot2021-03-182-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/wallaby. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/wallaby. Sem-Ver: feature Change-Id: I73998aa60325a26fc11418a0b37c1f4524469e32
* | Move flake8 as a pre-commit local target.Daniel Bengtsson2021-03-231-10/+14
|/ | | | | | | | | | | | | | | The goal here is to avoid conflicts between flake8 and hacking version each 2 days. Inspired from nova's approach[1]. The flake8 version to install will be determined by hacking and requirements[2] will stay aligned instead of relying on different versions. [1] https://opendev.org/openstack/nova/src/branch/master/.pre-commit-config.yaml#L26-L35 [2] https://opendev.org/openstack/hacking/src/branch/master/requirements.txt#L1 Change-Id: I9ffd46865477b3fa7d43258d67dd0ec224ee6467
* Merge "Use TOX_CONSTRAINTS_FILE"Zuul2021-01-221-3/+3
|\
| * Use TOX_CONSTRAINTS_FILEHervé Beraud2020-11-041-3/+3
| | | | | | | | | | | | | | | | | | | | | | UPPER_CONSTRAINTS_FILE is old name and deprecated This allows to use upper-constraints file as more readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>. [1] https://review.opendev.org/#/c/722814/ [2] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file Change-Id: I03900ffe9e59ad3f4f8f89329a9e1b9c6844b1b1
* | Dropping lower constraints testingHervé Beraud2020-12-181-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | We facing errors related to the new pip resolver, this topic was discussed on the ML and QA team proposed to to test lower-constraints [1]. I propose to drop this test because the complexity and recurring pain needed to maintain that now exceeds the benefits provided by this mechanismes. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html Change-Id: I62d911111b54976a9df726c48f593a52e275fe6c
* | Merge "Use py3 as the default runtime for tox"3.3.0Zuul2020-11-061-1/+1
|\ \
| * | Use py3 as the default runtime for toxHervé Beraud2020-11-031-1/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Moving on py3 as the default runtime for tox to avoid to update this at each new cycle. Wallaby support officially the following runtimes [1]: - Python 3.6 - Python 3.8 During Victoria Python 3.7 was used as the default runtime [2] however this version isn't longer officially supported. [1] https://governance.openstack.org/tc/reference/runtimes/wallaby.html#python-runtimes-for-wallaby [2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria Change-Id: Ieb5fd2c1efd9297b9b589e6f13cbe5e0a4cb73cb
* | Merge "Fix cache dir flooding when running from /tmp"Zuul2020-11-053-8/+80
|\ \ | |/ |/|
| * Fix cache dir flooding when running from /tmpArtem Goncharov2020-09-143-8/+80
| | | | | | | | | | | | | | | | | | | | Ansible invokes modules with executable placed under /tmp. This causes stevedore caching to create bazillions of useless cache files. When we can identify we run with executable under /tmp or if in the target cache directory an empty file '.disable' is present - skip writing cache. Change-Id: Ic483ac68027505402ba32d7f612631e15a678d09
* | Merge "Adding pre-commit"Zuul2020-10-0521-299/+317
|\ \
| * | Adding pre-commitHervé Beraud2020-09-1521-299/+317
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduced changes: - pre-commit config and rules. - Add pre-commit to pep8 gate, Flake8 is covered in the pre-commit hooks. - Applying fixes for pre-commit compliance in all code. Also commit hash will be used instead of version tags in pre-commit to prevend arbitrary code from running in developer's machines. pre-commit will be used to: - trailing whitespace; - Replaces or checks mixed line ending (mixed-line-ending); - Forbid files which have a UTF-8 byte-order marker (check-byte-order-marker); - Checks that non-binary executables have a proper shebang (check-executables-have-shebangs); - Check for files that contain merge conflict strings (check-merge-conflict); - Check for debugger imports and py37+ breakpoint() calls in python source (debug-statements); - Attempts to load all yaml files to verify syntax (check-yaml); - Run flake8 checks (flake8) (local) For further details about tests please refer to: https://github.com/pre-commit/pre-commit-hooks Change-Id: I045fa1cd7932d960e1cf49b2c335c7acdeba0b46 Signed-off-by: Moisés Guimarães de Medeiros <moguimar@redhat.com>
* | | Add Python3 wallaby unit testsOpenStack Release Bot2020-09-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an automatically generated patch to ensure unit testing is in place for all the of the tested runtimes for wallaby. See also the PTI in governance [1]. [1]: https://governance.openstack.org/tc/reference/project-testing-interface.html Change-Id: I1a592855fcb07e982b7b25688026646d51961096
* | | Update master for stable/victoriaOpenStack Release Bot2020-09-112-0/+7
| |/ |/| | | | | | | | | | | | | | | | | | | | | Add file to the reno documentation build to show release notes for stable/victoria. Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/victoria. Change-Id: I111d3307dd6af6d814d5f685f3acd7a41e5168e0 Sem-Ver: feature
* | fix supported python versions in documentationvictoria-em3.2.2Evgeni Golov2020-09-081-1/+1
| | | | | | | | Change-Id: Ia92d5b8f6194d9f7ba2f3221fe378dafe23be567
* | Fix the bug 1892610. There're some syntax errors in the comment of stevedore ↵3.2.1zhangziwen2020-08-236-9/+9
|/ | | | | | | | | | | | | | code. There is a syntax error in the comment of stevedore code. For example, in the HookManager class: :param on_load_failure_callback: Callback function that will be called when a entrypoint can not be loaded. Here should not be `a entrypoint`, just `an entrypoint` instead. Fixes: bug #1892610 Change-Id: Ic2aaf5f467bcecaec6adff1ead8e159ae749ac50
* add property methods to extension for more entry point values3.2.0Doug Hellmann2020-07-123-0/+73
| | | | | | | | | The underlying EntryPoint class has some similar methods to fetch these values, but they depend on the version of importlib.metadata that is installed, so this provides a consistent API Change-Id: I7a1b9541f0e4042a224e49c890ba3c63e8a5a259 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
View Lorry Controller Status