Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decouple deps #9

Merged
merged 38 commits into from
Jan 16, 2024
Merged

Decouple deps #9

merged 38 commits into from
Jan 16, 2024

Conversation

FrancescAlted
Copy link
Member

The idea is that the simple API should depend on very little libs external to Python (httpx, numpy and little else).

Still WIP.

FrancescAlted and others added 30 commits January 8, 2024 17:43
Which should be moved to services.
By explicitly checking for boolean in JSON object without going through schema
validation.
As many will be used both by services and clients.
Clients are the only users, and it avoids some extra dependencies in services.
So as to decouple reporting from the function itself.

And define tqdm-based reporter right in command-line client.
Although this may be completely dropped later on.
@FrancescAlted
Copy link
Member Author

This starts to be mature enough for a review.

The old code failed to get a proper dtype from metadata to build the
uninitialized dataset.

Allow testing by adding such a dataset to example files.
Copy link
Collaborator

@ivilata ivilata left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@FrancescAlted FrancescAlted merged commit ab29f28 into main Jan 16, 2024
1 check passed
@FrancescAlted FrancescAlted deleted the decouple-deps branch January 16, 2024 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants