Re: Apache2 hates my Django deployment method

[Mike Dewhirst]

On 12/12/2022 11:32 am, Jason wrote:
https://serverfault.com/questions/1058677/apache-2-4-37-reload-causes-error-scoreboard-is-full-not-at-maxrequestworkers 



and

https://serverfault.com/questions/1084635/apache-mpm-workers-stuck-in-g-gracefully-finishing-growing-scoreboard-is-fu

seems reloading is problematic because

>When you gracefully reload Apache, you're terminating the containing 
process. What is happening here is Apache is making each thread wait 
until all the threads in the containing process have completed prior 
to restarting the container PID.


> So, in you're case, you've got a single thread contained in all the 
processes in that list that is still busy or stuck somehow.




I had seen the first of those links and abandoned reload in logrotate. I 
now copytruncate instead with no restarting. That was advice from the 
very friendly Apache list.


I don't think I have the brainspace to identify the actual cause. My 
best strategy (I think) is to restart on redeployment and wait for for 
Apache to self-heal. If it is Apache's fault.


Thanks for jumping in

Cheers

Mike



On Sunday, December 11, 2022 at 5:45:40 PM UTC-5 Mike Dewhirst wrote:

On 12/12/2022 1:33 am, Jason wrote:

AFAIK, restarting apache process on deployment is standard, is
there a reason you don't want to do that?


With Ubuntu 2020.04 and the version of Apache which came with
that, reload worked fine and I always thought that was the right
way to redeploy.

The newer version of Apache or probably more particularly the
newer mpm-event module had a bug whereby ...

[Sun Dec 11 02:09:18.196035 2022] [mpm_event:error] [pid 893:tid
139808992921472] AH03490: scoreboard is full, not at
MaxRequestWorkers.Increase ServerLimit.

... and that consumed resources until Apache crashed. Hence my
questions on the Apache list which resulted in adjusted mpm-event
config recommended by gurus.

Currently, reloading triggers the above error about once per second.

Then issuing a restart generates ...

[Sun Dec 11 02:15:28.478942 2022] [mpm_event:notice] [pid 893:tid
139808992921472] AH00492: caught SIGWINCH, shutting down gracefully
[Sun Dec 11 02:15:31.840212 2022] [core:warn] [pid 893:tid
139808992921472] AH00045: child process 909 still did not exit,
sending a SIGTERM

... and that [core:warn] message repeats for the same pid but a
bunch of different child processes for however many there are
until it changes to a [core:error] for the same bunch ...

[Sun Dec 11 02:15:37.883824 2022] [core:error] [pid 893:tid
139808992921472] AH00046: child process 7868 still did not exit,
sending a SIGKILL
[Sun Dec 11 02:15:50.816477 2022] [mpm_event:notice] [pid
45163:tid 140392171792256] AH00489: Apache/2.4.52 (Ubuntu)
OpenSSL/3.0.2 mod_wsgi/4.9.0 Python/3.10 configured -- resuming
normal operations

... until Apache restarts.

So I reckon there is something wrong.

I now restart Apache on redeployment but it still goes through the
[core:warn] and [core:error] before restarting if I have done a
reload.

I guess I'll give up reloading.

Thanks for responding

Cheers

Mike




Templates are picked up because they're not evaluated and
compiled, rather they're processed dynamically so any changes
there do not require a restart.

On Saturday, December 10, 2022 at 9:34:42 PM UTC-5 Mike Dewhirst
wrote:

Server Version: Apache/2.4.52 (Ubuntu 2022.04) OpenSSL/3.0.2
mod_wsgi/4.9.0 Python/3.10
Server MPM: event
Server Built: 2022-09-30T04:09:50

Apache *seems* to hang onto something and eventually crashes
after I reload it after deploying a Python file.

That is either scripted (delete site and re-export from repo)
or drag and drop a py file using Filezilla on Windows.

It *seems* ok if I redeploy html templates.

I have asked on the Apache mailing list and the consensus
seems to be that something is "hogging" the mpm-event workers
and I have to figure out what and solve that.

The only solution I have is to restart Apache.

I have to think this is happening in other projects so I'm
wondering if anyone has solved this?

Thanks for any feedback

Mike

-- 
Signed email is an absolute defence against phishing. This email has

been signed with my private key. If you import my public key you can
automatically decrypt my signature and be sure it came from me. Just
ask and I'll send it to you. Your email software can handle signing.

-- 
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 view this discussion on the web visit

Re: URL evaluates to 'slug' literally instead of the variable slug

[Michael Starr]

It's poorly written and mine isn't. Am I better than them.

On Monday, December 5, 2022 at 6:36:30 AM UTC-8 elvisa...@gmail.com wrote:

> Good !
>
> Le dim. 4 déc. 2022 à 22:04, Michael Starr  a 
> écrit :
>
>> Thank you, Peter. I forgot to acknowledge your contribution.
>>
>> On Wednesday, November 30, 2022 at 4:43:47 PM UTC-8 Ryan Nowakowski wrote:
>>
>>> On Wed, Nov 30, 2022 at 09:16:39AM -0800, Michael Starr wrote: 
>>> > Thank you. Though, that hard codes everything, which is bad. How do I 
>>> > generalize it? 
>>>
>>> You'll need to do 2 things: 
>>>
>>> 1. Add the pet(s) you want to the template context, probably by 
>>> implementing get_context_data[1]. 
>>>
>>> 2. Change your template to use the pet from the template context instead 
>>> of the hard code pet, Mocha. Assuming your pet in the template context is 
>>> named 'pet': 
>>>
>>> Pet Profile: {{ pet.name 
>>> }} 
>>>
>>> ...alternatively since you've implemented get_absolute_url: 
>>>
>>> Pet Profile: {{ pet.name }} 
>>>
>>>
>>> [1] 
>>> https://docs.djangoproject.com/en/4.1/ref/class-based-views/mixins-simple/#django.views.generic.base.ContextMixin.get_context_data
>>>  
>>>
>> -- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/e8afb697-d067-4cc6-bda8-93dd9b8748een%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c209ab85-1e49-47f0-a6a2-570b48f37021n%40googlegroups.com.

Re: Apache2 hates my Django deployment method

[Jason]

https://serverfault.com/questions/1058677/apache-2-4-37-reload-causes-error-scoreboard-is-full-not-at-maxrequestworkers
 

and 

https://serverfault.com/questions/1084635/apache-mpm-workers-stuck-in-g-gracefully-finishing-growing-scoreboard-is-fu

seems reloading is problematic because

>When you gracefully reload Apache, you're terminating the containing 
process. What is happening here is Apache is making each thread wait until 
all the threads in the containing process have completed prior to 
restarting the container PID.

> So, in you're case, you've got a single thread contained in all the 
processes in that list that is still busy or stuck somehow.



On Sunday, December 11, 2022 at 5:45:40 PM UTC-5 Mike Dewhirst wrote:

> On 12/12/2022 1:33 am, Jason wrote:
>
> AFAIK, restarting apache process on deployment is standard, is there a 
> reason you don't want to do that?
>
>
> With Ubuntu 2020.04 and the version of Apache which came with that, reload 
> worked fine and I always thought that was the right way to redeploy. 
>
> The newer version of Apache or probably more particularly the newer 
> mpm-event module had a bug whereby ...
>
> [Sun Dec 11 02:09:18.196035 2022] [mpm_event:error] [pid 893:tid 
> 139808992921472] AH03490: scoreboard is full, not at 
> MaxRequestWorkers.Increase ServerLimit.
>
> ... and that consumed resources until Apache crashed. Hence my questions 
> on the Apache list which resulted in adjusted mpm-event config recommended 
> by gurus.
>
> Currently, reloading triggers the above error about once per second.
>
> Then issuing a restart generates ...
>
> [Sun Dec 11 02:15:28.478942 2022] [mpm_event:notice] [pid 893:tid 
> 139808992921472] AH00492: caught SIGWINCH, shutting down gracefully
> [Sun Dec 11 02:15:31.840212 2022] [core:warn] [pid 893:tid 
> 139808992921472] AH00045: child process 909 still did not exit, sending a 
> SIGTERM
>
> ... and that [core:warn] message repeats for the same pid but a bunch of 
> different child processes for however many there are until it changes to a 
> [core:error] for the same bunch ...
>
> [Sun Dec 11 02:15:37.883824 2022] [core:error] [pid 893:tid 
> 139808992921472] AH00046: child process 7868 still did not exit, sending a 
> SIGKILL
> [Sun Dec 11 02:15:50.816477 2022] [mpm_event:notice] [pid 45163:tid 
> 140392171792256] AH00489: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 
> mod_wsgi/4.9.0 Python/3.10 configured -- resuming normal operations
>
> ... until Apache restarts.
>
> So I reckon there is something wrong.
>
> I now restart Apache on redeployment but it still goes through the 
> [core:warn] and [core:error] before restarting if I have done a reload.
>
> I guess I'll give up reloading.
>
> Thanks for responding
>
> Cheers
>
> Mike
>
>
>
> Templates are picked up because they're not evaluated and compiled, rather 
> they're processed dynamically so any changes there do not require a restart.
>
> On Saturday, December 10, 2022 at 9:34:42 PM UTC-5 Mike Dewhirst wrote:
>
>> Server Version: Apache/2.4.52 (Ubuntu 2022.04) OpenSSL/3.0.2 
>> mod_wsgi/4.9.0 Python/3.10 Server MPM: event Server Built: 
>> 2022-09-30T04:09:50 Apache *seems* to hang onto something and eventually 
>> crashes after I reload it after deploying a Python file.
>>
>> That is either scripted (delete site and re-export from repo) or drag and 
>> drop a py file using Filezilla on Windows.
>>
>> It *seems* ok if I redeploy html templates.
>>
>> I have asked on the Apache mailing list and the consensus seems to be 
>> that something is "hogging" the mpm-event workers and I have to figure out 
>> what and solve that.
>>
>> The only solution I have is to restart Apache.
>>
>> I have to think this is happening in other projects so I'm wondering if 
>> anyone has solved this?
>>
>> Thanks for any feedback
>>
>> Mike
>>
>> -- 
>> Signed email is an absolute defence against phishing. This email has
>> been signed with my private key. If you import my public key you can
>> automatically decrypt my signature and be sure it came from me. Just
>> ask and I'll send it to you. Your email software can handle signing.
>>
>> -- 
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/8853bc85-97fb-48d7-af94-0807f777c0fan%40googlegroups.com
>  
> 
> .
>
>
>
> -- 
> Signed email is an absolute defence against phishing. This email has
> been signed with my private key. If you import my public key you can
> automatically decrypt my signature and be sure it came from me. Just
> ask and I'll send it to you. Your email software can handle signing.
>
>

-- 
You received this message because you are 

Re: Apache2 hates my Django deployment method

[Mike Dewhirst]

On 12/12/2022 1:33 am, Jason wrote:
AFAIK, restarting apache process on deployment is standard, is there a 
reason you don't want to do that?


With Ubuntu 2020.04 and the version of Apache which came with that, 
reload worked fine and I always thought that was the right way to redeploy.


The newer version of Apache or probably more particularly the newer 
mpm-event module had a bug whereby ...


[Sun Dec 11 02:09:18.196035 2022] [mpm_event:error] [pid 893:tid 
139808992921472] AH03490: scoreboard is full, not at 
MaxRequestWorkers.Increase ServerLimit.


... and that consumed resources until Apache crashed. Hence my questions 
on the Apache list which resulted in adjusted mpm-event config 
recommended by gurus.


Currently, reloading triggers the above error about once per second.

Then issuing a restart generates ...

[Sun Dec 11 02:15:28.478942 2022] [mpm_event:notice] [pid 893:tid 
139808992921472] AH00492: caught SIGWINCH, shutting down gracefully
[Sun Dec 11 02:15:31.840212 2022] [core:warn] [pid 893:tid 
139808992921472] AH00045: child process 909 still did not exit, sending 
a SIGTERM


... and that [core:warn] message repeats for the same pid but a bunch of 
different child processes for however many there are until it changes to 
a [core:error] for the same bunch ...


[Sun Dec 11 02:15:37.883824 2022] [core:error] [pid 893:tid 
139808992921472] AH00046: child process 7868 still did not exit, sending 
a SIGKILL
[Sun Dec 11 02:15:50.816477 2022] [mpm_event:notice] [pid 45163:tid 
140392171792256] AH00489: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 
mod_wsgi/4.9.0 Python/3.10 configured -- resuming normal operations


... until Apache restarts.

So I reckon there is something wrong.

I now restart Apache on redeployment but it still goes through the 
[core:warn] and [core:error] before restarting if I have done a reload.


I guess I'll give up reloading.

Thanks for responding

Cheers

Mike




Templates are picked up because they're not evaluated and compiled, 
rather they're processed dynamically so any changes there do not 
require a restart.


On Saturday, December 10, 2022 at 9:34:42 PM UTC-5 Mike Dewhirst wrote:

Server Version: Apache/2.4.52 (Ubuntu 2022.04) OpenSSL/3.0.2
mod_wsgi/4.9.0 Python/3.10
Server MPM: event
Server Built: 2022-09-30T04:09:50

Apache *seems* to hang onto something and eventually crashes after
I reload it after deploying a Python file.

That is either scripted (delete site and re-export from repo) or
drag and drop a py file using Filezilla on Windows.

It *seems* ok if I redeploy html templates.

I have asked on the Apache mailing list and the consensus seems to
be that something is "hogging" the mpm-event workers and I have to
figure out what and solve that.

The only solution I have is to restart Apache.

I have to think this is happening in other projects so I'm
wondering if anyone has solved this?

Thanks for any feedback

Mike

-- 
Signed email is an absolute defence against phishing. This email has

been signed with my private key. If you import my public key you can
automatically decrypt my signature and be sure it came from me. Just
ask and I'll send it to you. Your email software can handle signing.

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8853bc85-97fb-48d7-af94-0807f777c0fan%40googlegroups.com 
.



--
Signed email is an absolute defence against phishing. This email has
been signed with my private key. If you import my public key you can
automatically decrypt my signature and be sure it came from me. Just
ask and I'll send it to you. Your email software can handle signing.

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/24597590-6cdd-9c25-2b7d-1b9327a2d028%40dewhirst.com.au.


OpenPGP_signature
Description: OpenPGP digital signature

Re: Arrayfield constraint issue in 4.1

[James Gillard]

The callable list is indeed assigned as the default for the ArrayField, as 
documented 
here: 
https://docs.djangoproject.com/en/4.1/ref/contrib/postgres/fields/#django.contrib.postgres.fields.ArrayField

The original issue has already had a patch merged, which will be released 
in 4.1.5, see the fix 
here: https://docs.djangoproject.com/en/dev/releases/4.1.5/

On Sunday, 11 December 2022 at 18:02:24 UTC manjushak...@gmail.com wrote:

> Hello Sir, I need to understand the form.py  file because , what  is the 
> only list you have assigned as default in arrayfield, is it the method 
> list() ?
>  
>
> On Sat, Dec 10, 2022 at 10:00 PM James Gillard  
> wrote:
>
>> Thanks for the feedback. I opened a ticket and it was indeed confirmed as 
>> a bug: https://code.djangoproject.com/ticket/34205
>>
>> On Thursday, 8 December 2022 at 15:04:40 UTC Ryan Nowakowski wrote:
>>
>>> Might be a bug. Check the release notes for the post 4.0.8 versions to 
>>> see if anything related changed. File a bug with the simplest example code 
>>> that demonstrates the issue.
>>>
>>>
>>> On December 8, 2022 6:37:52 AM CST, James Gillard <
>>> ja...@journeetrips.com> wrote:

 I can't yet work out whether this is a Django bug or how I'm using 
 model constraints... Upgraded from 4.0.8 to 4.1.4 and have hit this issue 
 when saving this model in the admin. I'd read in the release notes that 
 these constraints would be validated on model save, and that's the code 
 that's leading to this exception. If it's not something I've done, it 
 seems 
 ArrayField isn't working with this new validation of my condition. The 
 same 
 happens for Q(phone_numbers__len__gte=0), and the error disappears if I 
 comment out this condition. It seems the generated code might be wrong, as 
 I see 12 "%s" and only 11 elements in params. All it's trying to do is 
 ensure that an empty list isn't considered unique.

 Here's the failing model:

 phone_numbers = ArrayField(models.CharField(max_length=200), 
 default=list, blank=True)

 class Meta:
 constraints = [
 models.UniqueConstraint(
fields=['phone_numbers'],
condition=~Q(phone_numbers__len=0),
name='unique_email_phones',
 ),
 ]
 )

 [image: Screenshot 2022-12-08 at 12.30.35.png]

 -- 
>> 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 view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/4a8a0941-dd65-4c22-bf16-4e11181794a0n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/29d9d224-3027-4346-9552-8fcadedd21dfn%40googlegroups.com.

Re: Job openings with in Python

[Gobi Dasu]

Hi Manjusha and also others with relevant skill sets,

I noticed you have a strong, in-demand skill set. We'd love to have you
join our talent network of software developers, data scientists, and
designers, called LD Talent - ldtalentwork.com. By joining LD Talent,
you’ll have the following benefits:

- Explore remote opportunities: both contract and full-time, with US-based
companies
- Set your own hourly rate and work on your own schedule
- Gain financial incentives upon posting new learnings on our Github/Blog -
blog.ldtalentwork.com
- Get funded to build your own ideas through the LD Ventures wing

You can become a part of the network by sending your resume to
i...@ldtalentwork.com and learn more about how you can advance your career.
If you have any questions, here’s our bookable calendar -
ldtalentwork.com/contact/
.

Thank you.

*Regards,*
*Gobi Dasu*  (calendar
)
*Stanford CS **·* *Northwestern HCI*
*LD Talent  *(demo
)


On Fri, Dec 9, 2022 at 8:27 AM Manjusha 
wrote:

> Hello everyone,
> I am last year student of computer branch,
> I have learned Django Framework and also built projects.
> This is my GitHub Link : https://github.com/manjusha-0103,
> I have added my resume.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/569632bd-86fd-4f61-8a00-50873bb72c85n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAMk8evmxOzqguLPxjjVBKgUz%3D_74q_L-FW%3Dp8JAp6ug1ztmDZA%40mail.gmail.com.

Re: Arrayfield constraint issue in 4.1

[Manjusha]

Hello Sir, I need to understand the form.py  file because , what  is the
only list you have assigned as default in arrayfield, is it the method
list() ?


On Sat, Dec 10, 2022 at 10:00 PM James Gillard 
wrote:

> Thanks for the feedback. I opened a ticket and it was indeed confirmed as
> a bug: https://code.djangoproject.com/ticket/34205
>
> On Thursday, 8 December 2022 at 15:04:40 UTC Ryan Nowakowski wrote:
>
>> Might be a bug. Check the release notes for the post 4.0.8 versions to
>> see if anything related changed. File a bug with the simplest example code
>> that demonstrates the issue.
>>
>>
>> On December 8, 2022 6:37:52 AM CST, James Gillard 
>> wrote:
>>>
>>> I can't yet work out whether this is a Django bug or how I'm using model
>>> constraints... Upgraded from 4.0.8 to 4.1.4 and have hit this issue when
>>> saving this model in the admin. I'd read in the release notes that these
>>> constraints would be validated on model save, and that's the code that's
>>> leading to this exception. If it's not something I've done, it seems
>>> ArrayField isn't working with this new validation of my condition. The same
>>> happens for Q(phone_numbers__len__gte=0), and the error disappears if I
>>> comment out this condition. It seems the generated code might be wrong, as
>>> I see 12 "%s" and only 11 elements in params. All it's trying to do is
>>> ensure that an empty list isn't considered unique.
>>>
>>> Here's the failing model:
>>>
>>> phone_numbers = ArrayField(models.CharField(max_length=200),
>>> default=list, blank=True)
>>>
>>> class Meta:
>>> constraints = [
>>> models.UniqueConstraint(
>>>fields=['phone_numbers'],
>>>condition=~Q(phone_numbers__len=0),
>>>name='unique_email_phones',
>>> ),
>>> ]
>>> )
>>>
>>> [image: Screenshot 2022-12-08 at 12.30.35.png]
>>>
>>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/4a8a0941-dd65-4c22-bf16-4e11181794a0n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAGz3pXKTMhbZjuxQh-GkufLhgFuBVpGjNhWLDVe-NDNQDTYZfA%40mail.gmail.com.

Re: Apache2 hates my Django deployment method

[Jason]

AFAIK, restarting apache process on deployment is standard, is there a 
reason you don't want to do that?

Templates are picked up because they're not evaluated and compiled, rather 
they're processed dynamically so any changes there do not require a restart.

On Saturday, December 10, 2022 at 9:34:42 PM UTC-5 Mike Dewhirst wrote:

> Server Version: Apache/2.4.52 (Ubuntu 2022.04) OpenSSL/3.0.2 
> mod_wsgi/4.9.0 Python/3.10 Server MPM: event Server Built: 
> 2022-09-30T04:09:50 Apache *seems* to hang onto something and eventually 
> crashes after I reload it after deploying a Python file.
>
> That is either scripted (delete site and re-export from repo) or drag and 
> drop a py file using Filezilla on Windows.
>
> It *seems* ok if I redeploy html templates.
>
> I have asked on the Apache mailing list and the consensus seems to be that 
> something is "hogging" the mpm-event workers and I have to figure out what 
> and solve that.
>
> The only solution I have is to restart Apache.
>
> I have to think this is happening in other projects so I'm wondering if 
> anyone has solved this?
>
> Thanks for any feedback
>
> Mike
>
> -- 
> Signed email is an absolute defence against phishing. This email has
> been signed with my private key. If you import my public key you can
> automatically decrypt my signature and be sure it came from me. Just
> ask and I'll send it to you. Your email software can handle signing.
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8853bc85-97fb-48d7-af94-0807f777c0fan%40googlegroups.com.