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
Resolve invalid escape sequence warnings #507
base: master
Are you sure you want to change the base?
Resolve invalid escape sequence warnings #507
Conversation
This fix is needed and long due. |
Thanks for supporting this PR, @PaulSvensson! I've not contributed to |
The last release of this package was in 2014, so it looks like it's no longer maintained at all |
Dear @keleshev, @mboersma, and @graingert, does one of you have the powers to integrate this patch and run a new release? It would be so sweet! With kind regards, |
AFAIK these were fixed in 2018 in #435 but it was never merged or released. |
Hi again. Shall we do something about this package for those who still need it, like maintenance, hereby asking for permission? @bob-schumaker also submitted a similar patch at GH-523, right? Also pinging the authors and most recent committers, @keleshev, @yb66, @mboersma, @graingert about it. Thank you very much in advance. 🙏 |
See @Sylvain303's answer at #519 (comment): There is docopt-ng now, maintained by @jazzband. Cheers, @itdaniher, @johnscillieri, @nyurik, @hugovk, @jezdez, @NickCrews, @sturmianseq, and @h4l. 💙 |
Maybe someone has the powers to update the README with a prominent admonition at the top to refer to docopt-ng, and after that, press the "Archive Repository" button? |
Simple change to prefix any regular expression matching strings with
r
to ensure they are used as raw strings and do not throw an invalid escape sequence warning: