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
The addition of the --no-deps option to "rez bind" has substantially changed the default behavior of that command: whereas in prior versions dependencies were not installed, now you're installing them by default.
In and of itself not a problem, however in many Windows domains (including ours) os.symlink will fail on machines by default (the user is NOT granted permissions to make a symlink without running the mklnk command in a shell that has elevated Administrator privileges -- similar to sudo, but with all the usual half-assery of Windows), which leads to "rez bind rez" failing with all sorts of interesting messages when it automatically attempts to bind the system Python as a dependency.
Internally we NEVER want to bind the system Python (it's potentially very different on every machine), so this new default tripped us up, but I don't think it's really a problem, just an opportunity for some better documentation.
M
The text was updated successfully, but these errors were encountered:
Hey Allan,
The addition of the --no-deps option to "rez bind" has substantially changed the default behavior of that command: whereas in prior versions dependencies were not installed, now you're installing them by default.
In and of itself not a problem, however in many Windows domains (including ours) os.symlink will fail on machines by default (the user is NOT granted permissions to make a symlink without running the mklnk command in a shell that has elevated Administrator privileges -- similar to sudo, but with all the usual half-assery of Windows), which leads to "rez bind rez" failing with all sorts of interesting messages when it automatically attempts to bind the system Python as a dependency.
Internally we NEVER want to bind the system Python (it's potentially very different on every machine), so this new default tripped us up, but I don't think it's really a problem, just an opportunity for some better documentation.
M
The text was updated successfully, but these errors were encountered: