be more explicit about asyncio usage
`get_event_loop()` would always implicitly create one on demand, but Python upstream has decided it's a bad/confusing API. Explicitly starting our own, then setting it, is exactly equivalent other than not being scheduled for deprecation.
This commit is contained in:
parent
40315e6ebb
commit
c5e766af75
|
@ -699,7 +699,8 @@ def run(options: 'Arguments') -> int:
|
|||
raise MesonException(f'Unknown subproject type {t!r}, supported types are: {ALL_TYPES_STRING}')
|
||||
tasks: T.List[T.Awaitable[bool]] = []
|
||||
task_names: T.List[str] = []
|
||||
loop = asyncio.get_event_loop()
|
||||
loop = asyncio.new_event_loop()
|
||||
asyncio.set_event_loop(loop)
|
||||
executor = ThreadPoolExecutor(options.num_processes)
|
||||
if types:
|
||||
wraps = [wrap for wrap in wraps if wrap.type in types]
|
||||
|
|
Loading…
Reference in New Issue