Closed JCZuurmond closed 2 weeks ago
This is confusing. What is the rationale for not raising a library-not-found
problem when a library is not found ?
Oh you mean because of suppress(ImportError)
?
My recommendation would be to provide a mechanism for manually dismissing noisy advices, rather than tackle such complex scenarios
An alternative to suppressing the message is fine to me. I like the separation of concern of first detecting the library-not-found
and then suppressing it in certain cases. I would prefer an automated approach over manual, depending on the frequency it occurs
we need to see if the originating import
node has try: ... except: ...
blocks. or with contextlib.suppress(ImportError)
would be fine as well.
Already fixed, closing.
Is there an existing issue for this?
Current Behavior
We raise an library not found problem with the following code snippet.
Similar to #1705
Expected Behavior
No problem should be raised. The library is not found, however, that is as expected
Steps To Reproduce
Cloud
Azure
Operating System
macOS
Version
latest via Databricks CLI
Relevant log output
No response