Re: Long-running tests

2010-04-16 Thread Paul McMillan
I'm hoping to be able to help with this problem during the SoC. In particular, I'm hoping that we can integrate unittest2 to make skipping these long-running tests easier. > And I know why. There are 10 of these: > >>> management.call_command('flush', verbosity=0, interactive=False) > for example,

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Tom X. Tobin
On Fri, Apr 16, 2010 at 11:13 PM, Jerome Leclanche wrote: > For one, there is no split between a -users mailing list and a > -developers mailing list. Understand that the Bazaar mailing list is > just as active as django-developers (so less active than -users + > -developers). But it does have on

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Jerome Leclanche
On Sat, Apr 17, 2010 at 6:35 AM, Tom X. Tobin wrote: > On Fri, Apr 16, 2010 at 10:10 PM, Russell Keith-Magee > wrote: >> However, at this point, I would like to tell you a story about four >> people named Everybody,  Somebody, Anybody, Nobody. > > This is exactly why I try not to bitch too much a

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Tom X. Tobin
On Fri, Apr 16, 2010 at 10:10 PM, Russell Keith-Magee wrote: > However, at this point, I would like to tell you a story about four > people named Everybody,  Somebody, Anybody, Nobody. This is exactly why I try not to bitch too much about Django's development process. It's very easy to complain,

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Russell Keith-Magee
On Sat, Apr 17, 2010 at 6:02 AM, orokusaki wrote: > When I first started posting things on trac, I put up a request that > took me an hour to create, explaining the justification, as well as > putting the code in there. I didn't know how to make a patch, and I > went about it the wrong way, but re

Re: Long-running tests

2010-04-16 Thread Karen Tracey
On Fri, Apr 16, 2010 at 11:00 PM, Tom X. Tobin wrote: > [snip details of run times] > > Sticking out like a sore thumb is API_TESTS under > modeltests.fixtures.models.__test__, which clocks in at 1090 > seconds(!). The serializer tests also seem to take a pretty chunk of > time at about 1-3 minut

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Russell Keith-Magee
On Sat, Apr 17, 2010 at 7:30 AM, George Sakkis wrote: > On Apr 15, 8:57 pm, Kevin Howerton wrote: > >> The level of resistance I see to change or outsider code contribution >> is an enormous de-motivator for people (like me) to want to make any >> contributions in the first place.  Why should I c

Long-running tests

2010-04-16 Thread Tom X. Tobin
I recently noticed that the Django test suite seemed to be ballooning in run time, so I wrote a new test runner that tracked run times. I set it to emit run times longer than two seconds, and had the following results (under PostgresSQL, since that's what we use in production): ** Long ru

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Tom X. Tobin
On Fri, Apr 16, 2010 at 9:36 PM, Russell Keith-Magee wrote: > On Sat, Apr 17, 2010 at 12:33 AM, sago wrote: >> >> On a completely unrelated note, any plans to move Django to git? > > I answered this exact question earlier in this thread. The answer is > no, because it would make exactly no differ

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Russell Keith-Magee
On Sat, Apr 17, 2010 at 12:33 AM, sago wrote: > > On a completely unrelated note, any plans to move Django to git? I answered this exact question earlier in this thread. The answer is no, because it would make exactly no difference to anything. Search out the earlier answer for more detail. Your

Re: Import problem starting with r12977

2010-04-16 Thread Derek Hoy
On Sat, Apr 17, 2010 at 12:36 AM, Derek Hoy wrote: > > I'll dig around a bit more. The problems seemed to come from the same models.py that was shared across the projects. I moved a couple of imports and it seems fine with trunk (r12996). So it looks like it's the change in the error handling th

Re: Import problem starting with r12977

2010-04-16 Thread Derek Hoy
Strange, I had the same problem and rolling back to 12976 fixed it. But another project still failed. It worked when I rolled back to r12949. http://code.djangoproject.com/changeset/12950 is the first of a few that deal with app loading. It may be our projects had import errors that weren't being

Re: High Level Discussion about the Future of Django

2010-04-16 Thread George Sakkis
On Apr 15, 8:57 pm, Kevin Howerton wrote: > The level of resistance I see to change or outsider code contribution > is an enormous de-motivator for people (like me) to want to make any > contributions in the first place. Why should I contribute a patch to > your flawed architecture if I'm going

Re: High Level Discussion about the Future of Django

2010-04-16 Thread George Sakkis
On Apr 15, 8:57 pm, Kevin Howerton wrote: > The level of resistance I see to change or outsider code contribution > is an enormous de-motivator for people (like me) to want to make any > contributions in the first place.  Why should I contribute a patch to > your flawed architecture if I'm going

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Tom Evans
On Fri, Apr 16, 2010 at 11:02 PM, orokusaki wrote: >... > I think I speak for a pretty broad user base when I say that folks who > use Django are bleeding edge developers who want cool stuff, and don't > mind paying a little extra to have it. It isn't like IBM and Microsoft > are using Django for

Re: High Level Discussion about the Future of Django

2010-04-16 Thread orokusaki
When I first started posting things on trac, I put up a request that took me an hour to create, explaining the justification, as well as putting the code in there. I didn't know how to make a patch, and I went about it the wrong way, but regardless of that, I put a lot of thought into it. Less than

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Tom X. Tobin
On Fri, Apr 16, 2010 at 4:34 PM, Taylor Marshall wrote: > On Fri, Apr 16, 2010 at 12:23 PM, Tom X. Tobin > wrote: >> None of this means that I think the core development process should >> change.  (Well, besides my fervent desire that they officially adopted >> git — and yes, I do believe it *wo

Re: High Level Discussion about the Future of Django

2010-04-16 Thread James Bennett
On Fri, Apr 16, 2010 at 4:34 PM, Taylor Marshall wrote: > There's already a unofficial mirror on GitHub which is maintained by jezdez: AFAIK there are mirrors on pretty much every DVCS/"social code" hosting site; bitbucket's got one as well, for example. -- "Bureaucrat Conrad, you are technica

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Taylor Marshall
On Fri, Apr 16, 2010 at 12:23 PM, Tom X. Tobin wrote: > None of this means that I think the core development process should > change.  (Well, besides my fervent desire that they officially adopted > git — and yes, I do believe it *would* make a difference, centralized > "official" branch and all —

Re: logialogin_required does not check User.is_active

2010-04-16 Thread subs...@gmail.com
Could the burden of this work be successfully (and sensibly) shifted to the backend itself by calling something like... deactivate()? In this event, the default backend's logic could be 'set is_active = False and expire cookie' and custom backends could do (or not do) whatever they want. Forgive

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Tom X. Tobin
On Fri, Apr 16, 2010 at 11:23 AM, Tom X. Tobin wrote: > But here's the great part: nothing is stoping anyone from hacking new Argh, the snoot in me just winced at re-reading my post and noticing that I misspelled "stopping". ::hangs head:: -- You received this message because you are subscribe

Import problem starting with r12977

2010-04-16 Thread Erik Stein
Hello -- I hope that's the correct place to ask, else point me to django-users. Starting with changeset http://code.djangoproject.com/changeset/12977 (Fixed #13328 -- Added a getstate/setstate pair to fields so that callable default values aren't pickled. Thanks to bkonkle for

Re: High Level Discussion about the Future of Django

2010-04-16 Thread sago
Isn't that what forking is for? A group of folks feel frustrated about not being able to commit, so they make their own copy of the source code available. A few months later they either implode when they realise just how much work it is going to take to do anything remotely sensible, or they come

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Tom X. Tobin
On Fri, Apr 16, 2010 at 10:32 AM, Jacob Kaplan-Moss wrote: > I'm not arguing that "stability, maturity, and longevity" are > "correct" priorities, only that, well, those are the ones we've > chosen. I'm not saying it's "wrong" to want more rapid improvement, > only that it's lower on *my* list. M

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Tom X. Tobin
On Fri, Apr 16, 2010 at 9:32 AM, Mike wrote: > On Apr 15, 3:32 pm, Jacob Kaplan-Moss wrote: >> For better or worse, we've chosen a development policy that >> prioritizes stability, maturity, and longevity. If those aren't your >> priorities, then perhaps a fork is the right answer. >> > Correct m

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Jacob Kaplan-Moss
On Fri, Apr 16, 2010 at 9:32 AM, Mike wrote: > Correct me if I'm wrong but I read it as "If you do not like our > policy then stability, maturity, and longevity aren't your priorities". > With all due respect it is not fair. But isn't that exactly what people in this thread are saying? The main c

Re: High Level Discussion about the Future of Django

2010-04-16 Thread Mike
On Apr 15, 3:32 pm, Jacob Kaplan-Moss wrote: > For better or worse, we've chosen a development policy that > prioritizes stability, maturity, and longevity. If those aren't your > priorities, then perhaps a fork is the right answer. > Correct me if I'm wrong but I read it as "If you do not like ou

Re: Pass Thru Image Proxy Patch Interest?

2010-04-16 Thread David Danier
> Yes, I was thinking the other day that it would be a cool solution for > serve() to be able to use storage backends Wouldn't it be better to have some {% serve path/to/file %} template tags, that does all the work of checking where the file exists and returning the right URL? Putting this into s

Re: Pass Thru Image Proxy Patch Interest?

2010-04-16 Thread Suno Ano
This blog post http://bit.ly/a4iyJ6 also talks about the ability to use what is called a remote URL to eventually server content (read content delivery network). In my opinion it also has a pretty good solution about caching images when setting up a pass though image proxy solution. -- You recei