Thanks for the extra details Jacob. I had a bit of time and thought
it was an interesting challenge so I created a Google Script based
twitter bot that tweets the title and links of everything posted to
the Django Announce Google group.
There may be bugs but so far it's working, you can check it
On Tue, Apr 2, 2013 at 11:02 PM, Russell Keith-Magee
wrote:
> In short, no - Twitter isn't a particularly reliable source for updates.
> Someone in the core team will usually tweet about the release, but since
> it's hard to share logins to a single Twitter account, and the person who
> owns Djang
That makes sense, thanks for the explanation and the pointers to the
best sources of information. I never realized the Django announce
mailing list existed, it will serve my purposes perfectly as I'm sure
it's intended to!
Regards,
Josh
On Apr 2, 9:02 pm, Russell Keith-Magee
wrote:
> Hi Josh,
>
Hi Josh,
In short, no - Twitter isn't a particularly reliable source for updates.
Someone in the core team will usually tweet about the release, but since
it's hard to share logins to a single Twitter account, and the person who
owns Django's twitter account won't always be involved in formally cu
Thanks for the release!
Kind of random question, but this seems like the best place to ask
it. I used to use Twitter mobile notifications to keep up with Django
releases, but I've noticed that the last three releases (since 1.4.4)
have not been announced on Django's Twitter. Is this just an over
Hi folks --
We've just released Django 1.5.1, a bug fix release that cleans up a
couple issues with last month's 1.5 release.
The biggest fix is for a memory leak introduced in Django 1.5. Under
certain circumstances, repeated iteration over querysets could leak
memory - sometimes quite a bit of
