RetroSearch Browse

Mon Oct 28 21:13:36 CET 2013 · https://mail.python.org/pipermail/python-dev/2013-October/129909.html

2013/10/28 Victor Stinner <victor.stinner at gmail.com>:
> Hi,
>
> While working on a fix, I got an assertion error during Python
> finalization because Python tried to import the "io" module whereas
> the module was just unloaded. Python tried to import the io module to
> display a warning and display the Python line where the warning was
> emitted. See the following issue for detail:
> http://bugs.python.org/issue19421
>
> I propose to block importing new modules (or import again unloaded
> modules) during Python finalization to avoid such tricky bugs.
>
> What do you think?

Though the practice of importing during finalization seems dubious,
baning it may be a compatibility problem.

-- 
Regards,
Benjamin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-October/129909.html below:

[Python-Dev] Block module import during Python finalization?