This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author cjw296
Recipients cjw296, dino.viehland, xtreak
Date 2020-02-06.18:55:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1581015301.37.0.414718126016.issue39551@roundup.psfhosted.org>
In-reply-to
Content
Apologies, but I'm still not sure what "the modules are published" means?
"publish "x" as a child onto the package" also doesn't mean much to me, I'm afraid. Are you aware of any importlib docs or some such which might be able to explain this to me?

When "It can still have normal Python modules as a child which aren't immutable", what happens when you try to patch the immutable module? What happens if you try to patch the mutable module below it?

When "the assignment is ignored with a warning.", what is doing that ignoring?

Unless I'm missing something, this feels like such an edge case I'm not sure mock.patch should be trying to support it. Should this be something that is handled by your immutable import thing?
History
Date User Action Args
2020-02-06 18:55:01cjw296setrecipients: + cjw296, dino.viehland, xtreak
2020-02-06 18:55:01cjw296setmessageid: <1581015301.37.0.414718126016.issue39551@roundup.psfhosted.org>
2020-02-06 18:55:01cjw296linkissue39551 messages
2020-02-06 18:55:01cjw296create