Re: Deploying a django application to apach2 on Ubuntu

Hey, this post is definitely for the django-users mailing list. This mailing list is solely for the discussion of django development itself. That is, discussion about development of the core libraries. Cheers, David On Sat, Jan 29, 2011 at 6:46 PM, Maxim Mai wrote: >

Re: Query String missing in a GET request

Hello, This is a mailing list to discuss the development of the django framework itself. Please post your question to django-users :) If you find there is an actual bug at play, you may be redirected here.. Cheers, David On Tue, Nov 23, 2010 at 3:54 AM, guilhelm

Re: Bug with testing framework when not using contrib.auth

This is certainly an artifact of the fact that messages recent started supporting anonymous messages. Previously it depended on auth. I suspect you just need to open a ticket for this. On Wed, Nov 3, 2010 at 4:43 AM, Yo-Yo Ma wrote: > I have a large application that

Re: Start project not working

Hello, this mailing list is to discuss the development of django itself. Please use django-users for questions like yours :) David On Fri, Oct 29, 2010 at 4:03 PM, aravind wrote: > I installed python2.5 and django official > > version and also copied admin.py in > > scripts

Re: #6735 -- Class based generic views: call for comment

On Tue, Oct 5, 2010 at 5:21 AM, George Sakkis wrote: > > Since dispatch is going to be defined on the base View class, can't we > omit it from the urlconf and have the URLresolver do: > >  if isinstance(view, type) and issubclass(view, View): >      view = view.dispatch

Re: Contributing more

Hey, I've been working on tickets that don't have tests or patches or both, to help move them along :) I've found it a good way to get involved with things that aren't too contentious. There are a few documentation bugs as well. Others will certainly have their own take on it too... David On

Re: #6735 -- Class based generic views: call for comment

Sorry, I keep top replying in my emails. It's because I'm mostly taking everything in and not really replying to anyone specifically. I _really_ like the idea of View being synonymous with a ResponseFactory. Using __call__: The view base class can take *args and **kwargs and apply them lazily

Re: #6735 -- Class based generic views: call for comment

On Sat, Oct 2, 2010 at 12:26 PM, Ian Lewis wrote: > On Sat, Oct 2, 2010 at 12:20 AM, Alex Gaynor wrote: >> Not really.  The big win from a class-based view is not being able to >> store state, you can do that with local variables, it's being able to >>

Re: #6735 -- Class based generic views: call for comment

October 2, 2010, David P. Novakovic > <davidnovako...@gmail.com> wrote: >> My problem with all of this is that it feels like a hell of a lot of >> hoopjumping to deal with something that could be solved in the >> Resolver. >> >> I may be missing s

Re: #6735 -- Class based generic views: call for comment

Sorry in my previous email you could simply pass the uninstantiated class in the url pattern. url(r'...',MyOOView,...) On Sat, Oct 2, 2010 at 8:57 AM, David P. Novakovic <davidnovako...@gmail.com> wrote: > My problem with all of this is that it feels like a hell of a lot of > hoopjum

Re: #6735 -- Class based generic views: call for comment

My problem with all of this is that it feels like a hell of a lot of hoopjumping to deal with something that could be solved in the Resolver. I may be missing something obvious here, so please tell me if I am.. but couldn't the resolver just check that quacks like something OOViewish has been

Re: four NoSQL backends you want? :)

This has probably been discussed at great length previously... but my 2c follows: If you are using a column/doc store you are trying to solve a different problem than if you are using an SQL db. How important is 100% interop? Surely it's about documenting the differences between them and

Re: Proposal: Meta.required_together

Is it? I read this as different to anything in the ORM. This is about conditionally requiring a second field if one is filled out. Normally it would be done at the JS level. I think it's a good idea, assuming I haven't missed something that already does this. I can't help thinking this is part

Re: #12012 Logging: request for comments

Hey mate, Great stuff! A cursory glance shows there isn't anything to log debug output from url resolution.. something I think I need to add.. I'll busy a ticket for it :) D On Sat, Sep 25, 2010 at 4:16 PM, Russell Keith-Magee wrote: > Hi all, > > I've just uploaded a

Re: Something.is_live instead of implementation specific is_live settings

This link and the comments suggest some good stuff... particularly the comment from Malcolm and the original post. http://www.protocolostomy.com/2009/08/17/django-settings-in-dev-and-production-why-the-hoops/ On Fri, Sep 24, 2010 at 10:01 AM, David P. Novakovic <davidnovako...@gmail.com>

Re: Something.is_live instead of implementation specific is_live settings

ing built in. For > instance, passing a variable to the "Development" server to tell it > you're in "Development" seems a bit redundant, no? > > On Sep 23, 3:39 pm, "David P. Novakovic" <davidnovako...@gmail.com> > wrote: >> As for running dif

Re: 'User' object has no attribute 'backend' - issue with using auth.login()

previously. Thoughts anyone? On Fri, Sep 24, 2010 at 9:32 AM, David P. Novakovic <davidnovako...@gmail.com> wrote: > Apart from being slightly offended at you posting a Joel Spolski link > to make a point, I'll address the actual issue at hand :P > > These docs pretty clearly show auth

Re: 'User' object has no attribute 'backend' - issue with using auth.login()

ue, as as simple User object will not suffice. It should say, > "It takes an HttpRequest object and a User object that has been run > through the function authenticate() first to alter the auth backends > that are attached as attributes to it.". > > This has very bad code smell, IMHO.

Re: 'User' object has no attribute 'backend' - issue with using auth.login()

This probably should have been posted to django-users anyway. Chances are, getting a stacktrace like this one or the last error you posted are actually problems with your code and not django itself. Unless you can show that it is actually a problem with django and not the way you are using it,

Re: Something.is_live instead of implementation specific is_live settings

As for running different configs: manage.py runserver --settings=settings_test etc.. On Fri, Sep 24, 2010 at 7:25 AM, Jacob Kaplan-Moss wrote: > On Thu, Sep 23, 2010 at 3:33 PM, Yo-Yo Ma wrote: >> I'm simply proposing the idea of having the

Re: Inclusion of easy-thumbnails into Django Contrib

question is not "can it be included?" but why is it a problem that this is a third party lib at the moment? Is there a strong case that it be better if it was part of django core or does it do its job just fine the way it is now? David On Thu, Sep 16, 2010 at 3:09 PM, David P.

Re: Inclusion of easy-thumbnails into Django Contrib

I don't want to sound negative, but answering your own question before anyone else can doesn't change the answer ;) D On Thu, Sep 16, 2010 at 3:00 PM, Yo-Yo Ma wrote: > Is there any plans to incorporate > http://github.com/SmileyChris/easy-thumbnails/ > into

Re: Error email flooding on high traffic production sites

Hey dude, What about something like sentry or lumberjack? I haven't looked at them too seriously, but I'd imagine there'd be a way to do smarter summarizing of emails etc..? D On Thu, Sep 9, 2010 at 1:26 PM, Simon Litchfield wrote: > Hi all > > Default behaviour of

Re: Feature request - set variables in template

to correct me here :) On Fri, Aug 27, 2010 at 10:21 AM, Yo-Yo Ma <baxterstock...@gmail.com> wrote: > You absolutely cannot. The "with" statement puts the variable in the > scope of the "with" statement only, not to mention that would not be > very explicit at all

Re: Feature request - set variables in template

You can basically do this with the "with" statement: http://docs.djangoproject.com/en/dev/ref/templates/builtins/?from=olddocs#with On Fri, Aug 27, 2010 at 10:06 AM, Yo-Yo Ma wrote: > I'm sure this will be met with criticism, but there is a reason why > just about all

Patch and tests for #13182

http://code.djangoproject.com/ticket/13182 Let me know if there is anything else I can do on this ticket, it is fairly simple anyway. David -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Patch and tests for #12295

Mornin' I've attached a patch with unit tests and updated the existing patch. Let me know if there is anything else I can do on this one. David -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: #12074 Fixed patch and added tests.

, Aug 5, 2010 at 9:17 AM, David P. Novakovic <davidnovako...@gmail.com > wrote: > Hey Alex, > > Thanks for the feedback. I actually had checked this with Russ earlier, but > didn't have a response yet. I prefer TestCases and would be happy to oblige. > > I'll move the cases I

Re: #12074 Fixed patch and added tests.

On Thu, Aug 5, 2010 at 8:55 AM, Alex Gaynor <alex.gay...@gmail.com> wrote: > On Wed, Aug 4, 2010 at 6:52 PM, David P. Novakovic > <davidnovako...@gmail.com> wrote: > > Hey, in the interest of easing myself into helping out I've picked an > easy > > ticket to get done.

#12074 Fixed patch and added tests.

Hey, in the interest of easing myself into helping out I've picked an easy ticket to get done. http://code.djangoproject.com/ticket/12074 I've fixed the patch and added tests. Let me know if I've missed something, or done something wrong :) Cheers, David -- You received this message because

Re: WAP communicating with server-side Python

David, This mailing list is for the development of the django library itself, not development WITH the library. Please direct your question to django-users. David On Wed, Aug 4, 2010 at 2:51 AM, shi shaozhong wrote: > Is there an equivalent mailling list for WAP? > I

Re: Django Unit Test on urls / views

Hi, This is the mailing list for discussion around developing the actual django framework, not the use of the framework. Your request would be better discussed over at django-users http://groups.google.com/group/django-users . Cheers, D On Wed, Jul 14, 2010 at 2:22 PM, Pradnya