You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would help if we can, for some existing simple poetry project(s), manually create a suitable meta.yaml and verify that it does create a valid conda package. (In cph format and/or use cph -transmute for other formats?) Maybe start with a very simple one like https://github.com/hackersandslackers/python-poetry-tutorial and then start trying more complex. If someone creates a fork to add ability to create meta.yaml link to it here and we can help with it. Especially the tests ;-)
Also want to say the README.md with comic mirrors my own experiences where I began to understand homebrew/linuxbrew is not a good idea for development, at least not without one of the env managers, which opens a can of worms. Ended up with conda, and remembering to always try conda install foobar before pip install foobar (especially since pip search foo no longer works!) And mamba as a drop-in replacement for conda really speeds things up. (There even is a micromamba mostly intended for making small containers like docker.)
Is it worthwhile making a fork to request a hint to checkout mamba to speed things up be added to the README?
The README also has a typo "buy" should be "but" btw.
It would be nice to generate a
meta.yaml
file to generate conda package withconda build
(https://docs.conda.io/projects/conda-build/en/latest/user-guide/tutorials/build-pkgs.html)The text was updated successfully, but these errors were encountered: