Publish steps to build a pip whl #1846
Replies: 2 comments
-
Thank you for posting this. We reviewed this, and think the recommended way is to use the source code following the pip installation as in the docs. Alternatively, it may be useful to have a docker container with your environment as needed, and volume-mount the Isaac Lab directories as needed. It will give you a way to develop while keeping your setup easy to deploy. |
Beta Was this translation helpful? Give feedback.
-
Thanks for taking a look! The pip install workflow in the docs is fine unless you need to change something about IsaacLab itself: fixing bugs, for example. Since it forces you to use a precompiled wheel, IsaacLab is not itself modifiable unlike in the conda workflows (which are harder to make repeatable). For what it's worth, I was able to replicate the published wheel with very little changing in IsaacLab.
We will probably move forward with this, but it would be better if we were sharing the same infrastructure as the published wheel. |
Beta Was this translation helpful? Give feedback.
-
Looking at the docs for pip installation, it's clear that there is some way to turn the packages from IsaacLab into a single pip-installable wheel. However, I can't find the process to do so. Can this be published as part of this repository?
Our use case is working from a fork of IsaacLab but being able to publish it into Python virtualenvs for other projects.
Beta Was this translation helpful? Give feedback.
All reactions