-
Notifications
You must be signed in to change notification settings - Fork 66
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
"Unsatisfiable Requirement" edge case error when juliacall
is upgraded but Julia registries are not
#428
"Unsatisfiable Requirement" edge case error when juliacall
is upgraded but Julia registries are not
#428
Comments
I'd be OK with adding an unconditional |
Thanks @cjdoris , I checked in julia and This may really be an issue for
I'm not entirely sure how juliapkg uses the .json files internally, maybe there is some subtlety. My concern with the explicit call to Any thoughts? Next time a version of PythonCall/juliacall is released, I can check. Unfortunately this edge case is rather hard to reproduce. |
Actually this would be a change to juliapkg so no worries there. It doesn't sound like that would fix things anyway, if the registry does update. You can roll back to an old version of the registry by cloning the registry repo and checking out an old commit. Can you do that and see if you can reproduce the issue? |
Sure, I will try this sometime next week |
Nm i had a chance to look just now. Steps to reproduce:
cd /tmp
git clone [email protected]:JuliaRegistries/General.git
cd General
git reset 46f90400dd
git checkout -- . && git clean -fd
conda create -n pyjlcheck
conda activate pyjlcheck
pip install juliacall==0.9.14
python -c 'from juliacall import Main as jl'
] registry rm General
] registry add /tmp/General
cd /tmp/General
git pull
pip install juliacall==0.9.15
from juliacall import Main as jl errors out with full logs:
I can confirm that taking that command
fails but adding
|
PR submitted to resolve this in |
Hello, I have a potential issue originally posted as a Discussion a few weeks back. I haven't gotten any responses, so I'm moving it to an issue in hopes of getting more traction. If my solution of adding another env var that, if set, calls
Pkg.registry.update()
inside the initialization script seems reasonable, I can try my hand at a PR.Discussed in #422
Originally posted by brian-dellabetta November 9, 2023
Hi there,
we have come across an edge case when upgrading PythonCall/juliacall, and I am curious if anyone knows of a workaround or clean solution.
Initial Condition:
juliacall==0.9.14
installed in their Python env[email protected]
installed in the Julia project that juliacall links to.[email protected]
available.Steps to reproduce:
pip install juliacall==0.9.15
from juliacall import Main as jl
This will result in the following error:
All I need to do is run
jl.seval("import Pkg; Pkg.registry.update()")
but I can't get access to jl, I hit the error above first. Any suggestions on how to programmatically resolve this, ideally in Python? Hoping there's a way without having to editjuliacall
source code to allow for an init/startup script. If that is the case, I can create an issue and take a shot at a PR. It may be as simple as adding another env var option that injectsPkg.registry.update()
in the init script somewhere around this line.Thanks!
The text was updated successfully, but these errors were encountered: