You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
1what's the source for all thisvks– vks2017年07月20日 06:08:49 +00:00Commented Jul 20, 2017 at 6:08
-
This is the case. Say, a.py import library X and monkey patches X. Then, b.py imports a.py. At this point, X is not directly visible to b.py. After that b.py imports X. Python won't import the same thing twice, so it goes on and uses the X patched in a.py for b.py instead of importing a new copy of X for b.py. That is why b.py only gets the patched X, but not the original X.hamster on wheels– hamster on wheels2017年07月20日 06:18:30 +00:00Commented Jul 20, 2017 at 6:18
-
@vks You shouldn't accept an answer which shows no effort at answering your questions. Blind copy paste is tantamount to plagiarism and must be frowned upon.coldspeed95– coldspeed952017年08月18日 14:09:34 +00:00Commented Aug 18, 2017 at 14:09
-
@cᴏʟᴅsᴘᴇᴇᴅ while you may be correct,I also had an aspect to look upon wherein I was stuck with this and somebody got me outta it.... So had no option but to accept this :)vks– vks2017年08月24日 05:19:26 +00:00Commented Aug 24, 2017 at 5:19
lang-py