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.
Summary
The cloud portal now accepts shots settings up to 2000. This is not the case for direct-access resources, where the limit is 200.
This PR updates the shots upper bound for cloud resources. This requires having distinct options models for different resource types.
Details and comments
Qiskit
BackendV2._default_options
The default options reported by
BackendV2._default_options
are now aligned with the actual defaults provided by the relevant model. SinceBackendV2._default_options
must be a classmethod, the options model is retrieved from the_ResourceBase
type argument. An alternative would be to use a subclass hook, but this would be more invasive.Documentation
Sphinx support for type variables is provided by the new development dependency sphinx-toolbox.
Autodoc's
autoclass
/autoproperty
directives seem to assume that method return types are classes (!), thus the link to the_OptionsType
type variable for theoptions
property is not rendered and needs anitpicky
exception. The_ResourceBase
type argument is properly linked.