Re: Django models in file sharing system

[Mike Dewhirst]

On 11/12/2015 5:00 AM, Vasu Dev Garg wrote:

models.py :

 `class Document(models.Model):
     docfile = models.FileField(upload_to='documents/%Y/%m/%d')
     user = models.ForeignKey(User, null=False, blank= False)
`


I have created a model for file upload as shown above. docfile is the
field that represents file to be uploaded and user field stores the name
of the user that is uploading the file.I want the additional fields so
that file uploaded is visible to the ones with whom it has been shared.
Tell me the fields for achieving the sharing task.


Maybe you should use a ManyToManyField so many users may be linked to 
any Document.


https://docs.djangoproject.com/en/1.8/ref/models/fields/#manytomanyfield

eg sharing = models.ManyToManyField('User')




--
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/84c40695-9652-443a-98d0-b5d416f673ea%40googlegroups.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 email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/566A1A35.9030701%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Re: What will be the replacement for .extra()?

[Dan Stephenson]

Following is worth a watch

https://opbeat.com/events/duth/#expressions


On Thursday, 10 December 2015 21:22:39 UTC, thinkwell wrote:
>
> So how would an query like this be written, with the new Query Expression 
> API? Where a count of events by day is required but the date column is 
> datetime?
>
> Triggers.objects.all().extra({"day": "date_trunc('day', date)"}).
> values_list('name', 'severity', 'day').annotate(total=Count('severity'))
>
>
>
>
>
> On Wednesday, December 9, 2015 at 8:07:28 PM UTC-5, Russell Keith-Magee 
> wrote:
>>
>> Hi Luis,
>>
>> On Thu, Dec 10, 2015 at 7:10 AM, Luis Masuelli  
>> wrote:
>>
>>> When I see the docs (
>>> https://docs.djangoproject.com/en/1.8/ref/models/querysets/#extra), I 
>>> notice .extra will be deprecated and removed. Is there a plan for the 
>>> replacement? As I see it, limiting ourselves to using Manager.raw() is not 
>>> a good idea, since you cannot work anymore on a RawQueryset object (as you 
>>> can work on any Queryset object you called .extra). So my question is: Is 
>>> there a good replacement for .extra being planned?
>>>
>>
>> Yes - the Query Expression API.
>>
>> https://docs.djangoproject.com/en/1.9/ref/models/expressions/
>>
>> Yours,
>> Russ Magee %-)
>>
>>

-- 
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ec4072cf-65d5-4a9d-9afb-8362b3857de6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What will be the replacement for .extra()?

[thinkwell]

So how would an query like this be written, with the new Query Expression 
API? Where a count of events by day is required but the date column is 
datetime?

Triggers.objects.all().extra({"day": "date_trunc('day', date)"}).values_list
('name', 'severity', 'day').annotate(total=Count('severity'))





On Wednesday, December 9, 2015 at 8:07:28 PM UTC-5, Russell Keith-Magee 
wrote:
>
> Hi Luis,
>
> On Thu, Dec 10, 2015 at 7:10 AM, Luis Masuelli  > wrote:
>
>> When I see the docs (
>> https://docs.djangoproject.com/en/1.8/ref/models/querysets/#extra), I 
>> notice .extra will be deprecated and removed. Is there a plan for the 
>> replacement? As I see it, limiting ourselves to using Manager.raw() is not 
>> a good idea, since you cannot work anymore on a RawQueryset object (as you 
>> can work on any Queryset object you called .extra). So my question is: Is 
>> there a good replacement for .extra being planned?
>>
>
> Yes - the Query Expression API.
>
> https://docs.djangoproject.com/en/1.9/ref/models/expressions/
>
> Yours,
> Russ Magee %-)
>
>

-- 
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7947a3c2-b011-4cd5-b307-5bb32fc101ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to add myself as a developer for hire in the wiki?

[Tim Graham]

Feel free to remove such entries if you like.

On Wednesday, December 9, 2015 at 1:40:58 PM UTC-5, larry@gmail.com 
wrote:
>
> On Wed, Dec 9, 2015 at 7:41 AM, Tim Graham  > wrote: 
> > You can login using a Trac or GitHub account, then click "Edit this 
> page" at 
> > the bottom of the page. 
> > 
> > On Wednesday, December 9, 2015 at 5:47:42 AM UTC-5, James Lin wrote: 
>
> A lot of links on that page are bad, and give a 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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8b732d71-546b-435f-9fc5-08a35e74a9f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Tests not passing in suite but pass individually

[Tim Graham]

I didn't see any indication in your previous posts that you were using 
database routers. That's why I continue to ask for a sample project - it's 
difficult to debug problems without seeing the entire picture.

On Wednesday, December 9, 2015 at 2:33:20 PM UTC-5, learn django wrote:
>
> After making following change & pointing router to 'default' database test 
> case is passing.
>
> 'default': {
> # 'ENGINE': 'django.db.backends.sqlite3',
> # 'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
> 'ENGINE': 'django.db.backends.postgresql_psycopg2',
> 'USER': 'postgres',
> 'NAME': '*mydb*',
> 'PASSWORD':'0212',
> 'HOST':'localhost',
> 'PORT':'',
> 'TEST': {
>'NAME': '*mytestdb*',
> },
> },
>
> However if I make router to point to app specific db which is defined as 
> follows,
> the test case still fails. I think its better not to keep on modifying the 
> router.
>
> Is there anything wrong with the app database definition below.
>
> 'orca': {
> 'ENGINE': 'django.db.backends.postgresql_psycopg2',
> 'NAME': '*orcadb*',
> 'USER':'postgres',
> 'PASSWORD':'0212',
> 'HOST':'localhost',
> 'PORT':'',
> 'TEST': {
>'NAME': '*orcatestdb*',
> },
> }
>
>
> On Wednesday, December 9, 2015 at 4:44:14 AM UTC-8, Tim Graham wrote:
>>
>> It seems a bit suspicious that you're using the same database name for 
>> ['default']['NAME'] and ['default']['TEST']['NAME'] -- is that intentional?
>>
>> On Tuesday, December 8, 2015 at 8:30:05 PM UTC-5, learn django wrote:
>>>
>>> Hi Tim,
>>>
>>> My test case was working with new app in new project which was
>>> using default database.
>>>
>>> DATABASES = {
>>> 'default': {
>>> 'ENGINE': 'django.db.backends.sqlite3',
>>> 'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
>>> }
>>> }
>>>
>>> So I went back to my old app and debugged a bit.
>>> If I make following changes in Database dictionary (commenting the 
>>> bolded test) and
>>> make my router for this app to point to default database the tests pass.
>>> Is it because am using postgres that this issue is seen ?
>>>
>>> DATABASES = {
>>> 'default': {
>>>   *  'ENGINE': 'django.db.backends.sqlite3',*
>>> *'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),*
>>> *#'ENGINE': 'django.db.backends.postgresql_psycopg2',*
>>> *#'USER': 'postgres',*
>>> *#'NAME': 'testdb',*
>>> *# 'PASSWORD':'v1ptela0212',*
>>> *# 'HOST':'localhost',*
>>> *# 'PORT':'',*
>>> *#'TEST': {*
>>> *#'NAME': 'testdb',*
>>> *#},*
>>> },
>>> 'sztp': {
>>> 'ENGINE': 'django.db.backends.postgresql_psycopg2',
>>> 'NAME': 'sztpdb',
>>> 'USER':'postgres',
>>> },
>>> 'orca': {
>>> 'ENGINE': 'django.db.backends.postgresql_psycopg2',
>>> 'NAME': 'orcadb',
>>> 'USER':'postgres',
>>> }
>>> }
>>>
>>>
>>> On Wednesday, December 2, 2015 at 4:18:25 PM UTC-8, learn django wrote:

 Will try to send minimal project by end of the day.
 Hopefully I can discover the reason during this exercise.

 On Wednesday, December 2, 2015 at 3:33:30 PM UTC-8, Tim Graham wrote:
>
> It looks correct. I'd like a minimal project I could download to 
> reproduce the issue. In putting that together, you might discover the 
> reason for the failure.
>
> On Wednesday, December 2, 2015 at 6:29:07 PM UTC-5, learn django wrote:
>>
>> Below is the test file & logs.
>> No matter in which order (using --reverse) I run the suite it fails.
>> The database backend is postgres. Is that an issue ?
>>
>> File:-
>> ===
>> import datetime
>> import pdb
>>
>> from rest_framework import status
>> from rest_framework.test import APIClient
>>
>> from django.http import HttpRequest
>> from django.contrib.auth.models import User
>> from django.utils import timezone
>> from django.test import TestCase
>>
>> from orca.models import *
>>
>> import orca.handlers.customer_handler as ch
>>
>> # Create your tests here.
>> class OrcaTestCase(TestCase):
>>
>> def test_customer_create_modify_delete(self):
>> '''Test customer object create, modify and delete operations 
>> in  DB.'''
>> # Create.
>> CustomerDb.objects.create(c_name='Zoo', c_role='Admin',
>>   c_date_created=timezone.now(),
>>   c_date_updated=timezone.now())
>> customer_list = CustomerDb.objects.all()
>> self.assertEqual(len(customer_list), 1)
>>
>> def test_launch(self):
>> '''Test launch.'''
>> CustomerDb.objects.create(c_name='Foo', c_role='Admin',
>>   

Multiple serializers

[miguel angel lopez mendo]

i have this serializers 

class ValuarCoche(serializers.ModelSerializer):
class Meta:
model = Valuacion
depth = 6
fields = ('coche','Precio_Venta','Precio_Compra')

class CocheSerializer2(serializers.ModelSerializer):
valuacion = ValuarCoche(many=True)
class Meta:
model = Coche


fields = ('id', 'marca', 'modelo', 'version', 
'estado','anio','timestamp','valuacion')


but don't work  i need that print 


{
"id": 3,
"marca": {
"id": 1,
"nombre": "Acura"
},
"modelo": {
"id": 1,
"nombre": "ILX"
},
"version": "a5",
"estado": "1",
"anio": 2015,
"timestamp": "2015-12-08T19:12:05.887126Z"

 "Precio_Venta": 0,

"Precio_Compra": 0

},



the error is the next 



-- 
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8e1a6157-63d4-4cbb-9df0-ad637202c72c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django models in file sharing system

[Vasu Dev Garg]

models.py :

 `class Document(models.Model):
 docfile = models.FileField(upload_to='documents/%Y/%m/%d')
 user = models.ForeignKey(User, null=False, blank= False)
`


I have created a model for file upload as shown above. docfile is the field 
that represents file to be uploaded and user field stores the name of the 
user that is uploading the file.I want the additional fields so that file 
uploaded is visible to the ones with whom it has been shared. Tell me the 
fields for achieving the sharing task.

-- 
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/84c40695-9652-443a-98d0-b5d416f673ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Prevent field from becoming null

[monoBOT]

The default is simply the default value, the user can still delete it.

You can control how the user enters the values in the form, in particular
on the clean_atribute method or redefining the clean one inherited from
 the forms.ModelForm class

If your want to be "hacky" you can rewrite the save method in the model and
there control if what the user enters is not of your appeal, but then you
are cheating arent you?

2015-12-10 13:26 GMT+00:00 Samuel Muiruri :

> Hello,
> I want to override the save for the show model so I check for if the value
> passed for a field is null if so ignore saving for the field
>
> class Shows(models.Model):
> some_field = models.CharField(max_length=128, default="something")
>
> def save(self, *args, **kwargs):
> super(Show, self).save()
>
>
>
> --
> 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 http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/c31be361-21f1-45c9-8257-78b56bf45c78%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*monoBOT*
Visite mi sitio(Visit my site): monobotsoft.es/blog/

-- 
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CA%2BxOsGCOqRrXxKEfDZM5Lome8cxLGcmUX3cwoo18BD1f%3DP1UAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django for Data Tables to group by when coloumn hidden

[Carsten Fuchs]

Hi Sid,

if with Data Tables you are in fact referring to http://datatables.net/, then you should 
put your questions with the folks over there. I guess what you want is possible with 
DataTables (I haven't checked), but be prepared for some customization with JavaScript 
being required.


If you want to solve the problem in pure Django (that is, with no JavaScript help on the 
client), I would probably create two different views, one for the table with and the 
other without the second column. The docs at 
https://docs.djangoproject.com/en/1.9/topics/db/aggregation/ explain very well the 
concepts that you need in order to build the table with the second column collapsed.


Best regards,
Carsten



Am 09.12.2015 um 16:07 schrieb Sid:

*Question:* I have a Data table displaying on django , but now I like to group 
by when
ever I will hide the column.


*column1 column2 column3*

AAACAD25

AAAUSD12

BBBCAD13

BBBUSD16

CCCCAD11

CCCUSD18


The above table will be displayed on web page using Django, now when ever I hide
*column2* It should group by and display like below table.


*column1* *column3*

AAA  37

BBB  29

CCC  39


when ever I unhide it again it should display same as first table again.

*can anyone tell me there is any possible way to do it.*


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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5669B63A.3050301%40cafu.de.
For more options, visit https://groups.google.com/d/optout.

Prevent field from becoming null

[Samuel Muiruri]

Hello,
I want to override the save for the show model so I check for if the value 
passed for a field is null if so ignore saving for the field

class Shows(models.Model):
some_field = models.CharField(max_length=128, default="something")

def save(self, *args, **kwargs):
super(Show, self).save()



-- 
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c31be361-21f1-45c9-8257-78b56bf45c78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Prevent field from becoming null

[Samuel Muiruri]

Hello,
I want to override the save for the show model so I check for if the value 
passed for a field is null if so ignore saving for the field

class Shows(models.Model):
some_field = models.CharField(max_length=128, default="something")

def save(self, *args, **kwargs):
super(Show, self).save()



-- 
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/48a95f77-ac39-42a3-81f7-11651e8d742c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Custom date format stopped working in template

[Fabio C. Barrionuevo da Luz]

This is a bug that will be fixed in the next bugfix release django (1.8.8)

https://docs.djangoproject.com/en/1.9/releases/1.8.8/#bugfixes



2015-12-10 3:26 GMT-03:00 sandino :

> Hello,
>
> I have custom localized data formats (
> https://docs.djangoproject.com/en/1.8/topics/i18n/formatting/#creating-custom-format-files
> ) that I use in my template. After upgrading to 1.8.7 it stopped working
> (it shows something like
> 0MarchSunMarchX_th00+RUTC_SunAMUTCMarchUTC0MarMarch_March+RMarAMUTC).
> I think it has to do with this fix
> https://docs.djangoproject.com/en/1.8/releases/1.8.7/#fixed-settings-leak-possibility-in-date-template-filter
>
> My directory structure (there are few other languages besides):
>
> /project
>   __init__.py
>   /project_app
> __init__.py
> /formats
>   __init__.py
>   /en
> __init__.py
> formats.py
>
> formats.py:
>
> INDEX_SHORT_DATETIME_FORMAT = 'm/d H:i'
>
>
> settings.py:
>
> FORMAT_MODULE_PATH = ['myapp.formats']
>
>
>
> Is it a bug or my mistake?
>
> --
> 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 http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/dd554709-8283-4dc9-ae4c-d2168a3096f6%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Fábio C. Barrionuevo da Luz
Palmas - Tocantins - Brasil - América do Sul

http://pythonclub.com.br/

Blog colaborativo sobre Python e tecnologias Relacionadas, mantido
totalmente no https://github.com/pythonclub/pythonclub.github.io .

Todos são livres para publicar. É só fazer fork, escrever sua postagem e
mandar o pull-request. Leia mais sobre como publicar em README.md e
contributing.md.
Regra básica de postagem:
"Você" acha interessante? É útil para "você"? Pode ser utilizado com Python
ou é útil para quem usa Python? Está esperando o que? Publica logo, que
estou louco para ler...

-- 
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAPVjvMZEWD_vCr%3DBx7z2BZJ5LUZ2bUtiqnHEeSssTRjTnPcZrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Custom date format stopped working in template

[sandino]

Hello,

I have custom localized data formats 
( 
https://docs.djangoproject.com/en/1.8/topics/i18n/formatting/#creating-custom-format-files
 
) that I use in my template. After upgrading to 1.8.7 it stopped working 
(it shows something like 
0MarchSunMarchX_th00+RUTC_SunAMUTCMarchUTC0MarMarch_March+RMarAMUTC). 
I think it has to do with this 
fix 
https://docs.djangoproject.com/en/1.8/releases/1.8.7/#fixed-settings-leak-possibility-in-date-template-filter

My directory structure (there are few other languages besides):

/project
  __init__.py
  /project_app
__init__.py
/formats
  __init__.py
  /en
__init__.py
formats.py

formats.py:

INDEX_SHORT_DATETIME_FORMAT = 'm/d H:i'


settings.py:

FORMAT_MODULE_PATH = ['myapp.formats']



Is it a bug or my mistake?

-- 
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/dd554709-8283-4dc9-ae4c-d2168a3096f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: get all current active connected users

[Jani Tiainen]

Hi,

That last login field only applies when user really logs in. (IOW you 
call login() function from django.contrib.auth). After that user is 
persisted to session so there is no need to authenticate per request.


Now if you have longer sessions than 24 hours user will stay logged in 
(I think default session TTL is 2 week after last modification). So that 
would still give troubles that users may have been active in last few 
seconds but not logged in for a few days.


On 09.12.2015 15:37, Jon Ribbens wrote:

On Wednesday, 9 December 2015 12:55:22 UTC, Jani Tiainen wrote:

This is really problematic domain since as you know, Django works
on HTTP request-response cycle. After cycle is finished there is
absolutely no way to know "who is logged on".

So first you have to determine factors that make up "currently
active user". Then you have to track that information somehow and
after that it's possible to gather a list of active/inactive users.


Users have a last_login field so you could easily say "users who have 
logged in in the last 24 hours" or whatever.

--
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7c5f0620-c094-4667-b474-82a23f432fa1%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--

Jani Tiainen

--
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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/566944D0.9020204%40gmail.com.
For more options, visit https://groups.google.com/d/optout.