saltbundlepy-pluggy
No description set
- Sources inherited from project systemsmanagement:s...ack:bundle:testing
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout systemsmanagement:saltstack:bundle:testing:CentOS7/saltbundlepy-pluggy && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_multibuild | 0000000053 53 Bytes | |
pluggy-1.0.0.tar.gz | 0000051510 50.3 KB | |
saltbundlepy-pluggy.changes | 0000009499 9.28 KB | |
saltbundlepy-pluggy.spec | 0000002099 2.05 KB |
Latest Revision
Alexander Graul (agraul)
accepted
request 1122609
from
Victor Zhestkov (vizhestkov)
(revision 3)
- Update to version 1.0.0 Deprecations and Removals * #116: Remove deprecated implprefix support. Decorate hook implementations using an instance of HookimplMarker instead. The deprecation was announced in release 0.7.0. * #120: Remove the deprecated proc argument to call_historic. Use result_callback instead, which has the same behavior. The deprecation was announced in release 0.7.0. * #265: Remove the _Result.result property. Use _Result.get_result() instead. Note that unlike result, get_result() raises the exception if the hook raised. The deprecation was announced in release 0.6.0. * #267: Remove official support for Python 3.4. * #272: Dropped support for Python 2. Continue to use pluggy 0.13.x for Python 2 support. * #308: Remove official support for Python 3.5. * #313: The internal pluggy.callers, pluggy.manager and pluggy.hooks are now explicitly marked private by a _ prefix (e.g. pluggy._callers). Only API exported by the top-level pluggy module is considered public. * #59: Remove legacy __multicall__ recursive hook calling system. The deprecation was announced in release 0.5.0. Features * #282: When registering a hookimpl which is declared as hookwrapper=True but whose function is not a generator function, a PluggyValidationError exception is now raised. * #309: Add official support for Python 3.9. * #251: Add specname option to @hookimpl. If specname is provided, it will be used instead of the function name when matching this hook implementation to a hook specification
Comments 0