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
Once a package has been localised, it can be helpful to know whether or not a resolve contains it, or another package by the same name. Especially if your localised packages are intermixed with your development packages (i.e. REZ_LOCAL_PACKAGES_PATH).
rez env python
resolved by manima@toy, on Wed Jun 26 19:28:58 2019, using Rez v2.32.1
requested packages:
python
~platform==windows (implicit)
~arch==AMD64 (implicit)
~os==windows-10.0.18362 (implicit)
resolved packages:
arch-AMD64 C:\Users\manima\packages\arch\AMD64 (local)
platform-windows C:\Users\manima\packages\platform\windows (local)
python-3.7.3 C:\Users\manima\packages\python\3.7.3\platform-windows\arch-AMD64 (localised)
> $
Implementation
Add a variable to packages as they become localised, e.g. localised = True. The attribute is then not preserved (or even respected) following a rez build of that same package and version. That way, you know whether a package is "original" and simply localised, or a development package. Something you're explicitly build yourself.
The text was updated successfully, but these errors were encountered:
Once a package has been localised, it can be helpful to know whether or not a resolve contains it, or another package by the same name. Especially if your localised packages are intermixed with your development packages (i.e.
REZ_LOCAL_PACKAGES_PATH
).Implementation
Add a variable to packages as they become localised, e.g.
localised = True
. The attribute is then not preserved (or even respected) following arez build
of that same package and version. That way, you know whether a package is "original" and simply localised, or a development package. Something you're explicitly build yourself.The text was updated successfully, but these errors were encountered: