Daniel Gilge

Unfortunately, this issue is still not fixed. Does anybody have a (temporary) solution? For instance another package which is a continuation of this package?

Here is a version for `py.test` without `TestCase` that works for me so far. (It's adjusted from `django.test.Client`.) **Note**: Transactions don't seem to work in this async setting. As a...

Yes, this is what I meant. `pytest-django` wrappes tests cases into transactions if you use the `db` fixture or the `django_db` mark. But it has no effect (in the current...

@andrewgodwin How should this be done? - Let the `__init__` method have another kwarg `login_user` where you can pass a user object and the login will be done like in...

This is working in my project so far: ```python class AuthWebsocketCommunicator(WebsocketCommunicator): async def __new__(cls, *args, **kwargs): instance = super().__new__(cls) await instance.__init__(*args, **kwargs) return instance async def __init__(self, application, path, headers=None,...

@mapes911 Thanks for sharing this. However, I thought to do the login within the communicator class because the communicator should be kind of a replacement for the `django.test.Client`. @andrewgodwin I...

@Akshita6 Just in case you didn't check which pulgins are loaded when you run `pytest`... I had the same error. In my case `pytest-asyncio` wasn't installed properly.

It will take a little effort to support Djanog 2.1 (https://travis-ci.org/Tivix/django-rest-auth/jobs/443539332). Therefore, I remove it for now.

Same issue here. ``` E806: using Float as a String E15: Invalid expression: 1.618 ``` Are there plans to fix this?