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
documentation for -Uaiohttp.web parameter: Unix file system path to serve on. Specifying a path will cause hostname and port arguments to be ignored.
The aiohttp web argument parser expects that it would be run without -H and -P parameters. Thus default has been passed to argparse. Defaults in argparse works in way that if values has not been specified, they are set anyway. In this situation it works not as intended. The possible solution is to override
Bonus: there may be many hostnames could be provided (as run server accepts), but argument parser is not adapted in this way.
To Reproduce
Let's take very basic aiohttp server implementation from tutorial:
Feel free to make a PR to fix it. I'm not really sure how useful the aiohttp.web entrypoint even is, I don't think it appears anywhere in our documentation..
Not sure about a recommendation but a note regarding another way would be useful. Many frameworks provide runpy entrypoints so I think it should remain exposed.
Describe the bug
documentation for
-U
aiohttp.web
parameter:Unix file system path to serve on. Specifying a path will cause hostname and port arguments to be ignored.
The
aiohttp
web argument parser expects that it would be run without-H
and-P
parameters. Thus default has been passed toargparse
. Defaults in argparse works in way that if values has not been specified, they are set anyway. In this situation it works not as intended. The possible solution is to overrideBonus: there may be many hostnames could be provided (as run server accepts), but argument parser is not adapted in this way.
To Reproduce
Let's take very basic aiohttp server implementation from tutorial:
and run it:
Expected behavior
I'm expecting that server is:
Logs/tracebacks
Python Version
aiohttp Version
multidict Version
yarl Version
OS
macOS
Related component
Server
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: