Re: "Design Decision Needed" is gone. Good riddance.

[Lennart Regebro]

On Tue, Apr 9, 2013 at 12:02 AM, Jeremy Dunck  wrote:
> "easy" is for people new to contributing django or to open source in
> general.  Your view of "easy" may be different than our intended
> meaning. :)

Well, fair enough. :-) Maybe I can say it like this: I found that
those with easy pickings were generally of the same class as those
without.

But I could be wrong of course.

//Lennart

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Design Decision Needed" is gone. Good riddance.

[Lennart Regebro]

On Mon, Apr 8, 2013 at 4:57 PM, Jacob Kaplan-Moss  wrote:
> Thanks, please let me know if you have questions!

Nope, but a suggestion: Mark new tickets as "easy pickings" by
default. During the sprint I didn't find any ticket that wasn't either
more than a year old (often indeed flagged as DDN) or easy. :-)

//Lennart

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Switch to database-level autocommit

[Lennart Regebro]

On Fri, Mar 1, 2013 at 4:11 PM, Alex Gaynor  wrote:
> FWIW: any sort of scheme where a transaction is kept open all request
> (including a transaction that only ever reads), will cause you serious pain
> if you're trying to do migrations on MySQL with traffic.

Wouldn't the transaction be opened when you make modifications, and
closed once the reqeust returns? Ie, in a typical read situation: No
transaction. In the typical write situation, the transaction is
started somewhere in the view, and closed once an HTTP redirect is
returned?

I do agree that 99.9% of the sites committing on the end of the
request is the right thing to do, and do think that this should be the
default, although I realize that debate is already lost.

//Lennart

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.