Re: Django IIS

On Wed, Sep 23, 2009 at 9:18 PM, Ronn Ross wrote: > Can Django run on IIS? > > > > The django-developers mailng list is for the discussion of the developmeny of django itself, not developmeny with Django. Please ask the django-users maing list. Alex -- "I disapprove of

Django IIS

Can Django run on IIS? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to

Re: Auth/Session modules and JSON views

On Wed, Sep 23, 2009 at 8:58 PM, django_fo...@codechimp.net wrote: > > This is probably a dumb question, but I am working on some JSON views > that I need to apply authentication too.  I thought maybe I could use > the Django built-in auth/session apps to wrapper the JSON

Auth/Session modules and JSON views

This is probably a dumb question, but I am working on some JSON views that I need to apply authentication too. I thought maybe I could use the Django built-in auth/session apps to wrapper the JSON View methods, but when I do testing I am not seeing the session id being sent back. I tried

Re: decorator_from_middleware change

On Monday 21 September 2009 20:27:50 Jacob Kaplan-Moss wrote: > No, I think this is precisely correct. I've been meaning to do > exactly what you're proposing for a while myself; just haven't > gotten around to it. > > > decorator_from_middleware isn't actually documented anywhere > > I

Re: decorator_from_middleware change

On Wednesday 23 September 2009 23:40:25 James Bennett wrote: > So, I've worked out what the problem is. > > Previously either of these worked: > > cache_page(timeout, view) > cache_page(view, timeout) > > Now, cache_page assumes that the first positional argument will be > the timeout. So

Re: Let's Talk About ``to_field``

I believe someone had linked a ticket before, but I was unable to find one, so I went ahead and submitted it here: http://code.djangoproject.com/ticket/11938 David Cramer On Wed, Sep 23, 2009 at 6:41 PM, David Cramer wrote: > As usual, my apologies for lacking context

Re: Let's Talk About ``to_field``

As usual, my apologies for lacking context :) The problem happens when you try to query with a model containing a foreign key that references a to_field. It fails to pass the proper attribute. # Exampe 1, a simple get lookup class ExampleBrokenModel(models.Model): user =

Re: Let's Talk About ``to_field``

On Wed, Sep 23, 2009 at 4:59 PM, David Cramer wrote: > > I haven't brought this up for quite a while, but ``to_field`` still > does not function properly (at least as of 1.1, I haven't noticed any > changes addressing it though). The issue is that anywhere you do a GET >

Re: Session/cookie based messages (#4604)

I'm a bit late in here, and it seems we reinvented a wheel as well (even tho we did this about a year ago), but recently just OS'd our simply notices system [1]. I'm also +1 for including something like this in trunk rather than using the current user messages. I had a brief look at django_notify

Re: NDjango - .Net port of Django template langauage

Michael Feingold wrote: > > Thank you for the pointers. You have some pretty interesting test > cases in your project. Thanks. Actually most of the credit goes to the django developers, because most of my tests are just ported versions of the django tests. > We also have quiet a few test

Re: decorator_from_middleware change

On Tue, Sep 22, 2009 at 4:07 PM, Luke Plant wrote: > Bummer, I tried hard not to break it - I added backwards > compatibility tests for the basic different uses.  Could you produce > a test case? So, I've worked out what the problem is. Previously either of these worked:

Re: NDjango - .Net port of Django template langauage

Thank you for the pointers. You have some pretty interesting test cases in your project. We also have quiet a few test cases in our unit tests have a peek if you are interested. As to the ticket - this is an interesting one. The scenario it refers to seems pretty clear to me I agree with Karen's

Let's Talk About ``to_field``

I haven't brought this up for quite a while, but ``to_field`` still does not function properly (at least as of 1.1, I haven't noticed any changes addressing it though). The issue is that anywhere you do a GET lookup, it doesn't process the to_field properly:: # TODO: waiting on to_field

Re: Change list default sort modification proposal

Take a look in test\regressiontests\admin_views\tests.py AdminViewBasicTest.testChangeListSortingXXX() methods. They should give you a good place to start. On Wed, Sep 23, 2009 at 6:18 PM, Ben Davis wrote: > I would write the tests though I'm not 100% sure how to write

Re: NDjango - .Net port of Django template langauage

Michael Feingold wrote: > On Sep 23, 2:54 am, Pablo Escobar > wrote: >> 1. Django is Open Source. It is not a problem to find the parsing >> algorithm >> > Of course it is And we did go through the code. But reverse > engineering can show you what happens, not what the

Re: Change list default sort modification proposal

I would write the tests though I'm not 100% sure how to write regression tests for a UI change... any suggestions on how to go about doing that? On Thu, Sep 17, 2009 at 2:04 PM, Joshua Russo wrote: > I don't have any say in what gets accepted or not but I do believe

Re: ManyRelatedManager signals

On Tue, 22 Sep 2009 19:10:19 -0700 (PDT), Stephen Sundell wrote: > Is there a reason not to have a signal before and after creating an > entry into a ManyToMany table. I have a piece of code i need to call > when this relationship is created. I don't know of any

Re: CSRF proposal and patch ready for review

On Tuesday 22 September 2009 21:24:48 Luke Plant wrote: > 2) Get the view to be exempted from the normal CSRF checks done > by the middleware. Thankfully, we already have not one but two > ways of doing this - the manual @csrf_exempt decorator on views, > and the internal mechanism that

Re: NDjango - .Net port of Django template langauage

On Sep 23, 2:54 am, Pablo Escobar wrote: > 1. Django is Open Source. It is not a problem to find the parsing > algorithm > Of course it is And we did go through the code. But reverse engineering can show you what happens, not what the intention was

Re: CSRF proposal and patch ready for review

On Sep 22, 9:24 pm, Luke Plant wrote: > > 2. I'm not at all keen on the implementation as a middleware > > (especially a view middleware, which doesn't play well with generic > > views and redispatching to other view functions, both patterns I like > > a lot). > > Could

Re: NDjango - .Net port of Django template langauage

1. Django is Open Source. It is not a problem to find the parsing algorithm PS Anyway. I don't see any advantages of django's templates comparing with ASP.NET MVC Views --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google