-
Notifications
You must be signed in to change notification settings - Fork 110
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
Make it possible to run from Enviroments that do not directly have Pycall #493
Conversation
…rectly have PyCall
Cool cool. Is there a guide somewhere on how Project.toml and the whole environment-based package system works? |
Pkg.jl docs. It could be better, but I have tried and I can't make it better yet. |
OK, I get what this PR does now. Looks good, merge when you're ready. |
Codecov Report
@@ Coverage Diff @@
## master #493 +/- ##
==========================================
+ Coverage 49.04% 49.32% +0.28%
==========================================
Files 79 79
Lines 2659 2668 +9
==========================================
+ Hits 1304 1316 +12
+ Misses 1355 1352 -3
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #493 +/- ##
==========================================
+ Coverage 49.04% 49.32% +0.28%
==========================================
Files 79 79
Lines 2659 2668 +9
==========================================
+ Hits 1304 1316 +12
+ Misses 1355 1352 -3
Continue to review full report at Codecov.
|
This adds a Project.toml
so that we can run the workers in the TensorFlow enviroment,
which will have PyCall for sure.
When making the Project.toml i did not both to transcribe the Compat rules,
since they are basically not julia 0.7 compat anyway.