| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks!
Sorry, something went wrong.
|
Hmm I also have a hunch that this might be worth calling out in What's New. Nvm it's already there, great job 🚀 |
Sorry, something went wrong.
|
Looks ready (for review again?) to me 😎 |
Sorry, something went wrong.
There was a problem hiding this comment.
Sorry, something went wrong.
There was a problem hiding this comment.
Minor tweaks but please add more tets with quotes inside.
Sorry, something went wrong.
|
Please avoid force-pushing. It's extremely hard to make reviews otherwise. |
Sorry, something went wrong.
|
Sorry for the force pushes but the 'commit suggestions' commits on GitHub came through as CRLF formatted instead of LF. I don't know if that's a GitHub Microsoft issue, or your IDE settings, or I need to git config autocrlf but hey I got there in the end. $ git log d000ccd...e3d9b05 is what has changed, addressing the review. The only change I disagreed with is the wording of the .. versionadded. The existing one seems to be worded more similarly to the others. |
Sorry, something went wrong.
|
I think it's a GH issue because other reviews had the same issue... |
Sorry, something went wrong.
|
Ready |
Sorry, something went wrong.
|
@picnixz 30 day courtesy ping 👀 |
Sorry, something went wrong.
There are propositions to add a single-quote-double-quote switch (pythongh-90630), so to avoid hiccups of people passing `force` as a positional and it being used for the single-double switch, we make kwargs kwargs-only.
Test special cases of strings that don't need quoting, do need quoting, do use `force`, don't use `force` etc. I've tried to be exhaustive.
…to `shlex.force`
Co-authored-by: Bartosz Sławecki <bartosz@ilikepython.com>
The comments for why these tests exist can always be found in the git history Co-authored-by: Bartosz Sławecki <bartosz@ilikepython.com>
Missed from last commit
Intended for another branch shlex-quote-typeerror Co-authored-by: Bartosz Sławecki <bartosz@ilikepython.com>
…view Show off the default behavior as `force=False`
Try not to use don't and we're and should've etc apostrophes.
Add test to ensure string with single quote inside it (without which the string wouldn't need quoting) is quoted even though `force=False`.
Documentation build overview161 files changed · + 5 added · ± 156 modified + Added
± Modified |
Sorry, something went wrong.
|
Really sorry for the rebase ffs, worst PR ever! 😭 |
Sorry, something went wrong.
@johnslavik's review has been addressed.
|
Merged. Thanks for your contribution. |
Sorry, something went wrong.
…ython#148846) There are propositions to add a single-quote-double-quote switch (pythongh-90630), so to avoid hiccups of people passing `force` as a positional and it being used for the single-double switch, we make kwargs kwargs-only. Co-authored-by: Bartosz Sławecki <bartosz@ilikepython.com>
| Back | FazBrowse Home | New Git URL |
Closes #119670
Supersedes my out-of-date PR #119674
We use force instead of always as a word more consistent with other programming jargon (like in rm -f the f is for 'force') as discussed
Commits
As mentioned I'm also going to open an issue a discussion thread about shlex.quote returning "''" for falsey non-str data. This PR and that discussion seem independent of each other, that is this PR doesn't need to be held back until that discussion is addressed.
📚 Documentation preview 📚: https://cpython-previews--148846.org.readthedocs.build/