Whenever you enter an environment with Rez by default it shows a log of the resolved environment. For example:
C:\>rez env maya python bleeding_rez
You are now in a rez-configured environment.
resolved by Roy@CB1, on Tue Oct 29 12:22:49 2019, using Rez v2.40.3
requested packages:
maya
python
bleeding_rez
~platform==windows (implicit)
~arch==AMD64 (implicit)
~os==windows-10 (implicit)
resolved packages:
arch-AMD64 C:\Users\Roy\packages\arch\AMD64 (local)
bleeding_rez-2.40.3 C:\Users\Roy\packages\bleeding_rez\2.40.3 (local)
maya-2019 C:\Users\Roy\packages\maya\2019 (local)
platform-windows C:\Users\Roy\packages\platform\windows (local)
python-3.7.3 C:\Users\Roy\packages\python\3.7.3\platform-windows\arch-AMD64 (local)
However when not having access to a Python interpreter or bleeding-rez inside the resolved environment this message will be missing. As such you will be left clueless as to what the resolved environment actually looks like unless you start debugging it manually, which could be quite involved when inside the environment (if even possible).
What I expected
It should allow entering any environment and log the message, for example rez env maya should still be capable of displaying it even without requiring these additional dependencies to be loaded into the child environment.
Current workaround
You can manually pass along bleeding-rez and the python interpreter as packages making the message show fine (as shown above). However this can also be automated with --self - this shouldn't be a production example but could be simpler than passing along a package for python and bleeding-rez manually.
rez env maya --self
This should pass along Python and bleeding-rez as a package.
Tested with bleeding_rez-2.40.3 and python-3.7.3 on Windows 10.
Issue
Whenever you enter an environment with Rez by default it shows a log of the resolved environment. For example:
However when not having access to a Python interpreter or
bleeding-rezinside the resolved environment this message will be missing. As such you will be left clueless as to what the resolved environment actually looks like unless you start debugging it manually, which could be quite involved when inside the environment (if even possible).What I expected
It should allow entering any environment and log the message, for example
rez env mayashould still be capable of displaying it even without requiring these additional dependencies to be loaded into the child environment.Current workaround
You can manually pass along
bleeding-rezand thepythoninterpreter as packages making the message show fine (as shown above). However this can also be automated with--self- this shouldn't be a production example but could be simpler than passing along a package forpythonandbleeding-rezmanually.This should pass along Python and bleeding-rez as a package.
Tested with
bleeding_rez-2.40.3andpython-3.7.3on Windows 10.Reference