Quentin Agren added the comment:
Sorry for the misunderstanding, and thanks for clarifying!
So essentially what I am getting by `from app import __init__` is the
`__init__` method of the module object bound to the name `app`.
However if I have a submodule `app/myapp.py`, `from app import
New submission from Quentin Agren :
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 ##
mkd
Change by Quentin Agren :
--
keywords: +patch
pull_requests: +9340
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35024>
___
___
Py
New submission from Quentin Agren :
Hi,
This is the first issue I submit so please correct me if I do anything wrong.
Description of the issue:
imporlib logs 'wrote ' even when file creation fails with
OSError (for lack of write persmission for example)
Reproducing the bug in
