-
Notifications
You must be signed in to change notification settings - Fork 101
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
Short-term prioritization of PRs/issues #510
Comments
Would you be interested in joining the JuliaPy Github organization? |
Yeah sure why not! |
@ararslan , could you invite Miles to JuliaPy? |
Thanks for injecting some life here. My 2c (which can be readily ignored, since I have no free time to devote atm 😢) is that the top priority should be removing roadblocks for a non-Julia user that wants to quickly use some Julia code, or to use a Python package which is using some Julia code under the hood. To that end, happy to see #487 at the top of the list, as, from the experience of setting up several users, the experience is sadly really really bad. You might also consider #496 instead, but I think that's harder, so probably best to focus on the low-hanging fruit first. |
No problem. I have zero time to work on new features unfortunately, but I think helping review/merge maintenance PRs should be ok. |
I think some PRs/issues are quite important and should be merged/fixed soon after #508 is done. Here is a ranking of what I think the most important PRs are:
find_spec
implemented in JuliaImporter #509PYTHONPATH
injulia_py_executable
to find julia-py #445cc @mkitti @tkf @marius311
Feel free to suggest any I missed. Once #508 is merged I think the high importance ones should be merged relatively soonish.
The text was updated successfully, but these errors were encountered: