fix: Prevent backslashes in descriptions from breaking docstrings [#735]. Thanks @robertschweizer & @bryan-hunt!

[robertschweizer]

We ran into Python parsing errors because we used backslashes in some description strings.

[bryan-hunt]

+1

I just encountered this issue consuming a published API and was going to submit the same patch.

Here is an example definition that triggers the issue: Modified Petstore

[codecov]

Codecov Report

Merging #735 (5ef1281) into main (302cd02) will not change coverage.
The diff coverage is n/a.

❗ Current head 5ef1281 differs from pull request most recent head 139c186. Consider uploading reports for the commit 139c186 to get more accurate results

@@            Coverage Diff            @@
##              main      #735   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           49        49           
  Lines         1971      1971           
=========================================
  Hits          1971      1971           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[dbanty]

Thanks for this, I did tweak it so that the diffs will be smaller for folks updating. PEP 257 seems to indicate that a docstring containing a \ is the only case where the r prefix is necessary. If there are more edge cases we may need to go back to all-raw docstrings, but I figure I should try to reduce diffs for folks.