Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rez bind behavior change and possible break on Windows #340

Open
yawpitch opened this issue Aug 16, 2016 · 0 comments
Open

rez bind behavior change and possible break on Windows #340

yawpitch opened this issue Aug 16, 2016 · 0 comments
Labels
bug rez-bind rez-bind related issues

Comments

@yawpitch
Copy link

yawpitch commented Aug 16, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug rez-bind rez-bind related issues
Projects
None yet
Development

No branches or pull requests

2 participants