Cannot import twisted (all dynamically-generated modules?)

[brad103]

Hey, great tool, thanks.

The code I wanted to acceptance test uses the twisted libraries. Whenever I included 'import twisted' in a fixture, the execution would immediately end. The interpreter I had set in my path could import twisted fine.

To get around it, I had to hack the ExecutionContext class and comment out:
<code>
__builtin__.__import__ = self._import
</code>
for it to work. So it is something in this process of isolating the execution environments that means twisted can't be imported. I can't see why.

I only have a single test page for now which is running fine like this, but I imagine I might start experiencing environmental issues with more tests in a suite without your isolation logic?

----
As a side note, I used buildout to grab waferslim for a py2.6 project, and it generated a 2.6 egg but with py3 code! I had to grab the 2.5 waferslim code and make an egg myself. Does there need to be a second project (waferslim2) to enable setuptools to not just grab the latest trunk version? (I'm pretty new to the cheeseshop)

[tim b (prime8)]

Have worked on this and believe it is fixed with the other changes made for the 1.0 release