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
Add the ability to force shlex.quote to always return an escaped / quoted string, avoiding the expensive regex-ing of a straggly set of characters (currently r'[^\w@%+=:,./-]') .
Different shells have slightly different sets of special characters, eg sometimes including #, sometimes not. To quell one's pedantic paranoia of strings being incorrectly escaped due to an incomplete regex check, we extend the signature of shlex.quote in a perfectly backwards compatible way which skips the regex and goes straight to the escaping.
Changes shlex.quote's signature from
defquote(s):
to
defquote(s, always=False):
always is of bool type, and by default is False, which produces the existing behaviour of the function.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Feature or enhancement
Proposal:
Add the ability to force
shlex.quote
to always return an escaped / quoted string, avoiding the expensive regex-ing of a straggly set of characters (currentlyr'[^\w@%+=:,./-]'
) .Different shells have slightly different sets of special characters, eg sometimes including
#
, sometimes not. To quell one's pedantic paranoia of strings being incorrectly escaped due to an incomplete regex check, we extend the signature of shlex.quote in a perfectly backwards compatible way which skips the regex and goes straight to the escaping.Changes
shlex.quote
's signature fromto
always
is ofbool
type, and by default isFalse
, which produces the existing behaviour of the function.Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Linked PRs
shlex.quote
#119674The text was updated successfully, but these errors were encountered: