Skip to content
This repository was archived by the owner on Jan 15, 2026. It is now read-only.
This repository was archived by the owner on Jan 15, 2026. It is now read-only.

Functions should not exit on requests.exceptions.RequestException #14

Description

@doug-the-guy

I'm using this API from another script and I've been dealing with the following error:

("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer'))

I tracked it down to the enterprise LiveHunt function I was using which was catching a requests.exceptions.RequestException, printing the exception and then calling exit(1) which left my script hanging. This is the case for every function that wraps an API endpoint.

I recommend instead to just raise the RequestException or wrap it in some custom exception and let the calling code deal with it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions