Skip to content

Asserts fail with no message #324

Open
@cab938

Description

@cab938

I was trying to programmatically interact with the nbclient package and kept getting blank assertion errors being thrown. It was a bit of a mess on my end to track down since nbclient was being hidden behind numerous other libraries I was working with, here's one of the ones which would regularly throw, indicating that there is no kernel available:

assert self.kc is not None

Any reason to use asserts here instead of something more friendly to calling libraries, e.g. a new KernelNotConfiguredException?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions