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

Pandas pickle dump format #123

Closed
mariustk opened this issue Apr 3, 2024 · 4 comments · Fixed by #124
Closed

Pandas pickle dump format #123

mariustk opened this issue Apr 3, 2024 · 4 comments · Fixed by #124
Assignees

Comments

@mariustk
Copy link

mariustk commented Apr 3, 2024

For multiple reasons a pandas dataframe might be stored in pickle format. This format have advantages in speed and size compared with csv and json. However it is not directly supported by qats, typically we have patched a qats installation with a pickle reader, however it is not optimal to do this every time a new release of qats is published.

An additional pandas pickle format to load pandas pickle dumps.

I can push a commit if I am added as contributor.

@mariustk
Copy link
Author

mariustk commented Apr 3, 2024

image

@eneelo
Copy link
Collaborator

eneelo commented Apr 9, 2024

Hi, this looks interesting! I will add you as a contributor so that you can push a branch and create a pull request. (Unless you have forked it? Then I would expect that you might be allowed to create a pull request from the fork).

Edit:
@mariustk As far as I can see, you should be able to push a branch although not specifically added as contributor (unless policies have change somehow). Have you tried?

@tovop
Copy link
Collaborator

tovop commented Apr 9, 2024

Hi @mariustk 😀 This is very welcome. Indeed a handy format. Please add tests and example(s) too.

@mariustk
Copy link
Author

It seems like forking it allowed me to create a pull request! @eneelo
#124

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 a pull request may close this issue.

3 participants