-
Notifications
You must be signed in to change notification settings - Fork 178
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
Adding pixi export command #800
Comments
Hi @guru-desh agreed that this feature would be useful. |
We're currently working on the opposite function where you can import an The translation to |
We would be open to adding this to pixi but won't have the capacity to pick this up anytime soon. We welcome PRs! |
Adds an export command group, and a subcommand for exporting in Conda environment.yml files. Currently it just exports the direct dependency names, but I could see adding flags to include all locked dependencies. It also currently does not export the versions, but that could also be a flag to select if it should export the specs as in the manifest, or as locked. works on prefix-dev#800
I find this feature especially important for backwards compatibility reasons: our cluster is running RHEL 8, and pixi requires newer kernel versions. My intended workaround would be to export data from pixi and use something like a conda lock. |
@akhmerov -- You might find the following which I wrote as a prototype useful: https://github.com/synapticarbors/pixi2ces I'm hoping to contribute some version of it part to |
@akhmerov I'm on Oracle Linux Server 8 and this satisfies Pixi
is it different in RHEL? |
@synapticarbors thank you for the pointer! @liquidcarbon 🤯 indeed, overriding system requirements seems to work. I wonder, though, whether something would explode later down the line. Where can I find more information? |
My main prod stuff is still under poetry, so can't say with full confidence it'll be fine, but I don't see why not |
Ah, it was my misunderstanding of the error message. It's not that pixi itself requires recent kernel and libc, but rather that it has default virtual package requirements for those. In that case my remark should be disregarded because exporting to conda environment, wouldn't change the virtual package requirements. Apologies for the noise. |
The Closing this issue as it can now be implemented. |
Problem description
It would be super awesome if pixi had an option to export the dependencies from the pixi.toml file to a conda environment .yaml file. It would work similar to how poetry export is able to export the dependencies from the pyproject.toml file into a requirements.txt.
There are valid use cases for this, and I have one. I'm a Head Teaching Assistant for the Machine Learning course at Georgia Tech. I found pixi pretty recently since pixi is one of the best package managers for managing regular, host, and build dependencies especially for anaconda environments (which we use extensively in our course assignments). Currently, we're using conda + poetry, which requires maintaining both a conda environment and a poetry environment, which is clunky for us.
An export feature in pixi would allow us to use pixi for managing all our dependencies and allowing us to easily export the conda environment files for all the platforms we support with full confidence that students won't run into issues.
Thank you guys so much for solving a VERY known problem in the python world. I really love this work, and I'm planning on using pixi extensively in the future.
The text was updated successfully, but these errors were encountered: