-
Notifications
You must be signed in to change notification settings - Fork 337
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
Support for keyword arguments in rez-python
#492
Comments
I think it would be possible to update the command to handle that without breaking backwards compatibility. Right now, it's ignoring arguments from the other argument groups (seperated by
|
Yeah this has been on my backlog for some time.. I don't see a problem
passing the non-rez args directly to rez-python.
…On Sat, Mar 3, 2018 at 5:30 AM, Brendan Abel ***@***.***> wrote:
I think it would be possible to update the command to handle that without
breaking backwards compatibility. Right now, it's ignoring arguments from
the other argument groups (seperated by ---), but really, those should
just be passed to python unprocessed.
rez-python [REZ ARGS] -- /path/to/script.py arg1 arg2 --keywords -f --debug
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#492 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABjqSvUDXieNWRAuaOlBnkL_9u4hVg9Iks5taY_NgaJpZM4SaRjT>
.
|
I was actually hoping for I can write my own script for that though. My use cases might not match up with the normal use case for rez-python. |
@swallitsch I think I can support passthru args here, looking into it shortly. |
Addressed by #523 |
Looking at how rez-python is implemented, this looks like a difficult request, but I'll ask it anyway.
Right now
rez-python
only supports positional arguments- no flags or kwargs.So,
rez-python ./scriptname /path/to/file/1 /path/to/file2
works, butrez-python ./scriptname -i --sequence baz --shot 100
will not, because rez tries to eat the flags and kwargs, then errors out when it doesn't understand them.I feel like it'd be a neat addition, because it would allow people to place
#!/usr/bin/env rez-python
as a script shebang line, and have it behave exactly as if you called the script withrez-env rez -c "{sys.argv}"
, which is how I initially expected rez-python to behave.The text was updated successfully, but these errors were encountered: