Although pyLIQTR's requirements.txt lists an unversioned juliacall, I've found that newer versions of that package lead to versioning conflicts:
Exception: 'julia' compat entries have empty intersection:
- '^1' at /ram/tmp/resource-estimation/.venv/lib/python3.11/site-packages/juliapkg/juliapkg.json
- '1.0.0 - 1.11' at /ram/tmp/resource-estimation/.venv/lib64/python3.11/site-packages/juliacall/juliapkg.json (OpenSSL_jll)
- '^1.10.3' at /ram/tmp/resource-estimation/.venv/lib64/python3.11/site-packages/juliacall/juliapkg.json
- '~1.8, ~1.9' at /ram/tmp/resource-estimation/.venv/julia_env/pyjuliapkg/juliapkg.json
- '1.0.0 - 1.11' at /ram/tmp/resource-estimation/.venv/lib/python3.11/site-packages/juliacall/juliapkg.json (OpenSSL_jll)
- '^1.10.3' at /ram/tmp/resource-estimation/.venv/lib/python3.11/site-packages/juliacall/juliapkg.json
- '^1' at /ram/tmp/resource-estimation/.venv/lib64/python3.11/site-packages/juliapkg/juliapkg.json
The solution is to update requirements.txt to specify
Although pyLIQTR's
requirements.txtlists an unversionedjuliacall, I've found that newer versions of that package lead to versioning conflicts:The solution is to update
requirements.txtto specify