Re: Drop Down Menu in Django Forms not working.

Yes, name is a foreign key here. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to

Re: Template Rendering Django 1.11

Are you using the cached template loader? It may mitigate the problem to some extent. https://docs.djangoproject.com/en/1.11/ref/templates/api/#django.template.loaders.cached.Loader As of Django 1.11, it's enabled if DEBUG is False and OPTIONS['loaders']

module object has no attribute after using different version of Python

I have both versions python 2.7 and 3.4 installed. I am using some code which is developed under 2.7 but I am using under 3.4. So after compiling using the following command python manage.py runserver I get the following error - File "C:\pyprojects\focus\site\general\forms.py", line 26, in

Re: Drop Down Menu in Django Forms not working.

name is a ForeignKey field? If not, you shouldn't use queryset attribute there. Use choices instead. If you want to render all available choices from db, you can get it like Model.objects.filter(...).values_list('name', flat=True) On Friday, August 4, 2017 at 8:07:24 PM UTC+3, Arun S wrote: > >

Re: Channels vs Django-websocket-redis

Hi, I look at django-websockets-redis really quickly. If you decide to use Redis ASGI layer it may look familiar. Main differences I notice so far: - ws4redis doesn't have concept of consumers and routing - it's coupled to the subset of WebSocket usage - it's propagate redis to the library api

Channels vs Django-websocket-redis

Hi, thanks for feedback! I need some time to dig into django-websocket-redis. I'll come back to you soon. Regards, Artem. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send

Re: [Django Channels] Can I use the same redis server as message backend and cache backend the same time?

1. You can - Channels namespaces itself away from most keys you might use (and you add a custom prefix with the "prefix" option). 2. Yes, as long as both sites have a different prefix setting In both cases I would recommend using separate Redis servers though. They have very low RAM usage and

[Django Channels] Can I use the same redis server as message backend and cache backend the same time?

I have 2 questions. 1.Can I use the same redis server as message backend and cache backend the same time? 2.Can I use the same redis server as message backend for different website they both serve by channels ? -- You received this message because you are subscribed to the Google Groups