martian.testing FakeModule inconsistency with python behaviour

Bug #482581 reported by chma on 2009-11-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grok
Undecided
Martijn Faassen

Bug Description

In python when you defina a class a in module m1 and then make an insance b (of class a) in module m2 and then you import m2 the m2.b.__module__ will be set to m1, if you use martian.testing.FakeModule however m2.b.__module__ will be set to m2. Is this behaviour intentional or a bug?

chma (cheaphomemadeacid) wrote :
Changed in grok:
assignee: nobody → Martijn Faassen (faassen)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers