As of yarl 1.0.0 (available since one hour ago), yarl.unquote is no longer available, thus causing an import error at web_urldispatcher.py.
Been able to run: from aiohttp import web
from aiohttp import web raises the following error:
Traceback (most recent call last):
File "web.py", line 1, in <module>
from aiohttp import web
File "/home/ruggero/Development/mqtt/.venv/lib/python3.6/site-packages/aiohttp/web.py", line 15, in <module>
from . import (hdrs, web_exceptions, web_fileresponse, web_middlewares,
File "/home/ruggero/Development/mqtt/.venv/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 5, in <module>
from aiohttp.web_urldispatcher import SystemRoute
File "/home/ruggero/Development/mqtt/.venv/lib/python3.6/site-packages/aiohttp/web_urldispatcher.py", line 21, in <module>
from yarl import URL, unquote
ImportError: cannot import name 'unquote'
Simply: from aiohttp import web
aiohttp 2.3.7 (both)
Ubuntu Linux 16.04
Python 3.6.3
Downgrade to yarl 0.18.0
Same problem since yarl 1.0.0, downgrading to yarl==0.18.0 helps as workaround.
13:36:06 File "/var/jenkins/workspace/sometest-01-test/test/__init__.py", line 19, in <module>
13:36:06 from aiohttp import web
13:36:06 File "/var/jenkins/shiningpanda/jobs/bd59e0bb/virtualenvs/d41d8cd9/lib/python3.6/site-packages/aiohttp/web.py", line 15, in <module>
13:36:06 from . import (hdrs, web_exceptions, web_fileresponse, web_middlewares,
13:36:06 File "/var/jenkins/shiningpanda/jobs/bd59e0bb/virtualenvs/d41d8cd9/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 5, in <module>
13:36:06 from aiohttp.web_urldispatcher import SystemRoute
13:36:06 File "/var/jenkins/shiningpanda/jobs/bd59e0bb/virtualenvs/d41d8cd9/lib/python3.6/site-packages/aiohttp/web_urldispatcher.py", line 21, in <module>
13:36:06 from yarl import URL, unquote
13:36:06 ImportError: cannot import name 'unquote'
Same here, opened a ticket to yarl.
Confirmed @ilmaruk , you were faster 馃憤
CHANGES
1.0.0 (2018-01-15)
Drop yarl.quote and yarl.unquote public functions (#155)
Can we get someone to pin yarl==0.18.0 in deps until the problem is sorted out?
For reference, #2664
@asvetlov ^^
Just in case: I'm working on moving aiohttp internals towards public yarl interfaces.
Damn that was quick! Good job everyone
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs.
If you feel like there's important points made in this discussion, please include those exceprts into that [new issue].
Most helpful comment
Can we get someone to pin
yarl==0.18.0in deps until the problem is sorted out?