As part of the discussions on local name binding, I dug up a patch that I sent to python-ideas back in June 2015. That's two and a half years ago, and was based on CPython 3.5. Here's what happened when I attempted to apply it to the current master branch (3.8): $ patch <~/Downloads/scope_hack.patch -p1 patching file Python/compile.c Hunk #1 succeeded at 100 (offset 3 lines). Hunk #2 succeeded at 134 (offset 3 lines). Hunk #3 succeeded at 793 (offset 2 lines). Hunk #4 succeeded at 2824 (offset 432 lines). Hunk #5 succeeded at 2871 with fuzz 2 (offset 430 lines). Hunk #6 succeeded at 3312 (offset 402 lines). Hunk #7 succeeded at 3330 (offset 402 lines). Hunk #8 succeeded at 5442 with fuzz 1 (offset 831 lines). Hunk #9 succeeded at 5457 with fuzz 2 (offset 832 lines). Hunk #10 succeeded at 5520 with fuzz 2 (offset 823 lines). $ And the build ran fine, the test suite didn't gain any new failures (there's no tests for the new functionality, but it didn't break anything else), and my original demo program worked just fine. Thank you to all the CPython core devs for maintaining code that is THIS stable. Stuff happens but there's no unnecessary code churn. Sure, GNU Patch had to do a bit of work to merge in the changes, but it did it completely automatically. You folks are awesome! ChrisA
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4