Skip to content

Standartize on Python tooling #15

@alexott

Description

@alexott

Currently, some of the subprojects utilize Hatch, while others are simply plain requirements files. It makes sense to unify on a common tooling - perhaps continue to use hatch or even switch to uv.

P.S. It would also be useful to discuss the repository structure - does it make sense to have a subdirectory per data source vs. having everything in one place and having optional dependencies?

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