Rez windows development workflow #1301
-
Yesterday I worked through getting setup for development on Windows using a virtual machine, Python3, virtualenv, and editable installs. I wrote down my experience and I'd like to consider this a good starting point but would like feedback from more seasoned devs. As an added effect, this discussion could be used by beginner and novice developers and enthusiasts as reference to make it easier to dive into tinkering or contributing to rez, until such time as an official "Best Practices" doc comes along. In attempt to frame the conversation a bit more, some questions that might be answered, or open the door to answering, might include:
Some backstory about me:
Note: In anticipation of things changing I created this gist. I'll make any edits to that document, not the original text posted here. My notes (copied from personal wiki): Rez Getting Started
Or, for more consistent path delimiters:
To my knowledge, production install is needed to circumnavigate this warning. See also: Pip-based rez installation detected warning with installation script
Where is the "production install"?
Based on this Slack discussion
export PATH=/c/rez/Scripts/rez:$PATH
export PYTHONPATH=/c/rez/Lib/site-packages:/c/rez/Scripts
rez --version
Referencepip editable installs |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I was just asking about editable pip installed earlier so this post came at a great time. Thank you for explaining it in detail! |
Beta Was this translation helpful? Give feedback.
-
I've given the gist some more TLC after testing the workflow on another Windows machine. As disclosed in the original post, the above documentation is out now out of date but will remain for posterity. The original idea was to get some feedback from the community at the time of creating this discussion. Anyone reading this should refer to the gist for the latest information. |
Beta Was this translation helpful? Give feedback.
I've given the gist some more TLC after testing the workflow on another Windows machine. As disclosed in the original post, the above documentation is out now out of date but will remain for posterity. The original idea was to get some feedback from the community at the time of creating this discussion. Anyone reading this should refer to the gist for the latest information.