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

Spynoza not downloadable #19

Open
tknapen opened this issue Sep 13, 2018 · 1 comment
Open

Spynoza not downloadable #19

tknapen opened this issue Sep 13, 2018 · 1 comment

Comments

@tknapen
Copy link
Member

tknapen commented Sep 13, 2018

I don't know why this repo has become so huge, but it makes a repo unusable if you make a simple python package 1GB. Could someone delete their fMRI data from this repo?

@Gilles86
Copy link
Contributor

You can use the following one liner to get a list of largest file

git rev-list --objects --all \
| git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \
| sed -n 's/^blob //p' \
| sort --numeric-sort --key=2 \
| cut -c 1-12,41- \
| numfmt --field=2 --to=iec-i --suffix=B --padding=7 --round=nearest

It shows that the entire repo is about 540MB, with 400MB coming from spynoza/data.

I think the established approach for including data in your Python package is to put it somewhere that is not the git repository, and let the install script take care of it. Anyone care to pick this up?

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

No branches or pull requests

2 participants