Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not your fault, but this looks dumb and isn't clear.
If we decide to merge this I think it would be better to remove the
app_factory
property and rename_import_app_factory > import_app_factory
and use that instead.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that making that function public would be a better option. Want me to refactor the function?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, regarding my problem, namely being able to set my own event loop, and not use the standard one - details are in the issue #156
There are no other details that I can provide - basically I don't know of a nice way to make the
runserver
command use the event loop that I want.If you can suggest a better way, that' fine. I haven't investigated that much, so I don't have an overview of the project's structure.
Until then, the problem remains valid, and both the traceback of the error, and the code that generated it can be found in the issue.
Thanks for your time! :)