On 8/13/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 8/13/06, Jakub Labath <[EMAIL PROTECTED]> wrote:
> > 2. Due to time/money reasons I am running a relatively old version of
> > django. I realise that by doing that I'm left on my own. However It
> > would be nice to be able to go to Trac
Hi,
Thanks everybody for the info.
James, thanks for the effort to still support the 0.91 branch, It's
much appreciated.
Best
jakub
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
On 8/13/06, Jakub Labath <[EMAIL PROTECTED]> wrote:
> 2. Due to time/money reasons I am running a relatively old version of
> django. I realise that by doing that I'm left on my own. However It
> would be nice to be able to go to Trac or somewhere and see all
> security related bugs/fixes so that
We recently discussed the security policy in light of the recent Rails
shenanigans here:
http://groups.google.com/group/django-developers/browse_thread/thread/7a647b883d637920
The new django-announce mailing list should keep you abreast of
security issues.
--Simon
On 8/13/06, Jakub Labath <[EMAIL PROTECTED]> wrote:
> 2. Due to time/money reasons I am running a relatively old version of
> django. I realise that by doing that I'm left on my own. However It
> would be nice to be able to go to Trac or somewhere and see all
> security related bugs/fixes so that
Hi,
At the company I work for most of the sites run django and I have been
pushing hard for it's adoption, while facing a lot of adversity from
all kinds of camps most notably the .NET and java.
I have already proven that django/python is enterprise ready, faster
to develop in, and performs
