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
PyCall no longer used #124
Conversation
Do not merge. I'm not sure a version has been tagged. This is just a suggested text. PyCall is also still mentioned in two other files. |
The version is already tagged, so it's good to improve this. |
That was quick. I'm not really a SciML user or dev, so I didn't need credit. I'm at best a tester of SciML, out of curiosity to see how well PythonCall works with it (since I suggested that change). I get a wall of text, ERRORs and Warnings, likely not because of it though. While I think I know why, many Python users would probably not (nor would have my environment, the likely cause):
|
It's because you have weird packages in your environment. Normal people from Python won't have a whole environment full of junk to start with that block the packages from installing. |
Yes, what I thought. Is there a way or should there be a way that the package would use a clean environment? Python users shouldn't have to know or care about what Julia environments are ideally. Nor if they later start messing with Julia and install packages, screw things up for already installed Python "[impure] world". |
@LilithHafner do you know if there's a way that we can force this to always use an environment we control? |
Strange. I thaught this did it Line 46 in df65e85
|
What version of diffeqpy are you using? |
EDIT: it works now with later version (installation, didn't go further yet). I had version 1.1.0, or so I recall, pretty sure (maybe can't confirm since I now updated to later): I had to do (I suppose will be default soon, just quote new) and am trying again: I think it may be working now, i.e. I'm not seeing my environment, only that SciML is huge):
At least not all at latest, but plausibly not a problem. |
No description provided.