-
-
Notifications
You must be signed in to change notification settings - Fork 423
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
ENH: Would you consider making q available through conda? #322
Comments
Hi @Sann5 sorry for missing this message, just saw it now, crazy times. Adding q to conda would be great. I'm not sure about the specifics though, so I'd really appreciate it if you can do it and link this repo and the q site if possible. Would be great if you can send me the PR that you create for doing it, so i can understand a bit about the process and the concept. Harel |
@harelba should I sign you up as one of the maintainers of the conda-forge recipe (a GitHub repo that will be in charge of publishing q in conda)? Or someone else? There will be SPAM from conda-forge. I will also sign up as a maintainer for the time being. |
No need to sign me up as a maintainer for now. Once you get tired from being a maintainer, please ping me and I'll take over as needed. Can you please send me the relevant PR for conda-forge, so i can take a quick look at it? |
For sure. I'll ping you when the PR is pending for review. |
@Sann5 Sorry for the delayed responses, too many things in parallel, and times are a bit crazy. My knowledge regarding python packaging structure is limited, I really appreciate your effort on this. |
I would like to use q in a cluster environment. However, the cluster does not support brew but it supports conda (there are ways of making q work but it's a dirty solution). I believe the process of building a package and making it available in conda is relatively uncomplicated. Would you consider doing so? I could also do it and link this repo for credits if that is something you would be okay with.
Thanks for the great tool! Cheers!
The text was updated successfully, but these errors were encountered: