You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Importing aiohttp results in a lot of ImportWarnings.
While cleaning the app from warnings I noticed that a lot of them stem from aiohttp. To my surprise, simply importing the library results in 10 warning. Of these, DeprecationWarnings are addressed in #3275, but I don't see anything about ImportWarnings.
Expected behaviour
Expected no warnings on library import.
Actual behaviour
ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
Steps to reproduce
$ python -Wall -c "import aiohttp"
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
project_root/venv/lib/python3.7/site-packages/aiohttp/multipart.py:8: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
from collections import Mapping, Sequence, deque
project_root/venv/lib/python3.7/site-packages/aiohttp/multipart.py:8: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
from collections import Mapping, Sequence, deque
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
return f(*args, **kwds)
Your environment
Linux Mint 18.3, Python 3.7.1, aiohttp 3.4.4.
The text was updated successfully, but these errors were encountered:
GitMate.io thinks the contributor most likely able to help you is @asvetlov.
Possibly related issues are #2301 (pyinstaller cannot import aiohttp), #276 (python crashes on aiohttp import), #2956 (Enable logging when aiohttp.web is used as a program), #2320 (aiohttp-jinja2), and #3044 (Uvloop raises a warning when I use aiohttp.test_utils.loop_context).
Long story short
Importing
aiohttp
results in a lot of ImportWarnings.While cleaning the app from warnings I noticed that a lot of them stem from aiohttp. To my surprise, simply importing the library results in 10 warning. Of these, DeprecationWarnings are addressed in #3275, but I don't see anything about ImportWarnings.
Expected behaviour
Expected no warnings on library import.
Actual behaviour
ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__
Steps to reproduce
Your environment
Linux Mint 18.3, Python 3.7.1, aiohttp 3.4.4.
The text was updated successfully, but these errors were encountered: