Create an OAuth2 Client Application problem

2014-12-30 Thread Hossein Rashnoo
Hi
I follow this tutorial and here 

 i 
got error. when i try to access http://localhost:8000/o/applications/ its 
redirect to  http://localhost:8000 
/accounts/login/?next=/o/applications/ 
and django 404 error appear that tells:
The current URL, accounts/login/, didn't match any of these.
Please help me.

-- 
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/d1d60238-c0f0-4704-b41d-5d8224ca5da5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Can't save input to database

2014-12-30 Thread Vijay Khemlani
the code sample links are broken :(

On Tue, Dec 30, 2014 at 4:59 PM, Thomas Lockhart 
wrote:

>  On 12/30/14 11:42 AM, Ronis wrote:
>
> Hi guys, I can't save the input from a custom form to database. I don't
> know what I am missing.
>
> I'm not sure either. But the html form you posted looks a *lot* like any
> template you might find in a django deployment. If it were me I'd look
> harder at just tying that in to the "usual places" and be done with it.
> That will give you form validation etc nearly for free and save the next
> person who is looking at your code from having to figure out what you did.
> Patterns and idioms save a lot of thinking best used elsewhere...
>
> hth
>
> - Tom
>
>
>
>  Because it's using a downloaded template from the web, I'm not using the
> django forms. Instead, I'm trying to simply save the input from the html
> form to the database. Im using the standard database when you create a
> django project. When I checked the admin the inputs are not saved.
>
>  Here is my code:
>
>
>  Views.py -> https://dpaste.de/SCBi
>
>  Models.py -> https://dpaste.de/3NX3
>
>  Admin.py -> https://dpaste.de/OWLS
>
>  htmlform -> https://dpaste.de/11DP
>
>  I'm a newbie programmer btw, this may be simple solution but I've spent
> some time and couldn't figure it out =/
>  --
> 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/ca13d351-0075-4000-902d-3f8755cb775e%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/54A3043E.10401%40gmail.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/CALn3ei1RG_QOb4%3DDuCz1rhejp3d5c3OWBWLg_bA0hJzJhx_OmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: delete OnetoOneField link

2014-12-30 Thread madjardi
thank you. you give me more confidence

вторник, 30 декабря 2014 г., 17:19:53 UTC+3 пользователь Vijay Khemlani 
написал:
>
> If you want to change a user's cashbox then yes, you would need to use 
> your solution, but it's easier to get c1 by just saying
>
> c1 = user.cashbox
>
> instead of Cashbox.objects.get
>
> A more definite solution would be to add the OneToOne relation to the User 
> model instead of the Cashbox object, but I'm not sure how that works in 
> your project.
>
> On Tue, Dec 30, 2014 at 6:56 AM, madjardi  > wrote:
>
>> class Cashbox(models.Model):
>> cashier = models.OneToOneField('User', null=True, blank=True, 
>> related_name='cashbox', on_delete=models.SET_NULL)
>>
>> in other code:
>> User.object.get(pk=1)
>> user.cashbox = None
>>
>> AttributeError: 'NoneType' object has no attribute 'cashier_id'
>>
>> one version solving is:
>> c1 = Cashbox.objects.get(pk=user.cashbox.id)
>> c1.cashier = None
>> c1.save()
>>
>>
>> c2 = Cashbox.object.get(pk=10)
>> c2.cashier = user
>> c2.save()
>>
>>
>> i need get other Cashbox to set link None. Why i need do so. is there a 
>> better solution.
>>
>> -- 
>> 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 http://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/9bac63fa-64e3-4353-82ae-6b31fa8f281f%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/4f327604-9cf0-4ba2-95f4-e2f116f75867%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Can't save input to database

2014-12-30 Thread Thomas Lockhart

On 12/30/14 11:42 AM, Ronis wrote:
Hi guys, I can't save the input from a custom form to database. I 
don't know what I am missing.
I'm not sure either. But the html form you posted looks a *lot* like any 
template you might find in a django deployment. If it were me I'd look 
harder at just tying that in to the "usual places" and be done with it. 
That will give you form validation etc nearly for free and save the next 
person who is looking at your code from having to figure out what you 
did. Patterns and idioms save a lot of thinking best used elsewhere...


hth

- Tom



Because it's using a downloaded template from the web, I'm not using 
the django forms. Instead, I'm trying to simply save the input from 
the html form to the database. Im using the standard database when you 
create a django project. When I checked the admin the inputs are not 
saved.


Here is my code:


Views.py -> https://dpaste.de/SCBi

Models.py -> https://dpaste.de/3NX3

Admin.py -> https://dpaste.de/OWLS

htmlform -> https://dpaste.de/11DP

I'm a newbie programmer btw, this may be simple solution but I've 
spent some time and couldn't figure it out =/

--
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/ca13d351-0075-4000-902d-3f8755cb775e%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/54A3043E.10401%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Can't save input to database

2014-12-30 Thread Ronis
Hi guys, I can't save the input from a custom form to database. I don't 
know what I am missing. 

Because it's using a downloaded template from the web, I'm not using the 
django forms. Instead, I'm trying to simply save the input from the html 
form to the database. Im using the standard database when you create a 
django project. When I checked the admin the inputs are not saved. 

Here is my code: 


Views.py -> https://dpaste.de/SCBi

Models.py -> https://dpaste.de/3NX3

Admin.py -> https://dpaste.de/OWLS

htmlform -> https://dpaste.de/11DP

I'm a newbie programmer btw, this may be simple solution but I've spent 
some time and couldn't figure it out =/ 

-- 
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/ca13d351-0075-4000-902d-3f8755cb775e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django App for synchronizing File upload

2014-12-30 Thread Collin Anderson
Hi,

There are a bunch of modules list here that should do what you want.
https://www.djangopackages.com/grids/g/ajax-file-uploading/

Collin

On Monday, December 29, 2014 10:45:54 AM UTC-5, Abdulhakim Haliru wrote:
>
> Hello Guys,
>
>
> Here is my requirements.. I need to upload heavy files to a django app. 
> the users should be able to sync the file upload in the background. 
>
> This technique can be seen in file sharing services like 4shared and 
> dropbox. I know java is the way to go but I am wondering if something like 
> that is obtainable with django or any other python module?
>
> 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 http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2985b5ed-217d-4bd8-b521-f181c543ab53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Bristol (UK) startup seeks awesome Python/Django engineer

2014-12-30 Thread Joseph Edwards
## Summary

Small startup in Bristol currently looking for an awesome software engineer 
to work on our existing code base.

Ideally you'd be located in Bristol/Bath and be able to work from our 
office, or be able to visit our offices on a weekly basis, but remote/home 
working is also negotiable. You would have prior experience of working for 
a small startup and/or handling all technical aspects of building a tech 
product. 

Our product is similar to Launch27, allowing customers to book a product, 
which is then allocated to groups within our workforce, and the lifecycle 
of a job is handled via our backend systems. This is not your typical 
boring Django integration job, there are some mundane parts but overall you 
should find this work quite pleasant.

Reply with why you think this role is interesting, and talk about any 
relevant experience you have with the technologies mentioned. Provide 
github links, code examples (gist/github/pastebin etc only pls, don't 
attach files), and anything else that makes you stand out from the rest. 
Interview would consist of a 1 hour phone call, and a decision made 
same/following day. Earliest start date would be 5th Jan.

## Tech specs

Stack: Python, Django, CircleCI, Github, DigitalOcean, Docker, MongoDB, 
Percona MySQL, Sentry, New Relic, LogEntries, Twilio, Slack, Vagrant, 
Trello, Stripe, TDD, Redis, RQ, CloudFlare, Python libs: 
django-debug-toolbar, freezegun, python-requests, freezegun, 
django-devserver, mongoengine, rq, django-rq

Primarily this is a Python role extended an existing API backend. We have 
complete separation between backend and frontend to ensure modularity and 
other developers working on the frontend. In future, we will have mobile 
integrations so it's absolutely imperative that the API is decoupled.

You may need to do other devops/research stuff, such as debugging prod 
instances, fixing memory leaks, diagnosing outages, settings up servers, 
fixing DNS, repairing build systems and all the other stuff that goes 
around a project.

All existing code follows TDD principles, has extensive commenting and is 
overall fairly clean, but with room for improvement on some of the core 
modules. Comes with CI build testing using Circle and ready to go Vagrant 
scripts. Our unit tests use time travel via freezegun, this allows us to 
test date/time sensitive functionality by means of monkeypatching. For 
example, ensuring that a subscription is terminated if a payment cannot be 
taken after 7 days. Every single piece of logic can be unit tested using a 
single command, and a full test suite takes around 60 seconds (not incl 
dependancies).

Ideal candidate would understand the importance of TDD, have good all-round 
knowledge of Python, and know their way around Django. You should 
understand the following without too much problem;

* How objects/classes works in Python (metaclasses, MROs etc would be a 
bonus)
* Python syntax (operators, list comprehensions, lambdas etc)
* Python stdlibs (itertools, os, sys, urllib etc)
* Stripe API for handling payments, invoices etc
* Job queues using rq/redis
* Document store using MongoEngine
* Demonstrate good understanding of what it means to be a software engineer
* Good knowledge of our stack

-- 
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/09dd12a3-86cc-4ca8-a392-b0bede493f26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django vs ExtJS

2014-12-30 Thread Frank Bieniek
 
Hi Joris,
some of the best arguments for python + django, 
you could find here - :

https://www.paypal-engineering.com/2014/12/10/10-myths-of-enterprise-python/
...
One language in particular has both a long history at eBay and PayPal and a 
growing mindshare among developers: *Python *.
...


Thanks
Frank

Am Dienstag, 30. Dezember 2014 11:44:20 UTC+1 schrieb Joris Benschop:
>
> Thank you both for these answers. Personally Im already convinced of 
> Django, but the trick is to convince others. The strong benefit of java is 
> that it is really easy to hire senior java developers on a consultancy 
> basis. For django it is not so simple, especially when the requirement is 
> to have these devs on-site (.nl / .be area).
>
>
>
> Op 30 dec. 2014 om 11:36 heeft Ariel Calzada  > het volgende geschreven:
>
> DJANGO + Tastypie is your TEAM for REST Services, forget Java :)
>
> 2014-12-30 5:34 GMT-05:00 Guilherme Leal 
> :
>
>> Given your scenario, we can say that with django, you wouldn't have to 
>> worry about creating REST services. You would create only one service, and 
>> let django manage the backend switch (with db routers). If you build your 
>> service well, you would have an abstract REST view/url generator (tastypie 
>> for instance), and with a little bit of effort (REALLY little), you could 
>> serialize the resource structure (metadata) on the request, and let ExtJS 
>> read that structure to build your frontend. Of course, this aproach 
>> requires a little bit of cache (to save some time on the read 
>> structure/build html for ExtJS). With that, you would have to write 
>> basically only the models (and of course, any exceptional case that might 
>> occur). And if you use django 1.7+, you can LITTERALLY forget about db 
>> admin, since django handles the migrations as well.
>>
>> I've done basically the same thing with Django REST Framework and 
>> AngularJS for the frontend. Works like a charm, and with the business logic 
>> on the signals, reduces the dev time by 90%. And worls like a charm.
>>
>> Em Tue Dec 30 2014 at 06:47:19, Joris Benschop > > escreveu:
>>
>>  Thank you, this is already very helpful.
>>> Currently company policy is to create REST services in java for each 
>>> backend and use ExtJS to query and visualize the results. With DJango I'm 
>>> trying to combine these into one, whilst staying compatible by using 
>>> tastypie as a REST service (so ExtJS can connect to that).
>>>
>>> joris
>>>
>>>
>>>
>>> On 29-12-14 16:51, Guilherme Leal wrote:
>>>
>>> Sincerely, I can't see the ExtJS's Models as true models on an MVC (or 
>>> MVT for instance) context, since the only real uses I've seen of them is to 
>>> bind form controls to any "model like" (basically anything) structure. 
>>> Therefore, the best comparsion for the ExtJS would be AngularJS (this is my 
>>> point of view, I might be wrong on this one).
>>>
>>>  But if you REALLY want to compare them, I would say that the biggest 
>>> point that django excels ExtJS, is that ExtJS doesn't have any meaningfull 
>>> way to introspect your DB to build the models dynamically, and with django 
>>> you can. As an exemple, with django, you can build an app that read your DB 
>>> metadata and build everithing from there (basicaly models; the views and 
>>> templates you can build in a way that they can read everything on a given 
>>> standard).
>>>
>>>  If you provide more specific info about the project, maybe we can come 
>>> with some more concrete comparsions.
>>>
>>> Em Mon Dec 29 2014 at 12:56:05, Joris Benschop >> > escreveu:
>>>
>>>  Hi List,
  
  I;m a data maangement specialist in a rather large multinational. I'm 
 trying to push Django as a fast development framework for front-end 
 applications of our databases. Currently the company is focusing on Sencha 
 ExtJS and java solutions. Can you help me with pointers why Django is 
 better? The free-as-in-beer argument is not very convincing by itself. 

  Thanks
 Joris
  -- 
 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 http://groups.google.com/group/django-users.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/django-users/53e17853-9922-4f77-bf9a-4cea7d35ade3%
 40googlegroups.com 
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>  -- 
>>>
>>> You received this message because you are subscribed to a topic in the 
>>> Google 

Re: Error when change a CharField to IntegerField

2014-12-30 Thread Neto
before was empty, but I deleted the column and remade, thanks

Em terça-feira, 30 de dezembro de 2014 11h52min14s UTC-2, Neto escreveu:
>
> I changed a CharField to IntegerField and when I did ./manage.py migrate, 
> appeared the message on terminal:
>
> django.db.utils.ProgrammingError: column "rotulo" cannot be cast 
> automatically to type integer HINT:  Specify a USING expression to perform 
> the conversion.
>
> What is it?
>

-- 
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/9d3a5dae-2dc9-4654-a6c2-94e3eeb8bbe2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Error when change a CharField to IntegerField

2014-12-30 Thread Jorge Andrés Vergara Ebratt
Hi, did the column had previus non-integer data in it?

2014-12-30 8:52 GMT-05:00 Neto :

> I changed a CharField to IntegerField and when I did ./manage.py migrate,
> appeared the message on terminal:
>
> django.db.utils.ProgrammingError: column "rotulo" cannot be cast
> automatically to type integer HINT:  Specify a USING expression to perform
> the conversion.
>
> What is it?
>
> --
> 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/67d68cf4-4feb-4656-b8e0-2651f9e25830%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Jorge Andres Vergara Ebratt*
*#SoftwareDeveloper (Or at least trying to be)*
*@javebratt*
*facebook.com/javebratt *

-- 
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/CAAeX05HV5j6X1%2Bw7XvEJb1Sb4Sux3dNUZJrBUzfnP-_8-ap2ZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: delete OnetoOneField link

2014-12-30 Thread Vijay Khemlani
If you want to change a user's cashbox then yes, you would need to use your
solution, but it's easier to get c1 by just saying

c1 = user.cashbox

instead of Cashbox.objects.get

A more definite solution would be to add the OneToOne relation to the User
model instead of the Cashbox object, but I'm not sure how that works in
your project.

On Tue, Dec 30, 2014 at 6:56 AM, madjardi 
wrote:

> class Cashbox(models.Model):
> cashier = models.OneToOneField('User', null=True, blank=True,
> related_name='cashbox', on_delete=models.SET_NULL)
>
> in other code:
> User.object.get(pk=1)
> user.cashbox = None
>
> AttributeError: 'NoneType' object has no attribute 'cashier_id'
>
> one version solving is:
> c1 = Cashbox.objects.get(pk=user.cashbox.id)
> c1.cashier = None
> c1.save()
>
>
> c2 = Cashbox.object.get(pk=10)
> c2.cashier = user
> c2.save()
>
>
> i need get other Cashbox to set link None. Why i need do so. is there a
> better solution.
>
> --
> 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/9bac63fa-64e3-4353-82ae-6b31fa8f281f%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/CALn3ei3UMe1O64gjup_ZvTjuH%3D_JZfEfO%3D5%3DTOTmPVo7QHDHoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Error when change a CharField to IntegerField

2014-12-30 Thread Neto
I changed a CharField to IntegerField and when I did ./manage.py migrate, 
appeared the message on terminal:

django.db.utils.ProgrammingError: column "rotulo" cannot be cast 
automatically to type integer HINT:  Specify a USING expression to perform 
the conversion.

What is it?

-- 
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/67d68cf4-4feb-4656-b8e0-2651f9e25830%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to generate the docs with the new style?

2014-12-30 Thread Tim Graham
Unfortunately, the offline docs use an entirely separate layout/theme so 
the new styles would need to be copied manually over here: 
https://github.com/django/django/tree/master/docs/_theme/djangodocs

I think it's a non-trivial amount of work and tricky because we are using 
things like web fonts on the main site. It's not a high priority in my mind.

On Monday, December 29, 2014 7:33:57 PM UTC-5, Aliane Abdelouahab wrote:
>
> hi, i asked the question in SO but still nothing, can the devs share the 
> new style to the github repo?
> http://stackoverflow.com/questions/27673432/django-docs-with-the-new-style
>

-- 
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/fae04283-b00a-4428-bbc5-9de4ff4af57c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django vs ExtJS

2014-12-30 Thread Jani Tiainen
On Mon, 29 Dec 2014 06:55:57 -0800 (PST)
Joris Benschop  wrote:

> Hi List,
> 
> I;m a data maangement specialist in a rather large multinational. I'm 
> trying to push Django as a fast development framework for front-end 
> applications of our databases. Currently the company is focusing on
> Sencha ExtJS and java solutions. Can you help me with pointers why
> Django is better? The free-as-in-beer argument is not very convincing
> by itself. 
> 

I'll give my late insight here. We're having rather large SPA's built
on top of ExtJS + Django and REST rather successfully.

Of course ExtJS and REST is really a joke - there is nothing that
really proper rest support in ExtJS, (no HATEOAS at all)

For a Django side REST tool we've been using DRF
(Django-Rest-Framework) which big gun for REST api.

Now why we picked Django over several others - We tried PHP, we
used Java for few web apps (and it's still in use). First reason was
the speed. We could implement features much faster with Python and
Django than we ever could do with Java (we did similiar apps with Java
as well but pace was definitely slower). Specially getting things
done within a reasonable time. Also lot of boilerplate code was
unnecessary. In Java we had really carefully plan every attribute and
getters and setters. Python makes lot of shortcuts there and it's much
more easier to do "magic". Though there lies a danger - you can write
Python code as Java (or even like C code) and that is not pretty
sight...

Another reason was level of complexity - even simplest Java app
(deployed on Tomcat) takes lot of efforts and "special" knowledge, not
to mention that you have to match versions you build with java versions
and complex configuration. Python is much more forgiving in those parts.

Of course we've ran a few issues on the road, like composite keys and
some "oo" features of Django ORM that were possible with Hibernate.

So current main setup in our development stack is Python (2.7), Django
(1.5), Oracle (10g and 11g), ExtJS (4.3), Dojotoolkit (1.6), OpenLayers
(2.x) and mapserver (6.x)

-- 

Jani Tiainen

-- 

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/20141230154442.0c03e788%40jns42-l.w2k.keypro.fi.
For more options, visit https://groups.google.com/d/optout.


delete OnetoOneField link

2014-12-30 Thread madjardi
class Cashbox(models.Model):
cashier = models.OneToOneField('User', null=True, blank=True, 
related_name='cashbox', on_delete=models.SET_NULL)

in other code:
User.object.get(pk=1)
user.cashbox = None

AttributeError: 'NoneType' object has no attribute 'cashier_id'

one version solving is:
c1 = Cashbox.objects.get(pk=user.cashbox.id)
c1.cashier = None
c1.save()


c2 = Cashbox.object.get(pk=10)
c2.cashier = user
c2.save()


i need get other Cashbox to set link None. Why i need do so. is there a 
better solution.

-- 
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/9bac63fa-64e3-4353-82ae-6b31fa8f281f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


django + OAuth2: Sessions

2014-12-30 Thread Anastasios Bakogiannis
Hi everyone,

I am using python-social-auth to implement login via Google, Github, ...
The problem I am having is that after the user is redirected to Google or
Github the sessionid is reset. I want to preserve the sessionid in order to
associate it later with the username.

I did some research but cannot find something online. The only thing I
found was that the sessionid might be reset in the case of changing from
http to https which is not the case since my website uses https.

Any help would be very appreciated.

Thanks a lot guys,
T.

-- 
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/CAJTC%2BnZ1-UOg0AtNbQ5mdqsJz7TkBp2fNTrt%3DAkzDDwnAo1fXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Django vs ExtJS

2014-12-30 Thread Guilherme Leal
I can say that, if you build your env like i tould you to, you would need
only one senior dev, and only for critical cases (whole env crashed, or
major new implementations). The other devs, can be junior devs, hired with
the intent to be formed inside the company.

Em Tue Dec 30 2014 at 08:44:08, Joris Benschop 
escreveu:

> Thank you both for these answers. Personally Im already convinced of
> Django, but the trick is to convince others. The strong benefit of java is
> that it is really easy to hire senior java developers on a consultancy
> basis. For django it is not so simple, especially when the requirement is
> to have these devs on-site (.nl / .be area).
>
>
>
> Op 30 dec. 2014 om 11:36 heeft Ariel Calzada 
> het volgende geschreven:
>
> DJANGO + Tastypie is your TEAM for REST Services, forget Java :)
>
> 2014-12-30 5:34 GMT-05:00 Guilherme Leal :
>
>> Given your scenario, we can say that with django, you wouldn't have to
>> worry about creating REST services. You would create only one service, and
>> let django manage the backend switch (with db routers). If you build your
>> service well, you would have an abstract REST view/url generator (tastypie
>> for instance), and with a little bit of effort (REALLY little), you could
>> serialize the resource structure (metadata) on the request, and let ExtJS
>> read that structure to build your frontend. Of course, this aproach
>> requires a little bit of cache (to save some time on the read
>> structure/build html for ExtJS). With that, you would have to write
>> basically only the models (and of course, any exceptional case that might
>> occur). And if you use django 1.7+, you can LITTERALLY forget about db
>> admin, since django handles the migrations as well.
>>
>> I've done basically the same thing with Django REST Framework and
>> AngularJS for the frontend. Works like a charm, and with the business logic
>> on the signals, reduces the dev time by 90%. And worls like a charm.
>>
>> Em Tue Dec 30 2014 at 06:47:19, Joris Benschop 
>> escreveu:
>>
>>  Thank you, this is already very helpful.
>>> Currently company policy is to create REST services in java for each
>>> backend and use ExtJS to query and visualize the results. With DJango I'm
>>> trying to combine these into one, whilst staying compatible by using
>>> tastypie as a REST service (so ExtJS can connect to that).
>>>
>>> joris
>>>
>>>
>>>
>>> On 29-12-14 16:51, Guilherme Leal wrote:
>>>
>>> Sincerely, I can't see the ExtJS's Models as true models on an MVC (or
>>> MVT for instance) context, since the only real uses I've seen of them is to
>>> bind form controls to any "model like" (basically anything) structure.
>>> Therefore, the best comparsion for the ExtJS would be AngularJS (this is my
>>> point of view, I might be wrong on this one).
>>>
>>>  But if you REALLY want to compare them, I would say that the biggest
>>> point that django excels ExtJS, is that ExtJS doesn't have any meaningfull
>>> way to introspect your DB to build the models dynamically, and with django
>>> you can. As an exemple, with django, you can build an app that read your DB
>>> metadata and build everithing from there (basicaly models; the views and
>>> templates you can build in a way that they can read everything on a given
>>> standard).
>>>
>>>  If you provide more specific info about the project, maybe we can come
>>> with some more concrete comparsions.
>>>
>>> Em Mon Dec 29 2014 at 12:56:05, Joris Benschop 
>>> escreveu:
>>>
>>>  Hi List,

  I;m a data maangement specialist in a rather large multinational. I'm
 trying to push Django as a fast development framework for front-end
 applications of our databases. Currently the company is focusing on Sencha
 ExtJS and java solutions. Can you help me with pointers why Django is
 better? The free-as-in-beer argument is not very convincing by itself.

  Thanks
 Joris
  --
 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/53e17853-9922-4f77-bf9a-4cea7d35ade3%
 40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>  --
>>>
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Django users" group.
>>> To unsubscribe from this topic, visit 

Re: Django vs ExtJS

2014-12-30 Thread Joris Benschop
Thank you both for these answers. Personally Im already convinced of Django, 
but the trick is to convince others. The strong benefit of java is that it is 
really easy to hire senior java developers on a consultancy basis. For django 
it is not so simple, especially when the requirement is to have these devs 
on-site (.nl / .be area).



> Op 30 dec. 2014 om 11:36 heeft Ariel Calzada  het 
> volgende geschreven:
> 
> DJANGO + Tastypie is your TEAM for REST Services, forget Java :)
> 
> 2014-12-30 5:34 GMT-05:00 Guilherme Leal :
>> Given your scenario, we can say that with django, you wouldn't have to worry 
>> about creating REST services. You would create only one service, and let 
>> django manage the backend switch (with db routers). If you build your 
>> service well, you would have an abstract REST view/url generator (tastypie 
>> for instance), and with a little bit of effort (REALLY little), you could 
>> serialize the resource structure (metadata) on the request, and let ExtJS 
>> read that structure to build your frontend. Of course, this aproach requires 
>> a little bit of cache (to save some time on the read structure/build html 
>> for ExtJS). With that, you would have to write basically only the models 
>> (and of course, any exceptional case that might occur). And if you use 
>> django 1.7+, you can LITTERALLY forget about db admin, since django handles 
>> the migrations as well.
>> 
>> I've done basically the same thing with Django REST Framework and AngularJS 
>> for the frontend. Works like a charm, and with the business logic on the 
>> signals, reduces the dev time by 90%. And worls like a charm.
>> 
>> Em Tue Dec 30 2014 at 06:47:19, Joris Benschop  
>> escreveu:
>> 
>>> Thank you, this is already very helpful.
>>> Currently company policy is to create REST services in java for each 
>>> backend and use ExtJS to query and visualize the results. With DJango I'm 
>>> trying to combine these into one, whilst staying compatible by using 
>>> tastypie as a REST service (so ExtJS can connect to that).
>>> 
>>> joris
>>> 
>>> 
>>> 
 On 29-12-14 16:51, Guilherme Leal wrote:
>>> 
 Sincerely, I can't see the ExtJS's Models as true models on an MVC (or MVT 
 for instance) context, since the only real uses I've seen of them is to 
 bind form controls to any "model like" (basically anything) structure. 
 Therefore, the best comparsion for the ExtJS would be AngularJS (this is 
 my point of view, I might be wrong on this one).
 
 But if you REALLY want to compare them, I would say that the biggest point 
 that django excels ExtJS, is that ExtJS doesn't have any meaningfull way 
 to introspect your DB to build the models dynamically, and with django you 
 can. As an exemple, with django, you can build an app that read your DB 
 metadata and build everithing from there (basicaly models; the views and 
 templates you can build in a way that they can read everything on a given 
 standard).
 
 If you provide more specific info about the project, maybe we can come 
 with some more concrete comparsions.
 
 Em Mon Dec 29 2014 at 12:56:05, Joris Benschop  
 escreveu:
 
> Hi List,
> 
> I;m a data maangement specialist in a rather large multinational. I'm 
> trying to push Django as a fast development framework for front-end 
> applications of our databases. Currently the company is focusing on 
> Sencha ExtJS and java solutions. Can you help me with pointers why Django 
> is better? The free-as-in-beer argument is not very convincing by itself. 
> 
> Thanks
> Joris
> -- 
> 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/53e17853-9922-4f77-bf9a-4cea7d35ade3%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
 -- 
>>> 
 You received this message because you are subscribed to a topic in the 
 Google Groups "Django users" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/django-users/gbI1X93KjQg/unsubscribe.
 To unsubscribe from this group and all its topics, 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 
 

Re: Django vs ExtJS

2014-12-30 Thread Ariel Calzada
DJANGO + Tastypie is your TEAM for REST Services, forget Java :)

2014-12-30 5:34 GMT-05:00 Guilherme Leal :

> Given your scenario, we can say that with django, you wouldn't have to
> worry about creating REST services. You would create only one service, and
> let django manage the backend switch (with db routers). If you build your
> service well, you would have an abstract REST view/url generator (tastypie
> for instance), and with a little bit of effort (REALLY little), you could
> serialize the resource structure (metadata) on the request, and let ExtJS
> read that structure to build your frontend. Of course, this aproach
> requires a little bit of cache (to save some time on the read
> structure/build html for ExtJS). With that, you would have to write
> basically only the models (and of course, any exceptional case that might
> occur). And if you use django 1.7+, you can LITTERALLY forget about db
> admin, since django handles the migrations as well.
>
> I've done basically the same thing with Django REST Framework and
> AngularJS for the frontend. Works like a charm, and with the business logic
> on the signals, reduces the dev time by 90%. And worls like a charm.
>
> Em Tue Dec 30 2014 at 06:47:19, Joris Benschop 
> escreveu:
>
>  Thank you, this is already very helpful.
>> Currently company policy is to create REST services in java for each
>> backend and use ExtJS to query and visualize the results. With DJango I'm
>> trying to combine these into one, whilst staying compatible by using
>> tastypie as a REST service (so ExtJS can connect to that).
>>
>> joris
>>
>>
>>
>> On 29-12-14 16:51, Guilherme Leal wrote:
>>
>> Sincerely, I can't see the ExtJS's Models as true models on an MVC (or
>> MVT for instance) context, since the only real uses I've seen of them is to
>> bind form controls to any "model like" (basically anything) structure.
>> Therefore, the best comparsion for the ExtJS would be AngularJS (this is my
>> point of view, I might be wrong on this one).
>>
>>  But if you REALLY want to compare them, I would say that the biggest
>> point that django excels ExtJS, is that ExtJS doesn't have any meaningfull
>> way to introspect your DB to build the models dynamically, and with django
>> you can. As an exemple, with django, you can build an app that read your DB
>> metadata and build everithing from there (basicaly models; the views and
>> templates you can build in a way that they can read everything on a given
>> standard).
>>
>>  If you provide more specific info about the project, maybe we can come
>> with some more concrete comparsions.
>>
>> Em Mon Dec 29 2014 at 12:56:05, Joris Benschop 
>> escreveu:
>>
>>  Hi List,
>>>
>>>  I;m a data maangement specialist in a rather large multinational. I'm
>>> trying to push Django as a fast development framework for front-end
>>> applications of our databases. Currently the company is focusing on Sencha
>>> ExtJS and java solutions. Can you help me with pointers why Django is
>>> better? The free-as-in-beer argument is not very convincing by itself.
>>>
>>>  Thanks
>>> Joris
>>>  --
>>> 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/53e17853-9922-4f77-bf9a-4cea7d35ade3%
>>> 40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>  --
>>
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Django users" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/
>> topic/django-users/gbI1X93KjQg/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAOs3Lp6byk7q5KDTTRPEOLUGDGxXQ
>> HpvqoKMQYY4XCVU09DHfQ%40mail.gmail.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 

Re: Django vs ExtJS

2014-12-30 Thread Guilherme Leal
Given your scenario, we can say that with django, you wouldn't have to
worry about creating REST services. You would create only one service, and
let django manage the backend switch (with db routers). If you build your
service well, you would have an abstract REST view/url generator (tastypie
for instance), and with a little bit of effort (REALLY little), you could
serialize the resource structure (metadata) on the request, and let ExtJS
read that structure to build your frontend. Of course, this aproach
requires a little bit of cache (to save some time on the read
structure/build html for ExtJS). With that, you would have to write
basically only the models (and of course, any exceptional case that might
occur). And if you use django 1.7+, you can LITTERALLY forget about db
admin, since django handles the migrations as well.

I've done basically the same thing with Django REST Framework and AngularJS
for the frontend. Works like a charm, and with the business logic on the
signals, reduces the dev time by 90%. And worls like a charm.

Em Tue Dec 30 2014 at 06:47:19, Joris Benschop 
escreveu:

 Thank you, this is already very helpful.
> Currently company policy is to create REST services in java for each
> backend and use ExtJS to query and visualize the results. With DJango I'm
> trying to combine these into one, whilst staying compatible by using
> tastypie as a REST service (so ExtJS can connect to that).
>
> joris
>
>
>
> On 29-12-14 16:51, Guilherme Leal wrote:
>
> Sincerely, I can't see the ExtJS's Models as true models on an MVC (or
> MVT for instance) context, since the only real uses I've seen of them is to
> bind form controls to any "model like" (basically anything) structure.
> Therefore, the best comparsion for the ExtJS would be AngularJS (this is my
> point of view, I might be wrong on this one).
>
>  But if you REALLY want to compare them, I would say that the biggest
> point that django excels ExtJS, is that ExtJS doesn't have any meaningfull
> way to introspect your DB to build the models dynamically, and with django
> you can. As an exemple, with django, you can build an app that read your DB
> metadata and build everithing from there (basicaly models; the views and
> templates you can build in a way that they can read everything on a given
> standard).
>
>  If you provide more specific info about the project, maybe we can come
> with some more concrete comparsions.
>
> Em Mon Dec 29 2014 at 12:56:05, Joris Benschop 
> escreveu:
>
>  Hi List,
>>
>>  I;m a data maangement specialist in a rather large multinational. I'm
>> trying to push Django as a fast development framework for front-end
>> applications of our databases. Currently the company is focusing on Sencha
>> ExtJS and java solutions. Can you help me with pointers why Django is
>> better? The free-as-in-beer argument is not very convincing by itself.
>>
>>  Thanks
>> Joris
>>  --
>> 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/53e17853-9922-4f77-bf9a-4cea7d35ade3%
>> 40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>  --
>
> You received this message because you are subscribed to a topic in the
> Google Groups "Django users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/django-users/gbI1X93KjQg/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAOs3Lp6byk7q5KDTTRPEOLUGDGxXQ
> HpvqoKMQYY4XCVU09DHfQ%40mail.gmail.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 

Re: Django vs ExtJS

2014-12-30 Thread Joris Benschop

Thank you, this is already very helpful.
Currently company policy is to create REST services in java for each 
backend and use ExtJS to query and visualize the results. With DJango 
I'm trying to combine these into one, whilst staying compatible by using 
tastypie as a REST service (so ExtJS can connect to that).


joris


On 29-12-14 16:51, Guilherme Leal wrote:
Sincerely, I can't see the ExtJS's Models as true models on an MVC (or 
MVT for instance) context, since the only real uses I've seen of them 
is to bind form controls to any "model like" (basically anything) 
structure. Therefore, the best comparsion for the ExtJS would be 
AngularJS (this is my point of view, I might be wrong on this one).


But if you REALLY want to compare them, I would say that the biggest 
point that django excels ExtJS, is that ExtJS doesn't have any 
meaningfull way to introspect your DB to build the models dynamically, 
and with django you can. As an exemple, with django, you can build an 
app that read your DB metadata and build everithing from there 
(basicaly models; the views and templates you can build in a way that 
they can read everything on a given standard).


If you provide more specific info about the project, maybe we can come 
with some more concrete comparsions.


Em Mon Dec 29 2014 at 12:56:05, Joris Benschop 
> escreveu:


Hi List,

I;m a data maangement specialist in a rather large multinational.
I'm trying to push Django as a fast development framework for
front-end applications of our databases. Currently the company is
focusing on Sencha ExtJS and java solutions. Can you help me with
pointers why Django is better? The free-as-in-beer argument is not
very convincing by itself.

Thanks
Joris
-- 
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/53e17853-9922-4f77-bf9a-4cea7d35ade3%40googlegroups.com

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

--
You received this message because you are subscribed to a topic in the 
Google Groups "Django users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/django-users/gbI1X93KjQg/unsubscribe.
To unsubscribe from this group and all its topics, 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/CAOs3Lp6byk7q5KDTTRPEOLUGDGxXQHpvqoKMQYY4XCVU09DHfQ%40mail.gmail.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/54A2667B.9030105%40gmail.com.
For more options, visit https://groups.google.com/d/optout.