-
Notifications
You must be signed in to change notification settings - Fork 19
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
Different operating systems are not compatible #54
Comments
Why can't the YAML files generated on Windows be used directly on Linux? Even if you remove the "build" information and only keep the library names and version numbers, some dependencies still fail to download, indicating that these libraries are not found. |
Some Linux or MacOS-specific libraries simply don't exist on Windows; you can't replicate the whole dependency tree on different OS. Even between MacOS and Linux, many dependencies are shared, but not all. But you probably don't need or want to replicate the full dependency tree of your project. If you praise portability, it is safer to annotate what your actual top-level dependencies are and leave For instance, the most basic example, an environment that just have Python version 3.12 installed will use different dependencies between OS flavors: Windowsmicromamba repoquery -c nodefaults -c conda-forge --platform win-64 depends python==3.12.5 Output:
Linuxmicromamba repoquery -c nodefaults -c conda-forge --platform linux-64 depends python==3.12.5 Output:
|
Exporting a virtual environment's yaml with micromamba on Windows cannot be used directly on Linux.
The text was updated successfully, but these errors were encountered: