Yegor Roganov
Yegor Roganov
Dynamically calling async fixture causes a runtime error saying "This event loop is already running"
Got this error when I tried to upgrade to 0.14.0 from 0.10.0. Rolled back for now.
This issue is very important, something should be done about supporting decoded JSON in WTForms. ATM even BooleanField doesn't work correctly (see https://github.com/wtforms/wtforms/blob/master/wtforms/fields/core.py#L692), not to mention FieldList and FormField. @foxx...
Would be interesting to know how much this affects performance since per @immunda even the current naive implementation affects performance "adversely".
+1 on this. It's especially annoying that mypy requires to provide types of values explicitly in some cases, but later disregards this information and type of values becomes Any. Example:...
+1 for an example It looks like I need to put all my Rx code into a Connector, but I'm not sure. UPD: maybe not even an example, but rather...
For Django 1.4: https://docs.djangoproject.com/en/1.4/topics/testing/#running-tests It seems that docs for Django 1.3 and earlier are not available on djangoproject.com
The issue might be related to https://github.com/mattupstate/flask-mail/issues/88
Thanks @erictraut, it's great to see there's work in this direction. I understand that `@final` is meaningless, but MyPy requires it for `in` narrowing to work. My issue points out...