-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[mypy
] Implicit re-imports in trieste.acquisition.__init__
#751
Comments
Need to decide whether this is worthwhile or not. Pros
Cons
|
This is not true - this behaviour is not code duplication, this is being explicit on what
Where would that flag go? Not sure how a user of
See this: error: Class cannot subclass "AcquisitionFunctionClass" (has type "Any") [misc] which originates from the same issue. |
We'll probably want to fix this in gpflux before fixing it in trieste. AFAICT gpflow already uses |
Also we'd probably want to generate and verify |
See this:
Running
mypy --strict
on this yields:Changing the import to
solves the problem, but then the
trieste.acquisition.__init__
is pointless.How to solve
Add
__all__ = ["AcquisitionFunctionClass", ...]
(and everything that needs to be reimported) to thetrieste.acquisition.__init__
.The text was updated successfully, but these errors were encountered: