-
Notifications
You must be signed in to change notification settings - Fork 40
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
Installing latest ipython release (8.24.0) causes conda validation error: 'emscripten' is not a valid Platform #927
Comments
Pinging @DerThorsten because I see that you've been working on the ipython recipe lately. Do you have any insight? |
the plattform was renamed to |
I believe everything I'm using is up to date, and I see |
can you try to use micromamba instead of conda. With micromamba you can just specify |
a
actually, the issue is in the rattler-build which writes the wrong platform to the packages. |
Terrific! Thanks so much @DerThorsten! |
Hi all,
First off, thank you so much for all your work. We're using emscripten-forge in combination with voici with great success.
In the last week or two my voici builds started to fail with the error message below after the following command is executed (inside voici build).
After this error, all of my
conda install
andconda create
commands start to fail (even in different environments). I tried reinstalling conda as well as updating to the latest version of conda (24.4 as of writing).Troubleshooting
I added a print line at
package_cache_data.py:123
(which isself._make_single_record(base_name)
according to the traceback above) and found that this validation error is triggered whenbase_name="ipython-8.24.0-py311h43c7e2a_1"
. That made me think that perhaps the latest emscripten-forge release of ipython is buggy so I tried pinning ipython to 8.23.0 and that fixed the issue.TLDR: Installing ipython 8.24.0 causes
conda.auxlib.exceptions.ValidationError: 'emscripten' is not a valid Platform
. Installing ipython 8.23.0 works ok.Thanks in advance.
The text was updated successfully, but these errors were encountered: