-
Notifications
You must be signed in to change notification settings - Fork 87
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
cached files need python version information in filenames #1551
Comments
The change in checksums went in in #1537. @chriscrsmith do you happen to have the old annotations? |
Hm so this means we could recreate the old files by using the pre- #1522 maintenance script. |
I've got a copy of the old annotation here, I think: |
Note: the cache directory is what's returned by
|
@nspope 's file has all the |
I also ran into this error while trying to run the human production config for the analysis2 paper. I followed the Development installation guide here but still have the same error. This is the version I'm on when checking with |
We need:
|
Update: after reinstalling the github Development version using
which may be why I have this warning |
Thanks - that all seems as expected; perhaps the warning could be more informative, though. |
I have AraTha and DroMel 235105850a365f7f171c459d4c5ee50483e0c17e3b2b0232412d22addca9915f edit: |
Yes!!! @silastittes, this should save you some work! (I'm re-uploading the files directly here.) |
Update: we have uploaded the files above to AWS; so now 0.2.0 should work. However, this means that now github HEAD is broken; next on the list is to fix that. |
Okay, so I'm proposing doing
If we do this, then the |
Closed in #1553. |
Over on slack, Alan Izararras pointed out that running
with version 0.2.0 now errors with
I can confirm this.
So, currently doing
pip install stdpopsim
and running that code does not work.I'm pretty sure that the problem is that we've replaced the files on amazon with new ones that have different hashes; thus breaking previous versions of the software.
I think the solution is to (a) put back the old files, and (b) add a naming convention to the files so we don't clobber previous ones.
Some suggestions for the naming convention (first suggestion best I think):
For each file, just append a file-specific version number, like
filename_v1.tar.gz
. Then we just need to update the version number whenever we update the file, no fragile programming required (like in 1 and 2 below).directory structure on amazon like
and the files within each of these would be symlinks to the previous one unless they had been updated. This would let us keep the actual file names the same (maybe bad).
filename_%version%.tar.gz
, again with most of these being symlinks.The text was updated successfully, but these errors were encountered: