how to copy data per user

[Jun Tanaka]

Hello all!

I use Django 1.6
I would like to copy data from one user to another. Say user 1 has 
data_set_A in database and I would like to copy data_set_A to user 2, 
user3, user4. 
If you could tell me any simple way to do so, I would appreciate it.

Thank you,
 
Jun

-- 
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/3c8bc377-0a6b-4c00-a1ae-5d917f3d24e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

getting started with django

[Anagha R]

How to get stated with django?How can we contribute to 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/01860db5-b03e-4656-9b9d-b629dfb94004%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: getting started with django

[Tim Graham]

Getting Started with Django:
https://docs.djangoproject.com/en/stable/intro/

Contributing:
https://docs.djangoproject.com/en/dev/intro/contributing/
https://docs.djangoproject.com/en/dev/internals/contributing/

On Wednesday, October 7, 2015 at 8:12:11 AM UTC-4, Anagha R wrote:
>
> How to get stated with django?How can we contribute to 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/497f8999-c8e6-428e-b1e6-bf12ce50025d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to copy data per user

[Tim Graham]

I don't think you've provided enough details about your models for anyone 
to provide an answer.

p.s. Django 1.6 is unsupported and has unfixed security vulnerabilities so 
you should try to upgrade to a supported version.
https://www.djangoproject.com/download/#supported-versions

On Wednesday, October 7, 2015 at 5:00:56 AM UTC-4, Jun Tanaka wrote:
>
> Hello all!
>
> I use Django 1.6
> I would like to copy data from one user to another. Say user 1 has 
> data_set_A in database and I would like to copy data_set_A to user 2, 
> user3, user4. 
> If you could tell me any simple way to do so, I would appreciate it.
>
> Thank you,
>  
> Jun
>

-- 
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/ccf1124b-d159-467c-8354-b81a92dcb305%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run all tests in INSTALLED_APPS with the new test runner 1.6?

[Tim Graham]

Copying the old test runner from an old version of Django seems like a fine 
solution. I thought someone might have published it on PyPI, but I couldn't 
find it if so.

On Wednesday, October 7, 2015 at 2:06:08 AM UTC-4, Gergely Polonkai wrote:
>
> I'm not sure I understand what you want to achieve. I use 1.8 and it runs 
> all tests for all apps without backporting anything.
> On 6 Oct 2015 22:39, > wrote:
>
>> I want the old behaviour of running all tests in INSTALLED_APPS by default 
>> Actually, 
>> I don't care too much if this is accomplished by grabbing the old 
>> django.test.simple.DjangoTestSuiteRunner from git history or by any other 
>> means.
>>
>> On Tuesday, October 6, 2015 at 4:24:00 PM UTC-4, Gergely Polonkai wrote:
>>>
>>> Hello,
>>>
>>> do you mean the integrated unittest module, or the Django test runners?
>>>
>>> However, both needs to be fetched from old history, and I daresay it 
>>> won't be an easy fetch. 1.6 code will more than likely be incompatible with 
>>> 1.8, so even if you backmerge it, you will have to do a lot of patching.
>>>
>>> Best,
>>> Gergely
>>> On 6 Oct 2015 21:02,  wrote:
>>>
 Hey, sorry to respond to such an old thread, but now that 1.8 
 completely removed the old test runner, I am wondering if there's any way 
 to get it back.

 I don't want to explain why I want it back. Please don't tell me I 
 don't want it.

 So, starting from the axiom that I want it back, how should I do it? 
 Grab it from git history?

 On Tuesday, November 12, 2013 at 8:29:14 PM UTC-5, Russell Keith-Magee 
 wrote:
>
>
> On Sun, Nov 10, 2013 at 3:36 PM, Kyle MacFarlane  > wrote:
>
>> With the new test runner in 1.6 it only seems to be running tests 
>> under my project and ignoring all tests in dependent apps listed in 
>> INSTALLED_APPS.
>>
>> If I try to specify another app to test by doing something like 
>> "django test a_dependency" I get an exception from Python's unittest 
>> saying 
>> "Path must be within the project" (all my dependencies are installed 
>> system 
>> wide or in a shared buildout folder in my user dir).
>>
>> The only tests outside of my project I seem to be able to run are 
>> Django's itself via "django test django".
>>
>> How can I get the new test runner to discover and run all tests in 
>> INSTALLED_APPS? As far as I can tell the new test runner only supports 
>> tests located under the cwd which is not very useful for me since my 
>> projects tend to just amalgamate smaller apps located elsewhere.
>>
>
> Hi Kyle,
>
> The short answer is no, you can't. However, there's method in this 
> madness.
>
> Essentially *all* Django projects are amalgams of smaller apps from 
> elsewhere, so you're not alone in this. However, it doesn't follow that 
> you 
> need to run the tests for those apps. Consider the tests for one of the 
> many apps in your project. This app is either:
>
> 1) A standalone, third party app, provided by another developer. This 
> developer has presumably written and run the test suite for that app, 
> validated that they pass, and packaged the app as version X. You pin 
> version X in your requirements file. At this point, there's no value in 
> you 
> running these tests as part of your own project -- these tests aren't 
> going 
> to start spontaneously failing just because they're in your project.
>
> 2) A standalone app that you're maintaining in house. Although you're 
> maintaining this in house, it's really no different to case 1. Good 
> discipline means writing code, running tests, and validating a release 
> (either as a tagged version, or just a VCS hash/revision) and pinning at 
> that release. Again, the testing of the app is (or should be) independent 
> of the testing of your project.
>
> 3) An app that is strongly tied to this particular project. In which 
> case, it should be part of the project directory, and will be picked up 
> using Django's test suite. If you want to put your project directory 
> somewhere other than the default, you can use the -t option to 
> ./manage.py 
> test to point at your top level project directory. This doesn't change 
> the 
> discovery strategy; it just alters the place that Django looks.
>
> So - you shouldn't have any need to run *all* the tests in 
> INSTALLED_APPS -- just the apps that are actually part of your project, 
> and 
> won't be independently tested. If the app is independently maintained, 
> but 
> not independently tested, you've got much bigger problems :-)
>
> 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 rece

Re: are parameters compulsary in an url pattern?

[Tim Graham]

If you can accomplish what you need without passing parameters, there is 
certainly no requirement to do so.

Have you read: https://docs.djangoproject.com/en/stable/topics/http/urls/ ?

On Wednesday, October 7, 2015 at 12:10:54 AM UTC-4, krmane wrote:
>
> Dear all, 
> I just wish to know if I must have all the parameters from my form as a 
> part of the url pattern? 
> I need to use only the request so was wondering if that is the case? 
> I have seen tutorials and all of them come with url parameters 
> I don't need a url like /articles/2013/03 etc. 
> I am writing a accounting/ inventory system and don't need a blogging 
> kind of application or a news room kind of stuff which Django is mostly 
> known for. 
> My forms will contain all the data and I can access all that in a view 
> through the request object I guess? 
> so a pattern like r(^setaccount'), views/account/setaccount must work. 
> is this correct or do I always need to pass parameters? 
> Which is the best time to use parameters apart from the request object? 
> Happy hacking. 
> Krishnakant. 
>

-- 
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/db5d6795-bcbf-4f9e-97c2-b49a3efe2952%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run all tests in INSTALLED_APPS with the new test runner 1.6?

[jordi . gutierrez . hermoso]

No, the new test runner does not run any 3rd party apps not in my project, 
and it does not run django.contrib either.

On Wednesday, October 7, 2015 at 2:06:08 AM UTC-4, Gergely Polonkai wrote:
>
> I'm not sure I understand what you want to achieve. I use 1.8 and it runs 
> all tests for all apps without backporting anything.
> On 6 Oct 2015 22:39, > wrote:
>
>> I want the old behaviour of running all tests in INSTALLED_APPS by default 
>> Actually, 
>> I don't care too much if this is accomplished by grabbing the old 
>> django.test.simple.DjangoTestSuiteRunner from git history or by any other 
>> means.
>>
>> On Tuesday, October 6, 2015 at 4:24:00 PM UTC-4, Gergely Polonkai wrote:
>>>
>>> Hello,
>>>
>>> do you mean the integrated unittest module, or the Django test runners?
>>>
>>> However, both needs to be fetched from old history, and I daresay it 
>>> won't be an easy fetch. 1.6 code will more than likely be incompatible with 
>>> 1.8, so even if you backmerge it, you will have to do a lot of patching.
>>>
>>> Best,
>>> Gergely
>>> On 6 Oct 2015 21:02,  wrote:
>>>
 Hey, sorry to respond to such an old thread, but now that 1.8 
 completely removed the old test runner, I am wondering if there's any way 
 to get it back.

 I don't want to explain why I want it back. Please don't tell me I 
 don't want it.

 So, starting from the axiom that I want it back, how should I do it? 
 Grab it from git history?

 On Tuesday, November 12, 2013 at 8:29:14 PM UTC-5, Russell Keith-Magee 
 wrote:
>
>
> On Sun, Nov 10, 2013 at 3:36 PM, Kyle MacFarlane  > wrote:
>
>> With the new test runner in 1.6 it only seems to be running tests 
>> under my project and ignoring all tests in dependent apps listed in 
>> INSTALLED_APPS.
>>
>> If I try to specify another app to test by doing something like 
>> "django test a_dependency" I get an exception from Python's unittest 
>> saying 
>> "Path must be within the project" (all my dependencies are installed 
>> system 
>> wide or in a shared buildout folder in my user dir).
>>
>> The only tests outside of my project I seem to be able to run are 
>> Django's itself via "django test django".
>>
>> How can I get the new test runner to discover and run all tests in 
>> INSTALLED_APPS? As far as I can tell the new test runner only supports 
>> tests located under the cwd which is not very useful for me since my 
>> projects tend to just amalgamate smaller apps located elsewhere.
>>
>
> Hi Kyle,
>
> The short answer is no, you can't. However, there's method in this 
> madness.
>
> Essentially *all* Django projects are amalgams of smaller apps from 
> elsewhere, so you're not alone in this. However, it doesn't follow that 
> you 
> need to run the tests for those apps. Consider the tests for one of the 
> many apps in your project. This app is either:
>
> 1) A standalone, third party app, provided by another developer. This 
> developer has presumably written and run the test suite for that app, 
> validated that they pass, and packaged the app as version X. You pin 
> version X in your requirements file. At this point, there's no value in 
> you 
> running these tests as part of your own project -- these tests aren't 
> going 
> to start spontaneously failing just because they're in your project.
>
> 2) A standalone app that you're maintaining in house. Although you're 
> maintaining this in house, it's really no different to case 1. Good 
> discipline means writing code, running tests, and validating a release 
> (either as a tagged version, or just a VCS hash/revision) and pinning at 
> that release. Again, the testing of the app is (or should be) independent 
> of the testing of your project.
>
> 3) An app that is strongly tied to this particular project. In which 
> case, it should be part of the project directory, and will be picked up 
> using Django's test suite. If you want to put your project directory 
> somewhere other than the default, you can use the -t option to 
> ./manage.py 
> test to point at your top level project directory. This doesn't change 
> the 
> discovery strategy; it just alters the place that Django looks.
>
> So - you shouldn't have any need to run *all* the tests in 
> INSTALLED_APPS -- just the apps that are actually part of your project, 
> and 
> won't be independently tested. If the app is independently maintained, 
> but 
> not independently tested, you've got much bigger problems :-)
>
> 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 djang

Re: How to run all tests in INSTALLED_APPS with the new test runner 1.6?

[jordi . gutierrez . hermoso]

Okay, I'll try grabbing the old test runner from git, thanks.

On Wednesday, October 7, 2015 at 8:38:40 AM UTC-4, Tim Graham wrote:
>
> Copying the old test runner from an old version of Django seems like a 
> fine solution. I thought someone might have published it on PyPI, but I 
> couldn't find it if so.
>
> On Wednesday, October 7, 2015 at 2:06:08 AM UTC-4, Gergely Polonkai wrote:
>>
>> I'm not sure I understand what you want to achieve. I use 1.8 and it runs 
>> all tests for all apps without backporting anything.
>> On 6 Oct 2015 22:39,  wrote:
>>
>>> I want the old behaviour of running all tests in INSTALLED_APPS by 
>>> default Actually, I don't care too much if this is accomplished by 
>>> grabbing the old django.test.simple.DjangoTestSuiteRunner from git history 
>>> or by any other means.
>>>
>>> On Tuesday, October 6, 2015 at 4:24:00 PM UTC-4, Gergely Polonkai wrote:

 Hello,

 do you mean the integrated unittest module, or the Django test runners?

 However, both needs to be fetched from old history, and I daresay it 
 won't be an easy fetch. 1.6 code will more than likely be incompatible 
 with 
 1.8, so even if you backmerge it, you will have to do a lot of patching.

 Best,
 Gergely
 On 6 Oct 2015 21:02,  wrote:

> Hey, sorry to respond to such an old thread, but now that 1.8 
> completely removed the old test runner, I am wondering if there's any way 
> to get it back.
>
> I don't want to explain why I want it back. Please don't tell me I 
> don't want it.
>
> So, starting from the axiom that I want it back, how should I do it? 
> Grab it from git history?
>
> On Tuesday, November 12, 2013 at 8:29:14 PM UTC-5, Russell Keith-Magee 
> wrote:
>>
>>
>> On Sun, Nov 10, 2013 at 3:36 PM, Kyle MacFarlane <
>> kylemac...@gmail.com> wrote:
>>
>>> With the new test runner in 1.6 it only seems to be running tests 
>>> under my project and ignoring all tests in dependent apps listed in 
>>> INSTALLED_APPS.
>>>
>>> If I try to specify another app to test by doing something like 
>>> "django test a_dependency" I get an exception from Python's unittest 
>>> saying 
>>> "Path must be within the project" (all my dependencies are installed 
>>> system 
>>> wide or in a shared buildout folder in my user dir).
>>>
>>> The only tests outside of my project I seem to be able to run are 
>>> Django's itself via "django test django".
>>>
>>> How can I get the new test runner to discover and run all tests in 
>>> INSTALLED_APPS? As far as I can tell the new test runner only supports 
>>> tests located under the cwd which is not very useful for me since my 
>>> projects tend to just amalgamate smaller apps located elsewhere.
>>>
>>
>> Hi Kyle,
>>
>> The short answer is no, you can't. However, there's method in this 
>> madness.
>>
>> Essentially *all* Django projects are amalgams of smaller apps from 
>> elsewhere, so you're not alone in this. However, it doesn't follow that 
>> you 
>> need to run the tests for those apps. Consider the tests for one of the 
>> many apps in your project. This app is either:
>>
>> 1) A standalone, third party app, provided by another developer. This 
>> developer has presumably written and run the test suite for that app, 
>> validated that they pass, and packaged the app as version X. You pin 
>> version X in your requirements file. At this point, there's no value in 
>> you 
>> running these tests as part of your own project -- these tests aren't 
>> going 
>> to start spontaneously failing just because they're in your project.
>>
>> 2) A standalone app that you're maintaining in house. Although you're 
>> maintaining this in house, it's really no different to case 1. Good 
>> discipline means writing code, running tests, and validating a release 
>> (either as a tagged version, or just a VCS hash/revision) and pinning at 
>> that release. Again, the testing of the app is (or should be) 
>> independent 
>> of the testing of your project.
>>
>> 3) An app that is strongly tied to this particular project. In which 
>> case, it should be part of the project directory, and will be picked up 
>> using Django's test suite. If you want to put your project directory 
>> somewhere other than the default, you can use the -t option to 
>> ./manage.py 
>> test to point at your top level project directory. This doesn't change 
>> the 
>> discovery strategy; it just alters the place that Django looks.
>>
>> So - you shouldn't have any need to run *all* the tests in 
>> INSTALLED_APPS -- just the apps that are actually part of your project, 
>> and 
>> won't be independently tested. If the app is independently maintained, 
>> but 
>>

Re: Formset questions: data vs. initial values

[Shawn Milochik]

You *can* use ModelForms for this. You don't need an active instance.

Iterate over the days in the month, and if you have an instance in your
database you instantiate a ModelForm where "instance=thing." If not, you
instantiate a ModelForm that has no instance, and you send as data ""
(empty string) for the entry and the proper date for the ref_date. You can
use the data kwarg when creating the ModelForm -- just as you'd send
"request.POST" into it.

When you receive the forms back in POST, you validate and save the forms.
Override the save() method of your ModelForm so that, if "entry" is blank
you don't save it. Incidentally, you should also check if it already exists
for that date and delete it in that case.

You can have multiple forms using "prefix," which could just be the date as
a string.

-- 
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/CAOzwKwFmrjn-i9WjEbxKhr6x7iLQuD0tXeBeYa_mcJs3ffpnpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Are jobs postings allowed on this forum?

[John Shields]

Thanks Russell!

On Tuesday, October 6, 2015 at 8:42:08 PM UTC-4, Russell Keith-Magee wrote:
>
> Hi John, 
>
> As long as they're on topic (i.e, for Django jobs), you're clear about 
> the geographical constraints on the job (e.g., only looking for people 
> in city X, relocation budget available; telecommuting welcome; US 
> citizen required), the job advertisement doesn't trigger any Community 
> Code of Conduct issues, and you don't start spamming the list as a 
> recruiter, you're free to post job advertisements. 
>
> Yours, 
> Russ Magee %-) 
>
> On Wed, Oct 7, 2015 at 3:23 AM, John Shields  > wrote: 
> > Hi, does this forum allow job postings? 
> > 
> > -- 
> > 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/30de2b49-9868-4030-b52b-c6b767056559%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/1458c655-f851-42f4-84ba-1ef2e6923435%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Load a static file with a variable name

[I . Dié]

Thank you very much monsieur François 

Le mardi 6 octobre 2015 20:40:01 UTC+2, François Schiettecatte a écrit :
>
> The '+' is an error, the line look more like this:
>
>  />
>
> On Tue, Oct 6, 2015 at 2:33 PM, I. Dié > 
> wrote:
>
>> I tried in your way to concatenate, I don't get any exception, but  the 
>> image image does'nt want to display. The plage only throw the "alt" value. 
>> Even for this line of code it's thing.
>>
>>
>> Le mardi 6 octobre 2015 19:51:04 UTC+2, Shawn Milochik a écrit :
>>>
>>> Try this:
>>>
>>> >> pet.name }} />
>>>
>>> You're embedding {{pet_name}} in a string. If this was a regular Python 
>>> statement, it would be like writing "Hello, {0}" and not having a format() 
>>> at the end.
>>>
>> -- 
>> 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/f29da80b-ffe4-421c-9aba-8ad76b87a484%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/ca812bda-3eff-49fa-b4ab-db10b9d1101b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Need For Mid Level Full Stack Developer (Python / Django) at BITS

[John Shields]

Hi Folks, there is a contract opportunity at a US Federal Agency in 
Bethesda, MD.   Due to Federal Agency constraints the position is onsite 
only, background check and fingerprinting is required.  The length is 8 
months but could extend depending on the developers deliverables.   Relo 
package is available.  US Citizen or H1B accepted.   Hourly rate is 
commensurate on experience and market rates, reply to this post if you need 
a range of the hourly rates.  Thanks and Good Luck!

If you're interested please apply at 
https://www.djangojobs.net/jobs/484/urgent-need-for-mid-level-full-stack-developer-python-django-bits/#sthash.bK6dfmQc.dpuf


*Biswas Information Technology Solutions Inc.*, (BITS) was founded in 
Herndon, Virginia in 2006 with an exclusive focus on end-to-end technology 
solutions for its clients. BITS provides high quality IT solutions using 
state-of-the-art technologies that fulfill the technological needs of its 
clients. Our objective is to provide complete and cost effective solutions 
to our clients and partners to increase their ROI.

Looking for an experienced Full Stack Developer to work on site at Federal 
client's office in Bethesda, MD. Candidate is responsible for providing 
support in developing the site concept, interface design, and architecture 
of the client's web-site, as well as provide support for the implementation 
of interfaces to applications.

Requirements:

   - Minimum of Bachelor's degree in Computer Science, or related field
   - 5+ years experience in web application development
   - Excellent problem-solving, design, development, and debugging skill
   - Experience in *Python, Django or Ruby on Rails, and PHP*
   - PostgreSQL experience preferred

- See more at: 
https://www.djangojobs.net/jobs/484/urgent-need-for-mid-level-full-stack-developer-python-django-bits/#sthash.bK6dfmQc.dpuf

-- 
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/54557715-85e0-48f1-b511-216a4912fee9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run all tests in INSTALLED_APPS with the new test runner 1.6?

[Carl Meyer]

On 10/07/2015 06:57 AM, jordi.gutierrez.herm...@ecometrica.org wrote:
> Okay, I'll try grabbing the old test runner from git, thanks.

That should work fine.

You should be aware, though, that specifically in the case of the
django.contrib app tests, we make no promise that they will pass under
your project's configuration, and pull requests that complexify the
tests solely to make them pass under a wider variety of configurations
will not be accepted. It is our policy that they should pass when run as
part of the Django test suite, but not necessarily in an arbitrary project.

You may find that a similar de facto policy exists for an increasing
number of third-party apps' test suites, too.

Carl

-- 
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/56152907.1040400%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: How to run all tests in INSTALLED_APPS with the new test runner 1.6?

[jordi . gutierrez . hermoso]

On Wednesday, October 7, 2015 at 10:16:30 AM UTC-4, Carl Meyer wrote:
>
> You should be aware, though, that specifically in the case of the 
> django.contrib app tests, we make no promise that they will pass under 
> your project's configuration, 
>

That's fine. I just want to make sure *we *didn't break anything. 

-- 
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/483b06bc-b3ca-41ea-9228-7395bee7db9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using Django and R in a production environment?

[Mike Covington]

Not sure if this approach is useful for you, but the following is how we 
use R and Django together.

We use R to build Shiny apps. These are served on their default port 3838 
(which users never actually go to directly). I've made a Django app to 
manage the Shiny apps and simply place them in an iframe.

Live site: http://symposium.plb.ucdavis.edu/apps/
Django App: https://github.com/mfcovington/djangocms-shiny-app

On Saturday, October 3, 2015 at 8:55:38 AM UTC-7, Chanat Praserthdam wrote:
>
> Hi Derek,
>
> Did you find the solution to your problem?
> I ran to a similar issue.  I am wondering if RServe will work for me.
>
>
> On Tuesday, April 30, 2013 at 12:40:01 PM UTC-7, Derek wrote:
>>
>> Thanks Nick; RStudio looks like a really good tool for development work.
>>
>> The impression I get though, is that the server is designed for allowing 
>> interactive R sessions over the web; whereas for us Django is the primary 
>> requirement and calls to R should happen "behind the scenes".  
>>
>> On Tuesday, 30 April 2013 15:43:01 UTC+2, Nick Santos wrote:
>>>
>>> Is Django a hard and fast requirement? If so, is it just about 
>>> integrating the routines? I think otherwise something like RStudio Server 
>>> would work for you. I've deployed it previously and it was a pretty nice 
>>> setup. It's based on Unix user accounts, so R processes run as if users 
>>> were running them on a desktop, except not. You may be able to share code 
>>> in this environment too, but I haven't played with it a ton.
>>>
>>> http://www.rstudio.com/ide/docs/server/getting_started
>>>
>>> -Nick
>>>
>>> On Tue, Apr 30, 2013 at 12:06 AM, Derek  wrote:
>>>
 " if you write your own R  analysis routines, why have them run in a 
 web system"

 Two issues here:

 1. We are writing R routines for someone else; who needs 'analysis on 
 demand'
 2. A web system means that multiple users in multiple locations can all 
 readily access the same analysis routines (but with different data sets)

 I agree that if you work on a desktop, with no need to access shared 
 data or use the same analysis routines as anyone else, then a web 
 interface 
 makes no sense.

 Basically we are trying to harness two disparate systems; each of which 
 is very powerful in their own sphere, to create an application that is 
 really useful for better and more efficient science.


 On 29 April 2013 16:59, Javier Guerra Giraldez  
 wrote:

> On Mon, Apr 29, 2013 at 2:13 AM, Derek  wrote:
> > hat no one is actually using R in a production environment 
> themselves (which
> > is a little surprising to me).
>
>
> well R itself is widely used in production... but the intersection
> with Django is very small.  (after all, if you write your own R
> analysis routines, why have them run in a web system)
>
> --
> Javier
>

 -- 
 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?hl=en.
 For more options, visit https://groups.google.com/groups/opt_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/24469c91-e641-4361-be6d-9c90fe0f4bf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Possible Bug in password_reset_form

[mwidman]

Thank you. 

I am not sure that solves the problem though (or I just don't understand 
how to do this): If I am calling password_reset directly from my urls, how 
do I pass a requestContext into the "extra_email_context"?  There is no 
request sent to "render_to_string" so the RequestContext would need to be 
created before that point, which either requires subclassing 
PasswordResetForm's save function or somehow getting access to the request 
in urls.py to build a RequestContext. 

Regards,
  Mike


On Monday, October 5, 2015 at 4:11:59 PM UTC-7, Tim Graham wrote:
>
> In Django 1.9, the "extra_email_context" parameter was added to achieve 
> this.
>
>
> https://docs.djangoproject.com/en/1.9/topics/auth/default/#django.contrib.auth.views.password_reset
>
> On Monday, October 5, 2015 at 5:48:57 PM UTC-4, mwidman wrote:
>>
>> Not sure if this intentional or not, but in Django 1.8.4 the 
>> PasswordResetForm's save function only passes a dictionary as the context 
>> to "send_mail()".
>>
>> Because of that, there is now way to add any extra information (i.e. from 
>> a RequestContext). 
>>
>> Can anyone say if this is done for some security reason or if the context 
>> dictionary should be made into a RequestContext via "make_context"?
>>
>

-- 
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/9b471115-cd44-4721-a92d-9f45762df0bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Possible Bug in password_reset_form

[Tim Graham]

You could create a custom view function that wraps password_reset() and 
adds a RequestContext.

On Wednesday, October 7, 2015 at 1:05:12 PM UTC-4, Mike Widman wrote:
>
> Thank you. 
>
> I am not sure that solves the problem though (or I just don't understand 
> how to do this): If I am calling password_reset directly from my urls, how 
> do I pass a requestContext into the "extra_email_context"?  There is no 
> request sent to "render_to_string" so the RequestContext would need to be 
> created before that point, which either requires subclassing 
> PasswordResetForm's save function or somehow getting access to the request 
> in urls.py to build a RequestContext. 
>
> Regards,
>   Mike
>
>
> On Monday, October 5, 2015 at 4:11:59 PM UTC-7, Tim Graham wrote:
>>
>> In Django 1.9, the "extra_email_context" parameter was added to achieve 
>> this.
>>
>>
>> https://docs.djangoproject.com/en/1.9/topics/auth/default/#django.contrib.auth.views.password_reset
>>
>> On Monday, October 5, 2015 at 5:48:57 PM UTC-4, mwidman wrote:
>>>
>>> Not sure if this intentional or not, but in Django 1.8.4 the 
>>> PasswordResetForm's save function only passes a dictionary as the context 
>>> to "send_mail()".
>>>
>>> Because of that, there is now way to add any extra information (i.e. 
>>> from a RequestContext). 
>>>
>>> Can anyone say if this is done for some security reason or if the 
>>> context dictionary should be made into a RequestContext via "make_context"?
>>>
>>

-- 
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/06e26a9c-3fe5-4c54-984f-618ccfc1c658%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fetching data in Django project

[Bhanu Kathuria]

By scrapping I have collected database from other website. How can I show 
it in my Django project.

-- 
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/17e49d1e-fcad-45bb-9bdf-65d4e104b81c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run all tests in INSTALLED_APPS with the new test runner 1.6?

[Tim Graham]

And actually as of Django 1.8, the contrib tests aren't shipped inside each 
application directory, so they won't be discovered even if you switch to 
the old test runner.

On Wednesday, October 7, 2015 at 11:21:54 AM UTC-4, 
jordi.gutie...@ecometrica.org wrote:
>
> On Wednesday, October 7, 2015 at 10:16:30 AM UTC-4, Carl Meyer wrote:
>>
>> You should be aware, though, that specifically in the case of the 
>> django.contrib app tests, we make no promise that they will pass under 
>> your project's configuration, 
>>
>
> That's fine. I just want to make sure *we *didn't break anything. 
>

-- 
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/72f50928-e5f6-4c03-8943-9df4387db5ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

KeyError

[Benjamin Smith]

I am making a user registration form to register new users using the User
model.

This is the forms.py:

class UserForm(forms.ModelForm):
confirm_email = forms.EmailField(label="Confirm email")

def clean(self):
email = self.cleaned_data['email']
confirm_email = self.cleaned_data['confirm_email']
password = self.cleaned_data['password']

if email != confirm_email:
raise ValidationError({'confirm_email': "Both email doesn't
match."})

if len(password) < 8:
raise ValidationError({'password': "Password should be of
minimum 8 characters."})

return super(UserForm, self).clean()

class Meta:
model = User
fields = ['first_name', 'last_name', 'username', 'email',
'confirm_email', 'password']

Template:

{% block content %}
Register

{% csrf_token %}
{{ user_form.as_p }}


{% endblock %}

Views.py:

def register_view(request):
if request.method == "POST":
user_form = UserForm(request.POST)
if user_form.is_valid:
user = user_form.save()
return  HttpResponseRedirect('/account/registered/')
else:
user_form = UserForm()
return render(request, 'register_view.html', {
'user_form': user_form
})

But when registering a user on submitting the form I am getting this error:

*KeyError at /account/register/*

*'confirm_email'*


How can I solve this problem? Your help will be much appreciated.

Thank you.

-- 
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/CAM4YLWLLi%2BfqcvjCebEEDnGjkVdSoETv%3D19Xux1KTOpn%3DXvz1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

KeyError

[Benjamin Smith]

I am making a registration form to register new users using the User model.

This is the forms.py:

class UserForm(forms.ModelForm):
confirm_email = forms.EmailField(label="Confirm email")

def clean(self):
email = self.cleaned_data['email']
confirm_email = self.cleaned_data['confirm_email']
password = self.cleaned_data['password']

if email != confirm_email:
raise ValidationError({'confirm_email': "Both email doesn't 
match."})

if len(password) < 8:
raise ValidationError({'password': "Password should be of 
minimum 8 characters."})

return super(UserForm, self).clean()

class Meta:
model = User
fields = ['first_name', 'last_name', 'username', 'email', 
'confirm_email', 'password']


Template:

 {% block content %}
Register

{% csrf_token %}
{{ user_form.as_p }}


{% endblock %}


 views.py:

def register_view(request):
if request.method == "POST":
user_form = UserForm(request.POST)
if user_form.is_valid:
user = user_form.save()
return  HttpResponseRedirect('/account/registered/')
else:
user_form = UserForm()
return render(request, 'register_view.html', {
'user_form': user_form
})


But I am getting this error while registering a new user when I submit the 
form:

KeyError at /account/register/
'confirm_email'

How can I solve this problem? Your help will be much appreciated.

Thank you. 

-- 
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/ca83b90f-334d-40cf-8561-fc02462ab80f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fetching data in Django project

[Daniel Roseman]

On Wednesday, 7 October 2015 18:19:30 UTC+1, Bhanu Kathuria wrote:
>
> By scrapping I have collected database from other website. How can I show 
> it in my Django project.
>

With a URL, a view, and optionally a template. Just like any other data.
-- 
DR. 

-- 
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/d5f8a9cc-f03a-4207-b1bd-6442b3f1870f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using Django and R in a production environment?

[Andrew Farrell]

One option is to use the conda package manager (you can get that here
) to create an environment with
`conda create --name django+r django=1.8`
activate it with
`source activate django+r`
And then install R packages with something like
`conda install --channel https://conda.anaconda.org/r r-data.table`

You can of also use conda to install pandas and, if you want a bunch of
data science libraries at once, you can download the full Anaconda
 distribution.

On Wed, Oct 7, 2015 at 11:42 AM, Mike Covington 
wrote:

> Not sure if this approach is useful for you, but the following is how we
> use R and Django together.
>
> We use R to build Shiny apps. These are served on their default port 3838
> (which users never actually go to directly). I've made a Django app to
> manage the Shiny apps and simply place them in an iframe.
>
> Live site: http://symposium.plb.ucdavis.edu/apps/
> Django App: https://github.com/mfcovington/djangocms-shiny-app
>
> On Saturday, October 3, 2015 at 8:55:38 AM UTC-7, Chanat Praserthdam wrote:
>>
>> Hi Derek,
>>
>> Did you find the solution to your problem?
>> I ran to a similar issue.  I am wondering if RServe will work for me.
>>
>>
>> On Tuesday, April 30, 2013 at 12:40:01 PM UTC-7, Derek wrote:
>>>
>>> Thanks Nick; RStudio looks like a really good tool for development work.
>>>
>>> The impression I get though, is that the server is designed for allowing
>>> interactive R sessions over the web; whereas for us Django is the primary
>>> requirement and calls to R should happen "behind the scenes".
>>>
>>> On Tuesday, 30 April 2013 15:43:01 UTC+2, Nick Santos wrote:

 Is Django a hard and fast requirement? If so, is it just about
 integrating the routines? I think otherwise something like RStudio Server
 would work for you. I've deployed it previously and it was a pretty nice
 setup. It's based on Unix user accounts, so R processes run as if users
 were running them on a desktop, except not. You may be able to share code
 in this environment too, but I haven't played with it a ton.

 http://www.rstudio.com/ide/docs/server/getting_started

 -Nick

 On Tue, Apr 30, 2013 at 12:06 AM, Derek  wrote:

> " if you write your own R  analysis routines, why have them run in a
> web system"
>
> Two issues here:
>
> 1. We are writing R routines for someone else; who needs 'analysis on
> demand'
> 2. A web system means that multiple users in multiple locations can
> all readily access the same analysis routines (but with different data 
> sets)
>
> I agree that if you work on a desktop, with no need to access shared
> data or use the same analysis routines as anyone else, then a web 
> interface
> makes no sense.
>
> Basically we are trying to harness two disparate systems; each of
> which is very powerful in their own sphere, to create an application that
> is really useful for better and more efficient science.
>
>
> On 29 April 2013 16:59, Javier Guerra Giraldez 
> wrote:
>
>> On Mon, Apr 29, 2013 at 2:13 AM, Derek  wrote:
>> > hat no one is actually using R in a production environment
>> themselves (which
>> > is a little surprising to me).
>>
>>
>> well R itself is widely used in production... but the intersection
>> with Django is very small.  (after all, if you write your own R
>> analysis routines, why have them run in a web system)
>>
>> --
>> Javier
>>
>
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_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/24469c91-e641-4361-be6d-9c90fe0f4bf0%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

Re: KeyError

[Vijay Khemlani]

"is_valid" is a method, you should call

if user_form.is_valid():
...

On Wed, Oct 7, 2015 at 2:14 PM, Benjamin Smith 
wrote:

> I am making a registration form to register new users using the User model.
>
> This is the forms.py:
>
> class UserForm(forms.ModelForm):
> confirm_email = forms.EmailField(label="Confirm email")
>
> def clean(self):
> email = self.cleaned_data['email']
> confirm_email = self.cleaned_data['confirm_email']
> password = self.cleaned_data['password']
>
> if email != confirm_email:
> raise ValidationError({'confirm_email': "Both email doesn't
> match."})
>
> if len(password) < 8:
> raise ValidationError({'password': "Password should be of
> minimum 8 characters."})
>
> return super(UserForm, self).clean()
>
> class Meta:
> model = User
> fields = ['first_name', 'last_name', 'username', 'email',
> 'confirm_email', 'password']
>
>
> Template:
>
>  {% block content %}
> Register
> 
> {% csrf_token %}
> {{ user_form.as_p }}
> 
> 
> {% endblock %}
>
>
>  views.py:
>
> def register_view(request):
> if request.method == "POST":
> user_form = UserForm(request.POST)
> if user_form.is_valid:
> user = user_form.save()
> return  HttpResponseRedirect('/account/registered/')
> else:
> user_form = UserForm()
> return render(request, 'register_view.html', {
> 'user_form': user_form
> })
>
>
> But I am getting this error while registering a new user when I submit the
> form:
>
> KeyError at /account/register/
> 'confirm_email'
>
> How can I solve this problem? Your help will be much appreciated.
>
> Thank you.
>
> --
> 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/ca83b90f-334d-40cf-8561-fc02462ab80f%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/CALn3ei3RG%2BLB4qsD%2BEmFO7Os-J-Q_VPvab3J9XapF%2BNcDi9aLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Load a static file with a variable name

[Simon Charette]

You'll want to use 



Because François' suggestion will break if you use a static file storage 
that doesn't
allow missing files reference such as the ManifestStaticFilesStorage 

.

Simon

Le mardi 6 octobre 2015 14:40:01 UTC-4, François Schiettecatte a écrit :
>
> The '+' is an error, the line look more like this:
>
>  />
>
> On Tue, Oct 6, 2015 at 2:33 PM, I. Dié > 
> wrote:
>
>> I tried in your way to concatenate, I don't get any exception, but  the 
>> image image does'nt want to display. The plage only throw the "alt" value. 
>> Even for this line of code it's thing.
>>
>>
>> Le mardi 6 octobre 2015 19:51:04 UTC+2, Shawn Milochik a écrit :
>>>
>>> Try this:
>>>
>>> >> pet.name }} />
>>>
>>> You're embedding {{pet_name}} in a string. If this was a regular Python 
>>> statement, it would be like writing "Hello, {0}" and not having a format() 
>>> at the end.
>>>
>> -- 
>> 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/f29da80b-ffe4-421c-9aba-8ad76b87a484%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/6cca59fe-4a35-4dfc-bfac-5b2e722e8f02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.