During the first half of the week I assisted with a couple of final bugs in
1.8. I also did some other release preparation tasks, like updating the
djangoproject.com downloads page (which is mostly programatically
generated) to accommodate two supported LTS versions (otherwise 1.4 would
have
Stan, 01 Apr 2015 04:46:
> Hi devs,
>
> Is there a good reason for having the shebang line in django-admin.py at
> #!/usr/bin/python
> "instead" of #!/usr/bin/env python ?
is there a good reason to use the latter?
"env python" is a terrible hack for systems that
are way behind with their "offic
On Saturday 04 April 2015 21:16:54 Michael Manfre wrote:
> On Sat, Apr 4, 2015 at 12:56 PM, Thomas Tanner wrote:
> > I think rare LTS releases and frequent (6month) incremental upgrades are
> > a good compromise.
> > Third-party packages should support LTS releases and at least the latest
> > Djan
On Sat, Apr 4, 2015 at 12:56 PM, Thomas Tanner wrote:
> I think rare LTS releases and frequent (6month) incremental upgrades are
> a good compromise.
> Third-party packages should support LTS releases and at least the latest
> Django version. They may drop support for earlier non-LTS releases.
>
I think rare LTS releases and frequent (6month) incremental upgrades are
a good compromise.
Third-party packages should support LTS releases and at least the latest
Django version. They may drop support for earlier non-LTS releases.
Either you stick with the LTS release or you go with the cutting e
I agree that DKIM is the responsibility of an MTA, not Django.
Alex
On Sat, Apr 4, 2015 at 6:53 AM, Bruno Ribeiro da Silva <
bruno.dev...@gmail.com> wrote:
> I do think DKIM is a task for the MTA too, so it doesn't make much sense
> to have it in django's core.
> On Apr 4, 2015 6:27 AM, "Claude
Am 04.04.2015 14:30, schrieb Tim Graham:
Now that Django 1.8 is released, I wanted to bump this thread for
discussion so we can hopefully ratify this schedule or modify it based
on feedback. In particular, I heard a concern that a six month release
schedule may be too often for the community. O
Now that Django 1.8 is released, I wanted to bump this thread for
discussion so we can hopefully ratify this schedule or modify it based on
feedback. In particular, I heard a concern that a six month release
schedule may be too often for the community. On the other hand, I think
smaller release
I do think DKIM is a task for the MTA too, so it doesn't make much sense to
have it in django's core.
On Apr 4, 2015 6:27 AM, "Claude Paroz" wrote:
> Le vendredi 3 avril 2015 19:05:02 UTC+2, Loek van Gent a écrit :
>>
>> Hi all,
>>
>> Is anyone using DKIM signing for densing emails? Does it make
Le vendredi 3 avril 2015 19:05:02 UTC+2, Loek van Gent a écrit :
>
> Hi all,
>
> Is anyone using DKIM signing for densing emails? Does it make sense to you
> to have a feature like that in Django core or is this typically something
> that should be in it's own app?
>
I think that generally DKIM
10 matches
Mail list logo