-
Notifications
You must be signed in to change notification settings - Fork 28
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
Py2neo 3 compatibility #4
Comments
I actually think it shouldn't be too hard.
Other parts of the rephetio codebase may use py2neo directly, but I think you can just deal with any errors there as they arise. Luckily I think the py2neo upgrade is most likely to cause errors rather than silent bugs. Happy to review any pull requests! |
It's ideal if we can upgrade to py2neo 3 and then make a new hetio release. Therefore, you can choose your hetio release based on whether you want to use py2neo 2 or 3. |
I've forked After it seems that the new |
If I want to add additional features to |
You can add an Currently, I didn't put pandas or py2neo as dependencies although arguable they should be. Or we could put these packages in One option for the progress bar is that you can try to import tqdm. If it fails continue without if that's not too hard to implement. Otherwise, you can just make the progress bar always on. |
I've made some small modifications to |
I'm working on upgrading
hetio
to be compatible withpy2neo
3. Since many parts of therephetio
pipeline usehetio
, what do you think the easiest way would be to test them all?So far I've managed to get
hetio
to load nodes into Neo4j 3.1.1.The text was updated successfully, but these errors were encountered: