On Tue, 22 Oct 2013, Russell Keith-Magee wrote:
> Hi Jasvir,
Hello Russell
> Frankly -- if something like this has happened, it's because Melange (the
I am really amazed that google uses such a software.
> We certainly haven't done anything strategically to avoid tagging the
> opportunity.
Tags
It seems there is a split reaction on whether or not models should assume
data is clean, and comes down to design decision.
I think that a docs patch explaining this entire concept to new users would
be sufficient for now (and I'm more than happy to spend time writing it).
Would any of the core d
Sounds good. I guess that may be an addition here:
https://docs.djangoproject.com/en/dev/ref/models/instances/#validating-objects
On Tuesday, October 22, 2013 8:40:46 AM UTC-4, Cal Leeming [Simplicity
Media Ltd] wrote:
>
> It seems there is a split reaction on whether or not models should assume
On 21.10.2013, at 15:57, Marc Tamlyn wrote:
> Hi Jannis,
>
> Let me know if you're in need of another committer at the sprint. Can't make
> any concrete promises as yet and I'd need to work out how cheaply I can get
> there, but I'd love to come assist if that's helpful.
Marc, absolutely, th
Ticket #20346 is the request that cache keys should be generated from a
request's full URL rather than path, and the proposed implementation of
this is backwards-incompatible.
Because the existing keys are a hash of the path, and so, so far as I know,
we do not have the original path needed to mig
On 22 oct. 2013, at 19:05, Jannis Leidel wrote:
> I know that Florian is going to be there and there are rumors that Aymeric
> will, too.
Yes, I'm coming!
--
Aymeric.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from
If all it meant was that currently cached content would effectively be
expired, I wouldn't see this as being anything more than an strong note.
But as I'm sure people have created their own tools for building the page
cache keys to forcibly expire them [and not yet taken advantage of that
function
It's almost here!
Tonight we've issued a release candidate for Django 1.6. Information,
including links to downloads and release notes, is available on the Django
project blog:
https://www.djangoproject.com/weblog/2013/oct/22/16c1/
--
You received this message because you are subscribed to the
Looks like an awesome release coming up! Big thanks to the Django team :)
Looking forward to trying it out.
One comment about the fact that set_password() now (correctly) makes blank
passwords valid. I could imagine some users have assumed that
set_password('') was the same as set_unusable_pass
Kudos for making this happen!
Small discrepancy: the blog post states python 2.7 is required; the
release notes it links to state python 2.6.5 is still supported, and 2.7
will be required from Django 1.7 onwards.
Yishai
On Wed, 23 Oct 2013 06:08:33 +0300, James Bennett
wrote:
It's al
10 matches
Mail list logo
