-
Notifications
You must be signed in to change notification settings - Fork 1.9k
csh and path() Context Manager #1300
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
Comments
Forgot to mention I'm on Python 2.7.9, Fabric 1.10.1. |
It looks like something somewhere is over-quoting the path string. In the "Executed" line, we see: [...] export PATH="$PATH:"[...]"" [...] i.e. we're opening quotes before $PATH, then opening again after the : (causing csh to complain) and then closing both sets at the end. |
csh behaviour with quoting and backslashes is strange. I had similar problems and found a fix: You need to set backslash_quote in csh. See pull request #1483. Feedback welcome. |
Please comment if the setting from #1483 is insufficient and we can reopen - thanks! (Though - I'll note that Fabric 1's aggressively "helpful" autoquoting is generally problematic and won't be present by default in 2.x.) |
Still getting the same error. However I'm not currently using path() so I'm fine with leaving it this way and eventually retesting on 2.x. |
Hi,
the path context manager seems to fail when trying to append path on FreeBSD/csh containing unescaped characters like
$
,~
and.
. It also seems to add unneeded extra quotes.E.g., with bower installed locally:
fab staging deploy
returns
also
export
is probably not working anyway in csh, should besetenv
I think.The text was updated successfully, but these errors were encountered: