amusecode
new install requires conda or venv?
My workflow is (more often I'd like to admit) a fully clean anaconda3, but the first step in the new install barfs at me, enforcing me to make an environment. I know this is a safe way of doing it, but is there no way to bypass this requirement?
Also, I happen to have a brew installed on linux, and the test for brew might depend on the command to be present? This could cause confusion in the setup script. I worked around it by disabling the brew command for the session and then it did see I was using ubuntu.
Do you mean that you set up a separate anaconda installation for each project, and then install into the base environment? Conda definitely recommends against installing anything except conda-build into the base environment, and pip-installing things without a virtualenv is going to be unsupported soon as well. So I'm afraid you'll need to make and activate an environment. I promise it won't hurt.
I do have a note somewhere that the Homebrew detection could also detect LinuxBrew and to swap the detection order, but I didn't implement it because I figured no one uses LinuxBrew anyway :facepalm:. Let's make fixing that the target of this issue.
yes, agreed. focus on brew.
My anaconda3 workflow is a mixed bag. In one instance of my (amuse) experiment I now have a broken numpy2 causing havoc. TBD.
If you're sure it's an issue with AMUSE, then please make a separate issue with a clear error message. We did have issues with numpy >=2, but those should be fixed now.
This isn't really the best way of using GitHub issues, please use the Slack for chat (as we've been doing) so that we can leave this for tracking problems that we're sure exist and that need to be fixed in AMUSE.