[issue18114] Update PyImport_ImportFrozenModuleObject() to set __package__

2020-03-06 Thread Brett Cannon
Brett Cannon added the comment: Since there's work to drop __package__, closing as "won't fix". -- resolution: -> wont fix stage: needs patch -> resolved status: open -> closed ___ Python tracker __

[issue18114] Update PyImport_ImportFrozenModuleObject() to set __package__

2018-10-26 Thread Brett Cannon
Brett Cannon added the comment: I'm not sure if it's still relevant. :) Feel free to look at the code and come back here with a recommendation as to whether this is still necessary or not. -- ___ Python tracker

[issue18114] Update PyImport_ImportFrozenModuleObject() to set __package__

2018-10-11 Thread Andrei Petre
Andrei Petre added the comment: Hi, is this still relevant? I see the file has changed quite a bit. -- nosy: +andreip ___ Python tracker ___ __

[issue18114] Update PyImport_ImportFrozenModuleObject() to set __package__

2013-06-10 Thread Brett Cannon
Brett Cannon added the comment: Marking as easy for any C coders. -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list maili

[issue18114] Update PyImport_ImportFrozenModuleObject() to set __package__

2013-06-10 Thread Brett Cannon
Brett Cannon added the comment: Forgot that PyImport_ImportFrozenModule() uses PyImport_ImportFrozenModuleObject() and the former is used to load _frozen_importlib, so can't drop the function. The code could still be updated, though, to set __package__ before the code object is executed. That