With the most recent 3.4 bugfix, calling create_server with port=None stopped working. This also affects 3.5, and I would imagine also 3.6, but haven't checked that. Test case: import asyncio; l = asyncio.get_event_loop(); l.run_until_complete(l.create_server(lambda: None, host='0.0.0.0', port=None)) Expected result: a socket object Broken result: "TypeError: an integer is required (got type NoneType)"
Ah thanks, that's fair. It seems a shame since this regression was introduced to 3.4 by a security/bugfix release. Since there's a workaround it's not a big deal.
History
Date
User
Action
Args
2022-04-11 14:58:33
admin
set
github: 71602
2016-09-16 10:43:58
mcobden
set
messages: +
2016-09-16 10:37:57
berker.peksag
set
status: open -> closedversions: + Python 3.5nosy: + berker.peksagmessages: + resolution: out of date
2016-09-16 10:25:51
mcobden
set
status: closed -> openresolution: works for me -> (no value)messages: + versions: - Python 3.5
2016-09-15 21:49:05
yselivanov
set
status: open -> closedresolution: works for memessages: + stage: resolved
2016-07-12 19:34:27
mcobden
set
title: BaseEventLoop.create_server does not accept port=None -> regression: BaseEventLoop.create_server does not accept port=None
