To not add too much mess to the history of the repo, it would be possible to squash the changes here into a single commit.
@denker Any preferences here?
Rebased version of #8
To not add too much mess to the history of the repo, it would be possible to squash the changes here into a single commit.
@denker Any preferences here?
I had trouble getting this to run, I think now I figured out why -- it seems the new static versions of the python-neo, elephant and odml libraries are inserted as git-annex objects, and thus exist only as empty links.
I would suggest to either add them as regular git files (maybe this requires opening a new PR?), or we could think of even getting rid of static versions (in favor of a regular requirements.txt).
I had trouble getting this to run, I think now I figured out why -- it seems the new static versions of the `python-neo`, `elephant` and `odml` libraries are inserted as git-annex objects, and thus exist only as empty links.
I would suggest to either add them as regular git files (maybe this requires opening a new PR?), or we could think of even getting rid of static versions (in favor of a regular `requirements.txt`).
Sure, we can also remove the static versions. Did you by chance test this code also directly with the latest versions? If these are compatible we could directly jump to the current release versions.
Sure, we can also remove the static versions. Did you by chance test this code also directly with the latest versions? If these are compatible we could directly jump to the current release versions.
That being said -- I hope we get Elephant 0.11 out the door next week, and it may make sense to wait for that (current version elephant 0.10 is pinned to neo<0.10.0, so that this would conflict).
That being said -- I hope we get Elephant 0.11 out the door next week, and it may make sense to wait for that (current version elephant 0.10 is pinned to `neo<0.10.0`, so that this would conflict).
Rebased version of #8
To not add too much mess to the history of the repo, it would be possible to squash the changes here into a single commit. @denker Any preferences here?
@denker Are there any more changes that need to be included here?
None are planned from my side, however there might be already new versions of the updated software packages.
@denker Can you merge this rather sooner than later as we are lagging already one neo version behind?
I had trouble getting this to run, I think now I figured out why -- it seems the new static versions of the
python-neo,elephantandodmllibraries are inserted as git-annex objects, and thus exist only as empty links.I would suggest to either add them as regular git files (maybe this requires opening a new PR?), or we could think of even getting rid of static versions (in favor of a regular
requirements.txt).Sure, we can also remove the static versions. Did you by chance test this code also directly with the latest versions? If these are compatible we could directly jump to the current release versions.
Good point, I'll test that. Hope there are no
ChannelGroups in...That being said -- I hope we get Elephant 0.11 out the door next week, and it may make sense to wait for that (current version elephant 0.10 is pinned to
neo<0.10.0, so that this would conflict).We should still