[Guido van Rossum] > > > I don't propose to automate this. I propose this: > > > > > > try: > > > import threading > > > except ImportError: > > > import dummy_threading as threading > > > > > > > So is this an indirect request for me to write ``dumy_threading``? If it > > is it won't be hard: I would do an ``import *`` on ``threading`` and then > > override the functions it uses from ``thread`` with ``import ... from ... > > as ...`` from ``dummy_thread``. Also would mean rewriting the > > ``threading`` testing suite. Prefectly happy to write it, just need you > > to say you want it. > > Yes. I don't want threading to automatically substitute dummy_thread > for thread. Multiple imports of threading must all fail when thread > cannot be imported. > Do you prefer I do a separate ``dummy_threading`` module or follow Martin's suggestions and just turn ``dummy_thread`` into a ``threading`` substitute itself? -Brett
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