Skip to content

update requirements? #37

@weber-s

Description

@weber-s

Hello there!

The requirements pinned the dependencies to very specific version. Notably, the request package, that is more than 2 years old.

Is there a reason to pin the version that specifically? It is starting to be an issue when used with other libs.

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