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
conda-forge support? #1994
Comments
What's the motivation? Conda supports PyPI out of the box: https://docs.anaconda.com/anacondaorg/user-guide/tasks/work-with-packages/#using-package-managers |
@orsinium Thanks for your reply. The motivation is that for a conda-forge package to work, all its dependencies must be on conda-forge as well. |
@orsinium Sorry I was not clear enough. Indeed, on your local machine that works fine. My point was that if you want to contribute a package to conda-forge (so people can install it using Reference: https://conda-forge.org/docs/maintainer/adding_pkgs.html#avoid-external-dependencies
|
@ma-sadeghi this would be really hard to make! Because, |
Sure, the question is why one would need it in conda if WPS already can be installed in conda environment using pip? There is not much difference to type |
@orsinium Because you can explicitly include C/Fortran dependencies if you ship your package in conda, and not in pip. |
Sure, I know why one needs conda 👍🏿 However, WPS doesn't have any C-dependencies, so you can deploy in 2 commands:
What do you use for deployment? Ansible, Docker, Taskfile, Makefile? In any case, one more command isn't a big deal. Even if WPS would come into Anaconda Cloud, there are tons of good flake8 extension that aren't on PyPI but deserve giving it a try, and so you still will need pip-based installation for them. |
@orsinium Fair enough and agreed :) |
No description provided.
The text was updated successfully, but these errors were encountered: