Apologies for the double send, apparently Thunderbird got confused when going through a 4G dead zone.
I should mention that I'm aware that any module that previously imported the stdlib version would retain that version rather than a reference to the new one, but I'm okay with that as this is a very specific use case: Having imports across tests and package modules use httplib3 to facilitate merging changes back upstream. On 2015-01-14 8:32 AM, Demian Brecht wrote: > Hi all, > > As part of the work I'm doing on httplib3 (now that I've actually gotten > a bit of time), one of the things I'm trying to get done is injection of > httplib3 over http in order to not have to modify all import paths in > modules and such. Here's the gist of what I have so far: > https://gist.github.com/demianbrecht/bc6530a40718e4fcbf90. > > It's greatly simplified over importlib2's inject mechanism, but I'm > assuming that's largely due to requirements of that package (i.e. Python > 2) in contrast to this one. > > My question is: Does this look sane? Is there anything that I might be > not accounting for? It /does/ seem to work as expected when running > tests, but I'm curious if there's anything that I might be missing that > might jump out at someone more intimately familiar with the mechanics of > importlib. > > Thanks, > Demian > >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com