from:"alex"

I've just checked, and self.consistent_hash(group) returns '0' in both 
functions, so it should be connecting to the same db...

On Friday, 23 March 2018 16:05:16 UTC, Andrew Godwin wrote:
>
> I would check the connection is going to the right server/database as 
> well? But past that, I can't help you - I'd try doing some things with 
> plain aioredis to see if you can replicate it there.
>
> Andrew
>
> On Fri, Mar 23, 2018 at 9:01 AM, 'Alex' via Django users <
> django...@googlegroups.com > wrote:
>
>> Hi,
>>
>> I've used the redis-cli to get the contents of the key, and it has filled 
>> it properly, so the information is definitely in redis under that key. The 
>> issue seems to be that message = await connection.get(pers_key) always 
>> returns none. One thing I'm certain of is that it's in redis!
>>
>> Alex
>>
>> On Friday, 23 March 2018 15:58:37 UTC, Andrew Godwin wrote:
>>>
>>> It looks correct at first glance - I would insert a debugger there and 
>>> see what the Redis database contained manually at that point.
>>>
>>> Andrew
>>>
>>> On Fri, Mar 23, 2018 at 2:56 AM, 'Alex' via Django users <
>>> django...@googlegroups.com> wrote:
>>>
>>>> I've been trying to add persistence to channel layers, such that each 
>>>> new consumer joining a group is sent the most recent message from that 
>>>> group, on connect. Below are my attempts. For some reason, the message in 
>>>> the highlighted line always seems to be of type 'None'. Am I going about 
>>>> this completely incorrectly? I'd be really grateful for any help.
>>>>
>>>>
>>>> from channels_redis.core import RedisChannelLayer
>>>> from channels.exceptions import ChannelFull
>>>> import time
>>>>
>>>>
>>>> class RedisChannelLayerGroupPersistence(RedisChannelLayer):
>>>>
>>>>
>>>>
>>>>
>>>> async def group_send(self, group, message):
>>>> """
>>>> Sends a message to the entire group.
>>>> """
>>>> assert self.valid_group_name(group), "Group name not valid"
>>>> # Retrieve list of all channel names
>>>> key = self._group_key(group)
>>>> pers_key = str(key) + "_PERS"
>>>> async with self.connection(self.consistent_hash(group)) as 
>>>> connection:
>>>> # Discard old channels based on group_expiry
>>>> await connection.zremrangebyscore(key, min=0, max=int(time.
>>>> time()) - self.group_expiry)
>>>> # Return current lot
>>>> channel_names = [
>>>> x.decode("utf8") for x in
>>>> await connection.zrange(key, 0, -1)
>>>> ]
>>>> # TODO: More efficient implementation (lua script per shard?) 
>>>>  try:
>>>> await connection.persist(pers_key)
>>>> await connection.set(pers_key, str(message))
>>>> print("TYPE = 
>>>>  {}".format(type(str(
>>>> message
>>>>
>>>>
>>>> for channel in channel_names:
>>>> try:
>>>> await self.send(channel, message)
>>>> except ChannelFull:
>>>> pass
>>>>
>>>>
>>>> async def group_add(self, group, channel):
>>>>
>>>>
>>>> """
>>>> Adds the channel name to a group.
>>>> """
>>>> # Check the inputs
>>>> assert self.valid_group_name(group), "Group name not valid"
>>>> assert self.valid_channel_name(channel), "Channel name not 
>>>> valid"
>>>> # Get a connection to the right shard
>>>> group_key = self._group_key(group)
>>>> pers_key = str(group_key) + "_PERS"
>>>> async with self.connection(self.consistent_hash(group)) as 
>>>> connection:
>>>> message = await connection.get(pers_key) #ISSUE HERE 
>>>> -- MESSAGE IS NONE
>>>> # Add to group sorted set with creation time as times

Re: Overriding channel-layer's group_send and group_add to add persistence

That did occur to me, but both connect using the function below, so unless 
they're somehow referring to different groups, I'm not sure how they could 
be going to different servers/databases...
async with self.connection(self.consistent_hash(group)) as connection:


On Friday, 23 March 2018 16:05:16 UTC, Andrew Godwin wrote:
>
> I would check the connection is going to the right server/database as 
> well? But past that, I can't help you - I'd try doing some things with 
> plain aioredis to see if you can replicate it there.
>
> Andrew
>
> On Fri, Mar 23, 2018 at 9:01 AM, 'Alex' via Django users <
> django...@googlegroups.com > wrote:
>
>> Hi,
>>
>> I've used the redis-cli to get the contents of the key, and it has filled 
>> it properly, so the information is definitely in redis under that key. The 
>> issue seems to be that message = await connection.get(pers_key) always 
>> returns none. One thing I'm certain of is that it's in redis!
>>
>> Alex
>>
>> On Friday, 23 March 2018 15:58:37 UTC, Andrew Godwin wrote:
>>>
>>> It looks correct at first glance - I would insert a debugger there and 
>>> see what the Redis database contained manually at that point.
>>>
>>> Andrew
>>>
>>> On Fri, Mar 23, 2018 at 2:56 AM, 'Alex' via Django users <
>>> django...@googlegroups.com> wrote:
>>>
>>>> I've been trying to add persistence to channel layers, such that each 
>>>> new consumer joining a group is sent the most recent message from that 
>>>> group, on connect. Below are my attempts. For some reason, the message in 
>>>> the highlighted line always seems to be of type 'None'. Am I going about 
>>>> this completely incorrectly? I'd be really grateful for any help.
>>>>
>>>>
>>>> from channels_redis.core import RedisChannelLayer
>>>> from channels.exceptions import ChannelFull
>>>> import time
>>>>
>>>>
>>>> class RedisChannelLayerGroupPersistence(RedisChannelLayer):
>>>>
>>>>
>>>>
>>>>
>>>> async def group_send(self, group, message):
>>>> """
>>>> Sends a message to the entire group.
>>>> """
>>>> assert self.valid_group_name(group), "Group name not valid"
>>>> # Retrieve list of all channel names
>>>> key = self._group_key(group)
>>>> pers_key = str(key) + "_PERS"
>>>> async with self.connection(self.consistent_hash(group)) as 
>>>> connection:
>>>> # Discard old channels based on group_expiry
>>>> await connection.zremrangebyscore(key, min=0, max=int(time.
>>>> time()) - self.group_expiry)
>>>> # Return current lot
>>>> channel_names = [
>>>> x.decode("utf8") for x in
>>>> await connection.zrange(key, 0, -1)
>>>> ]
>>>> # TODO: More efficient implementation (lua script per shard?) 
>>>>  try:
>>>> await connection.persist(pers_key)
>>>> await connection.set(pers_key, str(message))
>>>> print("TYPE = 
>>>>  {}".format(type(str(
>>>> message
>>>>
>>>>
>>>> for channel in channel_names:
>>>> try:
>>>> await self.send(channel, message)
>>>> except ChannelFull:
>>>> pass
>>>>
>>>>
>>>> async def group_add(self, group, channel):
>>>>
>>>>
>>>> """
>>>> Adds the channel name to a group.
>>>> """
>>>> # Check the inputs
>>>> assert self.valid_group_name(group), "Group name not valid"
>>>> assert self.valid_channel_name(channel), "Channel name not 
>>>> valid"
>>>> # Get a connection to the right shard
>>>> group_key = self._group_key(group)
>>>> pers_key = str(group_key) + "_PERS"
>>>> async with self.connection(self.consistent_hash(group)) as 
>>>> connection:
>>>> message = await connection.get(pers_k

Re: Overriding channel-layer's group_send and group_add to add persistence

Hi,

I've used the redis-cli to get the contents of the key, and it has filled 
it properly, so the information is definitely in redis under that key. The 
issue seems to be that message = await connection.get(pers_key) always 
returns none. One thing I'm certain of is that it's in redis!

Alex

On Friday, 23 March 2018 15:58:37 UTC, Andrew Godwin wrote:
>
> It looks correct at first glance - I would insert a debugger there and see 
> what the Redis database contained manually at that point.
>
> Andrew
>
> On Fri, Mar 23, 2018 at 2:56 AM, 'Alex' via Django users <
> django...@googlegroups.com > wrote:
>
>> I've been trying to add persistence to channel layers, such that each new 
>> consumer joining a group is sent the most recent message from that group, 
>> on connect. Below are my attempts. For some reason, the message in the 
>> highlighted line always seems to be of type 'None'. Am I going about this 
>> completely incorrectly? I'd be really grateful for any help.
>>
>>
>> from channels_redis.core import RedisChannelLayer
>> from channels.exceptions import ChannelFull
>> import time
>>
>>
>> class RedisChannelLayerGroupPersistence(RedisChannelLayer):
>>
>>
>>
>>
>> async def group_send(self, group, message):
>> """
>> Sends a message to the entire group.
>> """
>> assert self.valid_group_name(group), "Group name not valid"
>> # Retrieve list of all channel names
>> key = self._group_key(group)
>> pers_key = str(key) + "_PERS"
>> async with self.connection(self.consistent_hash(group)) as 
>> connection:
>> # Discard old channels based on group_expiry
>> await connection.zremrangebyscore(key, min=0, max=int(time.
>> time()) - self.group_expiry)
>> # Return current lot
>> channel_names = [
>> x.decode("utf8") for x in
>> await connection.zrange(key, 0, -1)
>> ]
>> # TODO: More efficient implementation (lua script per shard?) 
>>  try:
>> await connection.persist(pers_key)
>> await connection.set(pers_key, str(message))
>> print("TYPE = 
>>  {}".format(type(str(
>> message
>>
>>
>> for channel in channel_names:
>> try:
>> await self.send(channel, message)
>> except ChannelFull:
>> pass
>>
>>
>> async def group_add(self, group, channel):
>>
>>
>> """
>> Adds the channel name to a group.
>> """
>> # Check the inputs
>> assert self.valid_group_name(group), "Group name not valid"
>> assert self.valid_channel_name(channel), "Channel name not valid"
>> # Get a connection to the right shard
>> group_key = self._group_key(group)
>> pers_key = str(group_key) + "_PERS"
>> async with self.connection(self.consistent_hash(group)) as 
>> connection:
>> message = await connection.get(pers_key) #ISSUE HERE 
>> -- MESSAGE IS NONE
>> # Add to group sorted set with creation time as timestamp
>> await connection.zadd(
>> group_key,
>> time.time(),
>> channel,
>> )
>> # Set expiration to be group_expiry, since everything in
>> # it at this point is guaranteed to expire before that
>> try:
>> await self.send(channel, str(message))
>> except ChannelFull:
>> pass
>>
>>
>>
>>
>> await connection.expire(group_key, self.group_expiry)
>>
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/abc8747d-8d80-4ec4-a2ca-d5e91c161c08%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-users/abc8747d-8d80-4ec4-a2ca-d5e91c161c08%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/24613c4d-c566-4631-97cd-e858d286aadf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Overriding channel-layer's group_send and group_add to add persistence

I've been trying to add persistence to channel layers, such that each new 
consumer joining a group is sent the most recent message from that group, 
on connect. Below are my attempts. For some reason, the message in the 
highlighted line always seems to be of type 'None'. Am I going about this 
completely incorrectly? I'd be really grateful for any help.


from channels_redis.core import RedisChannelLayer
from channels.exceptions import ChannelFull
import time


class RedisChannelLayerGroupPersistence(RedisChannelLayer):




async def group_send(self, group, message):
"""
Sends a message to the entire group.
"""
assert self.valid_group_name(group), "Group name not valid"
# Retrieve list of all channel names
key = self._group_key(group)
pers_key = str(key) + "_PERS"
async with self.connection(self.consistent_hash(group)) as 
connection:
# Discard old channels based on group_expiry
await connection.zremrangebyscore(key, min=0, max=int(time.time
()) - self.group_expiry)
# Return current lot
channel_names = [
x.decode("utf8") for x in
await connection.zrange(key, 0, -1)
]
# TODO: More efficient implementation (lua script per shard?)  try:
await connection.persist(pers_key)
await connection.set(pers_key, str(message))
print("TYPE =  
{}".format(type(str(message


for channel in channel_names:
try:
await self.send(channel, message)
except ChannelFull:
pass


async def group_add(self, group, channel):


"""
Adds the channel name to a group.
"""
# Check the inputs
assert self.valid_group_name(group), "Group name not valid"
assert self.valid_channel_name(channel), "Channel name not valid"
# Get a connection to the right shard
group_key = self._group_key(group)
pers_key = str(group_key) + "_PERS"
async with self.connection(self.consistent_hash(group)) as 
connection:
message = await connection.get(pers_key) #ISSUE HERE 
-- MESSAGE IS NONE
# Add to group sorted set with creation time as timestamp
await connection.zadd(
group_key,
time.time(),
channel,
)
# Set expiration to be group_expiry, since everything in
# it at this point is guaranteed to expire before that
try:
await self.send(channel, str(message))
except ChannelFull:
pass




await connection.expire(group_key, self.group_expiry)


-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/abc8747d-8d80-4ec4-a2ca-d5e91c161c08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Listening to a django channel from outside a consumer

2018-03-12 Thread Alex



Hi,


The docs explain that it is possible to publish to the channel layer from 
outside of a consumer: 
https://channels.readthedocs.io/en/latest/topics/channel_layers.html#using-outside-of-consumers
 I 
need to do the opposite. I have a fairly complex python script that reads 
live data from pubnub, processes it, and pushes it to consumers via groups 
on the channel_layer. This works fine, but I need consumers to be able to 
announce their presence to this script so that it can push them data (it 
currently pushes to the channel layer only when it gets new data from 
pubnub, which could be every 24 hours).


I've decided to solve this by having the consumers publish to a 'presence' 
channel on connect. I now need the pubnub source script to listen to this 
channel. I've tried adding the below to the script, and it no longer throws 
errors, but it doesn't actually respond to messages. It successfully joins 
the channel layer, but the message handler 'receive_json', never fires.


This is the class, and then the initiation further down in the code:
from channels.generic.websocket import JsonWebsocketConsumer


class channelConsumer(JsonWebsocketConsumer):

def __init__(self):
self.channel_name = 'source'
def join(self):
async_to_sync(channel_layer.group_add)('presence', self.channel_name
)
def receive_json(self, message):
print("Presence Detected")
# do some stuff

global channel_layer
channel_layer = get_channel_layer()

global listener
listener = channelConsumer()
listener.join()




-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/08086bed-67a8-4fd6-8eec-0c417423ea8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failing to configure Django correctlly (conflict in settings between models.py and manage.py usage).

The only thing I need from Django (at this point) is to have the ability to 
communicate with my DB.
(person = models.Person.objects.filter(phone_number= phone_number) from my 
previous example)
I'm planning to use the admin page and I might add a GUI in some point.

Regards,
Alex

On Friday, January 5, 2018 at 5:10:20 PM UTC+2, Andréas Kühne wrote:
>
> Ah, 
>
> OK.
>
> Now it is a bit more clear. 
>
> What you are doing is not supported by django. You don't use the django 
> models OUTSIDE of the django project. That is not a supported usecase. You 
> can probably set it up, so that you CAN do that, but I would not recommend 
> it.
>
> What are you trying to accomplish by reading the models OUTSIDE of the 
> django project?
>
> Regards,
>
> Andréas
>
> 2018-01-05 15:50 GMT+01:00 alex Tarasiuk <alex...@gmail.com >
> :
>
>> Here is what I've done so far (it is a new project and I did followed the 
>> tutorial until it didn't worked for me any more).
>>
>> Here are the steps of how I created the project:
>>
>> 1. django-admin startproject MY_DGANGO
>>
>> 2.  python manage.py startapp my_django
>>
>> 3.  edited the models.py
>>
>> 4. python manage.py makemigrations my_django
>>
>> 5. python manage.py sqlmigrate my_django 0001
>>
>> 6.  python manage.py migrate
>>
>>  
>>
>> Now after the tables in the DB was created, I want to use it 
>> (add/remove/update date) from my project.
>>
>>
>> 7.  So from my project I’m importing models so I’ll be able to use the 
>> classes I’ve created to extract and add information to/from the DB.
>>
>> For example:
>>
>> · In models.py:
>>
>> Class Person(models.Model):
>>
>> first_name = models.CharField(max_length=100, null=False)
>>
>> last_name = models.CharField(max_length=100, null=False)
>>
>> phone_number = models.CharField(max_length=100, null=False)
>>
>> …
>>
>>  
>>
>> · In some file in my project:
>>
>> from MY_DGANGO.my_django import models
>>
>> ….
>>
>> def add_person(first_name, last_name, phone_number):
>>
>> …
>>
>> person = models.Person(first_name= first_name, last_name= last_name, 
>>
>> phone_number= phone_number)
>>
>> person.save()
>>
>> …
>>
>> …
>>
>> …
>>
>> def get_person_by_phone_number(phone_number):
>>
>> …
>>
>> person = models.Person.objects.filter(phone_number= phone_number)
>>
>> …
>>
>>
>> P.S. I'm runnig it without starting any Django server.
>>
>>
>>
>> On Friday, January 5, 2018 at 4:29:11 PM UTC+2, Andréas Kühne wrote:
>>>
>>> Ok,
>>>
>>> So are you in the folder where the manage.py file resides when you run 
>>> your commands? You have to be in that directory when running manage.py 
>>> commands.
>>>
>>> Also - as long as you haven't done too much already - I would recommend 
>>> starting fresh and looking into the tutorials in the django docs pages on 
>>> how to start a project. See 
>>> https://docs.djangoproject.com/en/2.0/intro/tutorial01/ or 
>>> https://tutorial.djangogirls.org/en/.
>>>
>>> The settings you have changed there are very strange (as Ramiro pointed 
>>> out) and should definitely not be required. Have you set the 
>>> DEFAULT_INDEX_TABLESPACE 
>>> setting anywhere? Because that is also something that shouldn't be 
>>> required
>>>
>>> Med vänliga hälsningar,
>>>
>>> Andréas
>>>
>>> 2018-01-05 15:17 GMT+01:00 alex Tarasiuk <alex...@gmail.com>:
>>>
>>>> Hi Andréas,
>>>> Thanks for your response.
>>>>
>>>> When I'm removing the lines you've talked about I'm having the 
>>>> following error:
>>>>
>>>> django.core.exceptions.ImproperlyConfigured: Requested setting 
>>>> DEFAULT_INDEX_TABLESPACE, but settings are not configured. You must either 
>>>> define the environment variable DJANGO_SETTINGS_MODULE or call 
>>>> settings.configure() before accessing settings.
>>>>
>>>> This is why I've added those settings in the first place.
>>>>
>>>>
>>>>
>>>> On Friday, January 5, 2018 at 3:59:31 PM UTC+2, Andréas Kühne wrote:
>>>>>
>>>>> Hi Alex,
&

Re: Failing to configure Django correctlly (conflict in settings between models.py and manage.py usage).

Here is what I've done so far (it is a new project and I did followed the 
tutorial until it didn't worked for me any more).

Here are the steps of how I created the project:

1. django-admin startproject MY_DGANGO

2.  python manage.py startapp my_django

3.  edited the models.py

4. python manage.py makemigrations my_django

5. python manage.py sqlmigrate my_django 0001

6.  python manage.py migrate

 

Now after the tables in the DB was created, I want to use it 
(add/remove/update date) from my project.


7.  So from my project I’m importing models so I’ll be able to use the 
classes I’ve created to extract and add information to/from the DB.

For example:

· In models.py:

Class Person(models.Model):

first_name = models.CharField(max_length=100, null=False)

last_name = models.CharField(max_length=100, null=False)

phone_number = models.CharField(max_length=100, null=False)

…

 

· In some file in my project:

from MY_DGANGO.my_django import models

….

def add_person(first_name, last_name, phone_number):

…

person = models.Person(first_name= first_name, last_name= last_name, 

phone_number= phone_number)

person.save()

…

…

…

def get_person_by_phone_number(phone_number):

…

person = models.Person.objects.filter(phone_number= phone_number)

…


P.S. I'm runnig it without starting any Django server.



On Friday, January 5, 2018 at 4:29:11 PM UTC+2, Andréas Kühne wrote:
>
> Ok,
>
> So are you in the folder where the manage.py file resides when you run 
> your commands? You have to be in that directory when running manage.py 
> commands.
>
> Also - as long as you haven't done too much already - I would recommend 
> starting fresh and looking into the tutorials in the django docs pages on 
> how to start a project. See 
> https://docs.djangoproject.com/en/2.0/intro/tutorial01/ or 
> https://tutorial.djangogirls.org/en/.
>
> The settings you have changed there are very strange (as Ramiro pointed 
> out) and should definitely not be required. Have you set the 
> DEFAULT_INDEX_TABLESPACE 
> setting anywhere? Because that is also something that shouldn't be 
> required
>
> Med vänliga hälsningar,
>
> Andréas
>
> 2018-01-05 15:17 GMT+01:00 alex Tarasiuk <alex...@gmail.com >
> :
>
>> Hi Andréas,
>> Thanks for your response.
>>
>> When I'm removing the lines you've talked about I'm having the following 
>> error:
>>
>> django.core.exceptions.ImproperlyConfigured: Requested setting 
>> DEFAULT_INDEX_TABLESPACE, but settings are not configured. You must either 
>> define the environment variable DJANGO_SETTINGS_MODULE or call 
>> settings.configure() before accessing settings.
>>
>> This is why I've added those settings in the first place.
>>
>>
>>
>> On Friday, January 5, 2018 at 3:59:31 PM UTC+2, Andréas Kühne wrote:
>>>
>>> Hi Alex,
>>>
>>> You shouldn't have anything regarding the settings in models.py.
>>>
>>> Remove:
>>> import os
>>> import django
>>> os.environ["DJANGO_SETTINGS_MODULE"] = "MY_DJANGO.MY_DJANGO.settings"
>>> django.setup()
>>>
>>> from your models.py file. You should never have any settings in the 
>>> models.py file at all. Also, you should never reference the django project 
>>> folder (your first MY_DJANGO here) in the project. It always has that 
>>> folder anyway.
>>>
>>> In settings.py, your INSTALLED_APPS should look like this:
>>>
>>> INSTALLED_APPS = [
>>> 'django.contrib.admin',
>>> 'django.contrib.auth',
>>> 'django.contrib.contenttypes',
>>> 'django.contrib.sessions',
>>> 'django.contrib.messages',
>>> 'django.contrib.staticfiles',
>>> 'django.contrib.sites',
>>> 'django.contrib.admindocs',
>>>
>>> 'my_django',
>>>
>>> ]
>>>
>>>
>>> Everything should then work as expected.
>>>
>>> Regards,
>>>
>>> Andréas
>>>
>>> 2018-01-05 13:07 GMT+01:00 alex Tarasiuk <alex...@gmail.com>:
>>>
>>>> Hi, I'm new to Django and having some trouble to configure it.
>>>> I'm using Django 1.11.9 (1.11.5 at first but then upgraded with hopes 
>>>> it will solve the issue) and Python 2.7.12 from virtualenv.
>>>>
>>>> Here is my project structure (Please pay attention to upper/lower case 
>>>> letters - it is intentionally):
>>>>
>>>> :
>>>>
>>>> module 1
>>>>

Re: Failing to configure Django correctlly (conflict in settings between models.py and manage.py usage).

Hi Andréas,
Thanks for your response.

When I'm removing the lines you've talked about I'm having the following 
error:

django.core.exceptions.ImproperlyConfigured: Requested setting 
DEFAULT_INDEX_TABLESPACE, but settings are not configured. You must either 
define the environment variable DJANGO_SETTINGS_MODULE or call 
settings.configure() before accessing settings.

This is why I've added those settings in the first place.



On Friday, January 5, 2018 at 3:59:31 PM UTC+2, Andréas Kühne wrote:
>
> Hi Alex,
>
> You shouldn't have anything regarding the settings in models.py.
>
> Remove:
> import os
> import django
> os.environ["DJANGO_SETTINGS_MODULE"] = "MY_DJANGO.MY_DJANGO.settings"
> django.setup()
>
> from your models.py file. You should never have any settings in the 
> models.py file at all. Also, you should never reference the django project 
> folder (your first MY_DJANGO here) in the project. It always has that 
> folder anyway.
>
> In settings.py, your INSTALLED_APPS should look like this:
>
> INSTALLED_APPS = [
> 'django.contrib.admin',
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',
> 'django.contrib.sites',
> 'django.contrib.admindocs',
>
> 'my_django',
>
> ]
>
>
> Everything should then work as expected.
>
> Regards,
>
> Andréas
>
> 2018-01-05 13:07 GMT+01:00 alex Tarasiuk <alex...@gmail.com >
> :
>
>> Hi, I'm new to Django and having some trouble to configure it.
>> I'm using Django 1.11.9 (1.11.5 at first but then upgraded with hopes it 
>> will solve the issue) and Python 2.7.12 from virtualenv.
>>
>> Here is my project structure (Please pay attention to upper/lower case 
>> letters - it is intentionally):
>>
>> :
>>
>> module 1
>>
>> module 2
>>
>> ...
>>
>> ...
>>
>> MY_DJANGO:
>>
>> MY_DJANGO:
>>
>> __init__.py
>>
>> settings.py
>>
>> urls.py
>>
>> wsgi.py
>>
>> my_django:
>>
>> migrations
>>
>> __init__.py
>>
>> admin.py
>>
>> apps.py
>>
>> models.py
>>
>> tests.py
>>
>> views.py
>>
>> __init__.py
>>
>> manage.py
>>  
>> in models.py I've added:
>>
>> import os
>> import django
>> os.environ["DJANGO_SETTINGS_MODULE"] = "MY_DJANGO.MY_DJANGO.settings"
>> django.setup()
>>
>> before the models import from django.db.
>>
>> in manage.py, in the main
>>
>> os.environ.setdefault("DJANGO_SETTINGS_MODULE", "MY_DJANGO.settings")
>>
>> was auto generated by Django 
>>
>> in settings.py, in INSTALLED_APPS:
>>
>> INSTALLED_APPS = [
>> 'django.contrib.admin',
>> 'django.contrib.auth',
>> 'django.contrib.contenttypes',
>> 'django.contrib.sessions',
>> 'django.contrib.messages',
>> 'django.contrib.staticfiles',
>> 'django.contrib.sites',
>> 'django.contrib.admindocs',
>>
>> ==>>>>'MY_DJANGO.my_django', or 'my_django', <<<<= Here is 
>> the problem
>>
>> ]
>>
>>
>> Problem description:
>>
>> if I use 'MY_DJANGO.my_django' in INSTALLED_APPS then running 'python 
>> manage.py check' command yields:
>>
>>  ImportError: No module named MY_DJANGO.settings
>>
>>
>>  
>>
>> and if I use 'my_django' in INSTALLED_APPS then I have an import error 
>> while importing models:
>>
>>  from MY_DJANGO.my_django import models (in some file) yields:
>>
>> ImportError: No module named my_django 
>>
>>
>> Also tried to add  ''my_django.apps.MyDjangoConfig' to INSTALLED_APPS, 
>> and it didn't helped.
>>
>> What am I doing wrong??
>>
>> Thanks in advance,
>> Alex.
>>
>>  
>>
>>
>>
>>
>>
>>
>>  
>>
>> -- 
>> 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...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/bb9251bb-7bce-4eec-b8ac-90b031db1284%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-users/bb9251bb-7bce-4eec-b8ac-90b031db1284%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/31d7a9d0-a861-4814-a4d5-9771ba828918%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Failing to configure Django correctlly (conflict in settings between models.py and manage.py usage).

Hi, I'm new to Django and having some trouble to configure it.
I'm using Django 1.11.9 (1.11.5 at first but then upgraded with hopes it 
will solve the issue) and Python 2.7.12 from virtualenv.

Here is my project structure (Please pay attention to upper/lower case 
letters - it is intentionally):

:

module 1

module 2

...

...

MY_DJANGO:

MY_DJANGO:

__init__.py

settings.py

urls.py

wsgi.py

my_django:

migrations

__init__.py

admin.py

apps.py

models.py

tests.py

views.py

__init__.py

manage.py
 
in models.py I've added:

import os
import django
os.environ["DJANGO_SETTINGS_MODULE"] = "MY_DJANGO.MY_DJANGO.settings"
django.setup()

before the models import from django.db.

in manage.py, in the main

os.environ.setdefault("DJANGO_SETTINGS_MODULE", "MY_DJANGO.settings")

was auto generated by Django 

in settings.py, in INSTALLED_APPS:

INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'django.contrib.sites',
'django.contrib.admindocs',

==>>>>'MY_DJANGO.my_django', or 'my_django', <<<<= Here is the 
problem

]


Problem description:

if I use 'MY_DJANGO.my_django' in INSTALLED_APPS then running 'python 
manage.py check' command yields:

 ImportError: No module named MY_DJANGO.settings


 

and if I use 'my_django' in INSTALLED_APPS then I have an import error 
while importing models:

 from MY_DJANGO.my_django import models (in some file) yields:

ImportError: No module named my_django 


Also tried to add  ''my_django.apps.MyDjangoConfig' to INSTALLED_APPS, and 
it didn't helped.

What am I doing wrong??

Thanks in advance,
Alex.

 






 

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/bb9251bb-7bce-4eec-b8ac-90b031db1284%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What's the simple way to implement a chat system in Django?

2017-10-05 Thread Alex Chiaranda

is use Firebase for the chat part an option ?

On Monday, October 2, 2017 at 12:39:48 PM UTC-3, Kishore Srinivas wrote:
>
> I want to make a chat system in Django, but all those channel stuffs looks 
> difficult , so are there any other simpler way to implement a chat system, 
> thanks 
>

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/370e7172-268c-480d-a80f-b48eb930eaef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

{% csrf_token %}

2017-09-26 Thread Alex Kleider

I'm using test driven development (going through Harry J.W. Percival's 
book) and have found that the following code fails because the template tag 
( {% csrf_token %} ) is rendered by the home_page view function but not by 
the django.template.loader.render_to_string function (and so the 
assertEqual test fails.)

...templates/home.html:
...

 
{% csrf_token %}
 
...

Testing code:

def test_home_page_returns_correct_html(self):
request = HttpRequest()
response = home_page(request)
returned_html = response.content.decode()
expected_html = render_to_string('home.html')
self.assertEqual(returned_html , expected_html)

returned_html and expected_html are the same except that returned_html 
contains the following line (and the other doesn't:)

Infact, expected_html doesn't even contain the
{% csrf_token %}
line.

Can anyone suggest a work around?
Thanks in advance.

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c424de1a-4866-4f29-b93f-c06f46651ea2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django Channels compatibility with Google App/Compute Engine?

2017-07-07 Thread Alex Z

Hello! I'm really new here, and also relatively new to Django, and I've
been researching different ways to incorporate real-time updates with
Django without specifically using AJAX. I dug around and found out about
Django Channels, and I'm learning the basics right now. What I'm trying to
do is develop a card game app, and I wanted each player to be able to play
a card on their computer, and it would show up for everyone else playing
(on different computers) without refreshing the page. I think I can figure
something out to accomplish this with Django Channels, but I have a
different issue: is Django Channels easily compatible with Google
App/Compute Engine? I want to deploy it using Google Compute Engine, but I
couldn't find many resources on the topic or any that answered my
questions. For example, how would I deploy my Django app with a specific
channel layer (Redis, RabbitMQ, etc.)? What other precautions should I take
before I deploy a Django project that uses Channels? Any input on this
would be fantastic, even any information on deploying a Django project that
uses Channels via Google Compute Engine. Thanks!

--
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/4d38a789-ee1a-4127-95ef-8420e57621f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Google analytics and request.resolver_match.url_name

2017-07-07 Thread Alex Riina

I'm getting familiar with google analytics and stumbled 
upon 
https://developers.google.com/analytics/devguides/collection/analyticsjs/pages#modifying_page_urls
 
in which the google docs recommend regexing out some unique ids. In django, 
it's a lot simpler to get something like /user/account/ from 
/user/USER_ID/account/ by using

  ga('set', 'page', "{{ request.resolver_match.url_name }}");


Is there any reason I should rethink that?

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/17291c67-0126-4e1a-a497-50846b9eeed0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Catching errors inside transaction.atomic()

2017-06-13 Thread Alex Krupp

The Django documentation gives a warning

to avoid catching errors inside transaction.atomic() blocks, and to use
nested transactions if you need to do so. But in the case where we have
code like:

with transaction.atomic():
# Create and save some models here

try:
SomeModel.objects.get(id=NON_EXISTENT_ID)
except SomeModel.DoesNotExist:
raise SomeCustomError()

Will anything bad actually happen if we just immediately raise a custom
error without doing any other error handling? The expected behavior in this
case would be that the entire transaction gets rolled back, and so nothing
before or after the exception is committed.

I'm just wondering in cases like these there is any reason for using the
recommended nested transaction, or if it's just extra code that's not
serving any purpose. The examples only speak to cases where there is there
would otherwise be database queries getting executed in between the first
database error and the end of the transaction, which isn't the case 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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/8765cfc1-6083-4f6e-8f86-ace888a0ad21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Should I store offline calculation results in the cache?

2017-05-27 Thread Alex Heyden

Seven years ago, that may very well have been a true statement. I wouldn't
stand by it today. Disk caching should be perfectly stable, even if it's a
pretty poor solution for the average use case.

The part that hasn't changed is memcached. Memcached should be everyone's
default caching solution, not just on Django, but everywhere. You use
memcached until you've proven you have a use case that makes memcached
explicitly the wrong choice, and even then, you have someone else sanity
check your assumptions.

On Sat, May 27, 2017 at 9:17 AM, Alexandre Pereira da Silva <
aletes@gmail.com> wrote:

> Redis caching is a good solution for this. You can have persistence, it's
> fast and only limited by your available RAM.
>
> Your implementation should be more robust about missing itens from the
> cache. If for any reason the cache is lost, your code should rebuild the
> values in a background task.
>
>
>
> On Sat, May 27, 2017 at 6:25 AM, Antonis Christofides <
> anto...@djangodeployment.com> wrote:
>
>> Hello all,
>>
>> I have an application that calculates and tells you whether a specific
>> crop at a specific piece of land needs to be irrigated, and how much. The
>> calculation lasts for a few seconds, so I'm doing it offline with Celery.
>> Every two hours new meteorological data comes in and all the pieces of land
>> are recalculated.
>>
>> The question is where to store the results of the calculation. I thought
>> that since they are re-creatable, the cache would be the appropriate place.
>> However, there is a difference with the more common use of the cache: they
>> are re-creatable, but they are also necessary. You can't just go and delete
>> any item in the cache. This will cripple the website, which expects to find
>> the calculation results in the cache. Viewing something on the site will
>> never trigger a recalculation (and if I make it trigger, it will be a
>> safety procedure for edge cases and not the normal way of doing things).
>> The results must also survive reboots, so I chose the file-based cache.
>>
>> I didn't know about culling, so when the pieces of land grew to 100, and
>> the items in the cache to 400 (4 items need to be stored for each piece of
>> land), I spent a few hours trying to find out what the heck is going on. I
>> solved the problem by tweaking the culling parameters. However all this has
>> raised a few issues:
>>
>>1. The filesystem cache can't grow too much because of issue 11260
>>, which is marked
>>wontfix. According to Russell Keith-Magee
>>,
>>
>> "the filesystem cache is intended as an easy way to test caching, not as
>> a serious caching strategy. The default cache size and the cull strategy
>> implemented by the file cache should make that obvious. If you need a cache
>> capable of holding 10 items, I strongly recommend you look at memcache.
>> If you insist on using the filesystem as a cache, it isn't hard to subclass
>> and extend the existing cache."
>>
>> If these comments are correct, then the documentation needs some fixing,
>> because not only does in not say that the filesystem cache is not for
>> serious use, but it implies the opposite:
>>
>> "Without a really compelling reason, ... you should stick to the cache
>> backends included with Django. They’ve been well-tested and are easy to
>> use."
>>
>> Is Russell not entirely correct perhaps, or is the documentation? Or am I
>> missing something?
>>
>>
>>1. In the end, is it a bad idea to use the cache for this particular
>>case? I also have a similar use case in an unrelated app: a page that 
>> needs
>>about a minute to render. Although I've implemented a quick-and-dirty
>>solution of increasing the web server's timeout and caching the page, I
>>guess the correct way would be to produce that page offline with Celery or
>>so. Where would I store such a page if not in the cache?
>>
>> --
>> Antonis Christofideshttp://djangodeployment.com
>>
>> --
>> 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 django-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/django-users/a5a8d1ab-f4e0-a6b5-b1da-acc9dc2dbf9d%40djan
>> godeployment.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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
>

Re: Django Channels, Nginx, Daphne - Not working?

2017-05-04 Thread Alex Elson

I was able to get it working with the development server, python manage.py 
runserver, with an addition to the firewall on Google Cloud.

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/78173b95-e0a3-4930-8cec-581d36784671%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django Channels, Nginx, Daphne - Not working?

Here is my nginx default configuration if that could be it.

server {
listen 80 default_server;
listen [::]:80 default_server;

root /var/www/html;
charset utf-8;

index index.html index.htm index.nginx-debian.html;

server_name _;

location / {

proxy_pass http://localhost:8000;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
try_files $uri $uri/ =404;
}
}

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/75667dd1-2d00-494c-997c-e6754b46b633%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django Channels, Nginx, Daphne - Not working?

I am trying to only use Daphne for websockets  I believe, following the 
deployment tutorial in the Channel documentation. And yes I am running both 
processes on the same machine. 

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/75ecc3b4-1564-47a3-bcf9-e7926e05a290%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django Channels, Nginx, Daphne - Not working?

I have  "socket = new Websocket("ws:// ...", "socket.onopen," and 
"socket.send" commands in my Javascript code, and although the Javascript 
works, it seems to not be able to run these commands, or it is unable to 
access my functions in consumer.py, althought it works flawlessly if I run 
my project locally.

-- 
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 django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/f9bc1728-d281-4245-8960-42c1770f8281%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django Channels, Nginx, Daphne - Not working?