-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
Availability on Conda Repo #144
Comments
Also, I cannot publish my package on conda-forge due to the its dependency on Gekko, since Gekko is not yet on conda-forge. Could someone please kindly look into this... Thanks a lot! https://github.com/conda-forge/staged-recipes/runs/6348196472 |
There are no immediate plans to publish Gekko on conda-forge. YAML can handle both capturing and reinstalling Pip-installed packages with:
you can recreate with pip dependencies on another platform:
Most eveything that is on I added this to the list of future enhancements. |
Tried the
A work-around is to use |
@APMonitor try to use My experience with My package is already on pypi. The reason why I need to put this on conda-forge is because we use a cloud platform which the virtual machine instance is built based on conda and the jupyter notebook running on it is not working with packages installed using pip install. Also, having it on conda also make many data scientists' life easier. Thanks a lot for these extra work. |
I submitted the forked staged-recipes for review with the |
@APMonitor Thanks a lot for supporting! Once your is approve, I can submit mine too. Cheers! |
@APMonitor by the way, I think you forgot to submit the pull request... you have to submit a pull request in order for them to accept it. |
Thanks for the reminder. It looks like it is failing on some of the checks: conda-forge/staged-recipes#18925 The error looks non-descriptive:
Any ideas? |
Digging into the logs, it appears that the
I need to update that binary (out of date). |
I think something related to MacOS dependency, if you look at the error log, it says: The check passes on MacOS, but failed on Linux. |
@APMonitor Perhaps, you can try to ping @conda-forge/staged-recipes @conda-forge/core on the PR if you cannot figure it out. I tried to look it up online, but no luck so far. |
I released a new version of Gekko
Here is some information on that error code: https://docs.microsoft.com/en-us/answers/questions/379441/error-code-34exited-with-code-107374181934.html
Maybe getting closer... |
Their documentation mentions that I should wait a few days before reaching out with a ping to their developer group. I tried setting |
I just found this for Gekko 1.0.0: https://anaconda.org/Bjrn/gekko for |
Unfortunately not, my package is required to be on |
Thanks - I added a reply. The biggest problem seems to be with the bin folder |
Hi! Can you please update me on what is the status of GEKKO in conda? Is it available there officially? Is there any way |
We were never able to get past the restrictions with distributing the compute binaries (not allowed with conda). Here is some help on installing with conda from a GitHub repo: https://stackoverflow.com/questions/19042389/conda-installing-upgrading-directly-from-github The GitHub repo for Gekko is https://github.com/BYU-PRISM/GEKKO so something like this may work:
Here is an alternate way to install from a GitHub package: matterport/Mask_RCNN#699 |
Is it possible to make Gekko available on Conda repository (eg. conda-forge)? I am using Gekko in one of my package, and I wanted to include a environment.yml for default packages dependency for conda environment.
The text was updated successfully, but these errors were encountered: