Re: Django Channels 2.0.0 groups

2018-02-03 Thread Ahmed Magdy
Finally, I think reverting back to channels 1.x.x was much easier for you and me. ^^ Really appreciate what you did and the project, now I can implement the chatting functionality for my graduation project. On Saturday, February 3, 2018 at 9:47:04 AM UTC+2, Andrew Godwin wrote: > > Ah, yes, it l

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Andrew Godwin
Ah, yes, it looks like aioredis requires at least 3.5.2. I will update the channels_redis readme to make this clear. On Fri, Feb 2, 2018 at 11:44 PM, Ahmed Magdy wrote: > v3.5.1:37a07cee5969 > > On Saturday, February 3, 2018 at 9:41:38 AM UTC+2, Andrew Godwin wrote: >> >> That looks like a probl

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Ahmed Magdy
v3.5.1:37a07cee5969 On Saturday, February 3, 2018 at 9:41:38 AM UTC+2, Andrew Godwin wrote: > > That looks like a problem with the version of Python you are running - > what version is it? > > Andrew > > On Fri, Feb 2, 2018 at 11:36 PM, Ahmed Magdy > wrote: > >> Since you closed the issue, I'm p

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Andrew Godwin
That looks like a problem with the version of Python you are running - what version is it? Andrew On Fri, Feb 2, 2018 at 11:36 PM, Ahmed Magdy wrote: > Since you closed the issue, I'm posting here. > Ok, so I've updated asgiref package to 2.1.1 and now getting different > exception. > > > [2018

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Ahmed Magdy
Since you closed the issue, I'm posting here. Ok, so I've updated asgiref package to 2.1.1 and now getting different exception. [2018/02/03 09:29:23] WebSocket HANDSHAKING /sessions/ [127.0.0.1:13235] > ERROR:root:Exception inside application: '_WindowsSelectorEventLoop' > object has no attribu

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Andrew Godwin
Yup, that looks like a genuine bug, I have opened a GitHub issue to track it: https://github.com/django/channels/issues/848 Andrew On Fri, Feb 2, 2018 at 10:35 PM, Ahmed Magdy wrote: > I even made sure to read the docs multiple times before posting. :/ > > I've been reading about Redis, and sin

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Ahmed Magdy
I even made sure to read the docs multiple times before posting. :/ I've been reading about Redis, and since I got windows OS, I installed the port for Windows based redis , tested the server and client they are working ok

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Andrew Godwin
The docs do mention this in a big callout at the top of the Channel Layers page :) http://channels.readthedocs.io/en/latest/topics/channel_layers.html Andrew On Fri, Feb 2, 2018 at 8:52 PM, Ahmed Magdy wrote: > Aha thanks for making it clear, I will read more about redis then. > Shouldn't the d

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Ahmed Magdy
Aha thanks for making it clear, I will read more about redis then. Shouldn't the docs mention that though? On Saturday, February 3, 2018 at 6:47:47 AM UTC+2, Andrew Godwin wrote: > > No, there is no in-memory channel layer any more, only Redis is available > at the moment. You must put something

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Andrew Godwin
No, there is no in-memory channel layer any more, only Redis is available at the moment. You must put something into the settings in order to make it function. Andrew On Fri, Feb 2, 2018 at 8:42 PM, Ahmed Magdy wrote: > I thought it uses in memory channel layer by default if it's empty? I > did

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Ahmed Magdy
I thought it uses in memory channel layer by default if it's empty? I didn't try setting a value, because only redis was available in v2.0.0 and I don't like using stuff I don't understand. On Saturday, February 3, 2018 at 6:08:02 AM UTC+2, Andrew Godwin wrote: > > It needs to contain a value to

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Andrew Godwin
It needs to contain a value to work - what value were you trying that was not empty? Andrew On Fri, Feb 2, 2018 at 8:04 PM, Ahmed Magdy wrote: > I tried not having CHANNEL_LAYERS or setting it to {} > same exception > > On Saturday, February 3, 2018 at 3:36:43 AM UTC+2, Andrew Godwin wrote: >>

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Ahmed Magdy
I tried not having CHANNEL_LAYERS or setting it to {} same exception On Saturday, February 3, 2018 at 3:36:43 AM UTC+2, Andrew Godwin wrote: > > Do you have a CHANNEL_LAYERS setting in your settings file? If so, what is > it set to? > > Andrew > > On Fri, Feb 2, 2018 at 5:17 PM, Ahmed Magdy > w

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Andrew Godwin
Do you have a CHANNEL_LAYERS setting in your settings file? If so, what is it set to? Andrew On Fri, Feb 2, 2018 at 5:17 PM, Ahmed Magdy wrote: > That's what I did after reading the documentation here's how my channels > files look like > > # settings.py > # ... > ASGI_APPLICATION = 'djangoChan

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Ahmed Magdy
That's what I did after reading the documentation here's how my channels files look like # settings.py # ... ASGI_APPLICATION = 'djangoChannels.routing.application' # ... # routing.py from django.conf.urls import url from channels.routing import ProtocolTypeRouter, URLRouter from channels.auth

Re: Django Channels 2.0.0 groups

2018-02-02 Thread Andrew Godwin
Hi Ahmed, In the new release channel layers are optional - if you don't configure them they will indeed come through as None. The settings format changed slightly too - you can read more here: http://channels.readthedocs.io/en/latest/topics/channel_layers.html Andrew On Fri, Feb 2, 2018 at 3:31

Django Channels 2.0.0 groups

2018-02-02 Thread Ahmed Magdy
I'm relatively new to channels and was using Channels v1.x.x groups easily, but after v2.0.0 update and reading the documentation # This example uses WebSocket consumer, which is synchronous, and so # needs the async channel layer functions to be converted. from asgiref.sync import AsyncToSync c