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
we are currently struggling with installing custom Python packages that are not provided by PyPI using the gears-cli. We use install-requirements, export-requirements and import-requirements in a Docker multi-stage build in order provide an image with preinstalled Python packages.
Currently, it seems that entries (lines) in the requirements.txt file are treated as strings and it is not possible to use --extra-index-url in order to specify an alternative package index or to provide a path.
Did we miss something or are there any workarounds?
Are there any plans for allowing alternative Python package indexes (e.g. a GitLab package index) or specifying paths?
Thanks a lot for all of your support and your great work!
The text was updated successfully, but these errors were encountered:
Hey @dsmanl , sorry for the late reply, we are planning to allow much more options in the future but currently, as a workaround, it is possible to install from a local path (assuming Redis has access to this path). Just put this path in the requirement.txt (full path) and if Redis has access to it then it will be installed from there. Then you can export and import this requirement (notice that the requirement name will be the full path you give). I know it's not perfect, hope it will do for now, let me know if you need any help with this.
Dear all,
we are currently struggling with installing custom Python packages that are not provided by PyPI using the
gears-cli
. We useinstall-requirements
,export-requirements
andimport-requirements
in a Docker multi-stage build in order provide an image with preinstalled Python packages.Currently, it seems that entries (lines) in the
requirements.txt
file are treated as strings and it is not possible to use--extra-index-url
in order to specify an alternative package index or to provide a path.Did we miss something or are there any workarounds?
Are there any plans for allowing alternative Python package indexes (e.g. a GitLab package index) or specifying paths?
Thanks a lot for all of your support and your great work!
The text was updated successfully, but these errors were encountered: