[Python-Dev] Choosing a best practice solution for Python/extension modules (original) (raw)
Brett Cannon brett at python.org
Mon Feb 23 23:12:06 CET 2009
- Previous message: [Python-Dev] Choosing a best practice solution for Python/extension modules
- Next message: [Python-Dev] Choosing a best practice solution for Python/extension modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Feb 23, 2009 at 13:23, Nick Coghlan <ncoghlan at gmail.com> wrote:
Brett Cannon wrote: > Well, neither do I as your proposed approach below is what I do for > warnings.
It's possible I actually had testwarnings.py open in another window while writing that example function... ;) As Steven said, your concerns are precisely why I'm suggesting hiding this in a helper function - so people that aren't quite as comfortable playing games with sys.modules can still use it to suppress particular extension modules when writing tests. Initially for the Python regression test suite only, but perhaps eventually in importlib if we're happy with the way it works out for us.
Sounds like a plan.
Created http://bugs.python.org/issue5354 and assigned it to myself so we don't forget about it.
If we do end up going with this approach I am willing to help out with moving the standard library over.
-Brett -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20090223/857dbd1e/attachment.htm>
- Previous message: [Python-Dev] Choosing a best practice solution for Python/extension modules
- Next message: [Python-Dev] Choosing a best practice solution for Python/extension modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]