method to escape gitwildmatch #26
Comments
|
@MrOutis That would be a useful addition. I'm interested in a PR. |
|
Cool, @cpburnz ! I'll be submitting a patch for it (a very basic one, but at least to start the conversation) |
ghost
mentioned this issue
bors bot
added a commit
to rehandalal/therapist
that referenced
this issue
Oct 4, 2019
95: Update pathspec to 0.6.0 r=rehandalal a=pyup-bot This PR updates [pathspec](https://pypi.org/project/pathspec) from **0.5.9** to **0.6.0**. <details> <summary>Changelog</summary> ### 0.6.0 ``` ------------------ - `Issue 24`_: Drop support for Python 2.6, 3.2, and 3.3. - `Issue 25`_: Update README.rst. - `Issue 26`_: Method to escape gitwildmatch. .. _`Issue 24`: cpburnz/python-pathspec#24 .. _`Issue 25`: cpburnz/python-pathspec#25 .. _`Issue 26`: cpburnz/python-pathspec#26 ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/pathspec - Changelog: https://pyup.io/changelogs/pathspec/ - Repo: https://github.com/cpburnz/python-path-specification </details> Co-authored-by: pyup-bot <github-bot@pyup.io>
clrpackages
pushed a commit
to clearlinux-pkgs/pathspec
that referenced
this issue
Oct 7, 2019
…0.6.0 0.6.0 (2019-10-03) ------------------ - `Issue #24`_: Drop support for Python 2.6, 3.2, and 3.3. - `Issue #25`_: Update README.rst. - `Issue #26`_: Method to escape gitwildmatch. .. _`Issue #24`: cpburnz/python-pathspec#24 .. _`Issue #25`: cpburnz/python-pathspec#25 .. _`Issue #26`: cpburnz/python-pathspec#26
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great to have a method for escaping a string according to gitwildmatch, thus, putting backslashes before
!,[,],?*.I could send a PR if there's interest on this
The text was updated successfully, but these errors were encountered: