-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Make Base.shell_escape() and Base.shell_split() public #53510
Make Base.shell_escape() and Base.shell_split() public #53510
Conversation
(bump) |
I'm definitely on board with making them public. Should we also export them? |
Hmm to me they're not quite reached-for-often-enough to be worth exporting, but I don't feel very strongly about it. |
Yeah, that's fair. Will discuss next triage call, but that shouldn't block merging this as is. |
triage says public is good. |
Can this be done for the other platform specific shell escapes as well? |
Do you mean these?
|
Yes, exactly. Their docstrings are very in-depth, and I was planning on putting them in the manual in some form so that the docstrings of |
Base.shell_escape() is particularly useful since it's the only way to properly convert a Cmd to a string.
Note that Base.escape_raw_string() is already in the manual so it should be public anyway.
83e0d1a
to
5d89485
Compare
Sure, I guess that makes sense. Made them public in 5d89485, along with |
(bump) |
Base.shell_escape()
is particularly useful since it's the only way (AFAICT) to properly convert aCmd
to a string.