-
Notifications
You must be signed in to change notification settings - Fork 8
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
TyPython path can't update in new python envs #13
Comments
This problem can be split into the following two parts:
|
1. Cleanup: remove pydantic and toml 2. Use interpreted Julia to speed up some resolution 3. Managed to distinguish the correctness of a project's TyPython dependency. (partially address #13)
* remove redundant init * fix typo of ORM * improve initialization * further improve initialization: 1. Cleanup: remove pydantic and toml 2. Use interpreted Julia to speed up some resolution 3. Managed to distinguish the correctness of a project's TyPython dependency. (partially address #13) * lazy annotations * remove unused deps * when julia exits the first, Python should know things are dead. * try support 1.6
It's seems that we didn't check the path of package Lines 161 to 167 in 4ddd6e8
ps: #44 uses default environment in |
If we have install jnumpy in python environment
envA
and execjnumpy.init_jl()
once, we will add TyPython path in our default projectManifest.toml
. But if we create a new python environment and install new version jnumpy, the old one still work so the path inManifest.toml
would not update.Maybe we should use different default Julia environments in every different python environments?
jnumpy/jnumpy/defaults.py
Lines 50 to 52 in e5c92bf
The text was updated successfully, but these errors were encountered: