martian.testing FakeModule inconsistency with python behaviour

Bug #482581 reported by chma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grok
New
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?

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.