[Guido] > Instead of asking us to add more macros, I recommend that you use the > lower-level C API that is used by the macros. There's a bunch of ways > to save and restore the state. The macros are just shortcuts (and a > handy way to make all the code disappear when threads don't exist). [Martin Sjögren] > Well, that's exactly what I'm doing, isn't it? You are using macros, yes <wink>. What Guido is telling you is that the set of macros we already have is adequate for everything we do, so it would just bloat our code base with stuff we never ever test if we were add additional stuff we never use. He's also telling you that you can write your macros in such a way that you don't have to change them across Python releases, and it was *that* complaint you seemed keenest about. That one you can solve on your own.
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