Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #70716 > unrolled thread

where to put global testing value

Back to article view | Back to comp.lang.python

Contents

  where to put global testing value Robin Becker <robin@reportlab.com> - 2014-04-29 17:17 +0100

#70716 — where to put global testing value

A user complains that under AppEngine I'm not allowed to import __main__.

I can fix this issue merely by putting a try block around the offending import 
which is only used like this


import __main__
testing = getattr(__main__,'_rl_testing',False)
del __main__

this is only used as a hack way, during testing, to modify the behaviour of the 
importing module (a proxy for a C extension). During testing we keep both the C 
version and the supposed replacement of various functions so they can be tested 
against each other

https://bitbucket.org/rptlab/reportlab/src/default/src/reportlab/lib/rl_accel.py

Is there a more reasonable way to allow changes to module level globals before 
the import takes place? I guess since this module is supposed only to be 
imported by reportlab we can put this sort of thing onto the reportlab module 
itself, but that could possibly lead to import loops.

Any ideas?
-- 
Robin Becker

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web