Message328512
I'm running Python 3.6 on Ubuntu 16.04
I don't know if this should qualify as a bug, but I noticed the following behavior difference in the (contrived?) scenario of directly importing '__init__' from a package:
## Setup ##
mkdir app
echo 'print(f"Executing app/__init__.py as {__name__}")' > app/__init__.py
## Native: executes __init__ *once* ##
python -c 'from app import __init__'
# Output:
# Executing app/__init__.py as app
## Importlib: executes __init__ *twice* ##
python -c "import importlib; importlib.import_module('.__init__', 'app')"
# Output:
# Executing app/__init__.py as app
# Executing app/__init__.py as app.__init__
Note in addition that absolute import (either with importlib or native) executes '__init__' twice. |
|
Date |
User |
Action |
Args |
2018-10-26 05:31:45 | qagren | set | recipients:
+ qagren |
2018-10-26 05:31:45 | qagren | set | messageid: <1540531905.09.0.788709270274.issue35073@psf.upfronthosting.co.za> |
2018-10-26 05:31:45 | qagren | link | issue35073 messages |
2018-10-26 05:31:44 | qagren | create | |
|