-
-
Notifications
You must be signed in to change notification settings - Fork 258
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
How to use --pex-args in bdist_pex #233
Comments
Try |
@jsirois, thanks for responsing to my question so quickly! Are you suggesting that I look at the variables as an alternative to passing in the values through the command line? The one I'm after is a variable that's equivalent to --python-shebang. This command prints out a lovely list of variables:
So one might conclude that any argument or option that follows --pex-args gets captured by the pex command (instead of being treated a setup-tools argument), however that would imply the following command should work:
|
Turns out |
Fix is in @ 2fc3f73 |
Other pex args also fail when passed via pex-args, including It looks like these are all being parsed as requirements instead of options. I'm running a clone from master which includes this fix. |
@pikeas - mind filing a seperate issue? I don't replicate your experience with a quick test:
|
I read too quickly, you mention what looks like an ini-file section of some sort ( |
I'm trying to use bdist_pex. I want to ensure that I use a different Python for the shebang. I can tell that this syntax is not working. Please could you point me to the correct usage of --pex-args?
The text was updated successfully, but these errors were encountered: