You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, activating the venv before building your project should be sufficient as we normally use the first python3 binary found on the path to determine the interpreter configuration.
those of us on MacOs are still waiting on #1741. additionally, hot swapping venvs at runtime has more surface area than just updating the path as suggested in the linked issue. You also have to remove the sites-packages paths from preexisting venvs if they exist and account for platform differences in path name. This might actually be a small nice to have.
I have a python venv and in my opinion, there should be a function to load the venv into the pyo3 runtime. Something like
would make things very easy. Or is there a simple way how this is possible that I'm missing?
The text was updated successfully, but these errors were encountered: