Closed argaen closed 7 years ago
Umm, I had the same thought a few days ago. Finally, for consistency, I prefer to leave the clock-bomb on the user's hands. If they do not configure the factory they must configure it. Trying to make all happy - tests, not well configured environments, etc - might head us to weak environments.
I'm facing a similar issue now, what's the fix for this? I'm new to aiotask and not sure which factory are we talking here to initialize. can someone help here
There's more info in the readme
loop.set_task_factory(context.task_factory)
If the factory hasn't been set, we will see errors like
Instead of propagating this exception, an alternative way of dealing with this is:
In the set method, we would just show the warning.
This avoids impact when users are not aware of this module, forget to initialize the factory (or maybe they just don't want to), tests...
I'm not sure either this is something we want though, @pfreixes what do you think?