Re: FYI: added a proper "easy" field to Trac

On Jun 16, 10:32 am, Julien Phalip wrote: > On Jun 16, 3:08 am, Alex Kamedov wrote: > > > Django documentation page Contributing to Django [1] has the same problem > > too > > [1]https://docs.djangoproject.com/en/1.3/internals/contributing/ > > I've fixed

Re: FYI: added a proper "easy" field to Trac

On Jun 16, 3:08 am, Alex Kamedov wrote: > Django documentation page Contributing to Django [1] has the same problem > too > [1]https://docs.djangoproject.com/en/1.3/internals/contributing/ I've fixed the link in the wiki page. The doc is already fixed in trunk. Thanks,

Re: FYI: added a proper "easy" field to Trac

Hi Alex, If you open a ticket to report these problems, we'll make sure they get fixed. Yours Russ Magee %-) On Thu, Jun 16, 2011 at 1:08 AM, Alex Kamedov wrote: > Django documentation page Contributing to Django [1] has the same problem > too > [1] 

[GSoC form-rendering] Weekly Check-in

Hi, I unfortunatelly missed the last weekly check-in. However during this time I was already on my travel to Amsterdam for DjangoCon Europe. During this Conference and mostly during the sprints have I spoken to some of the core contributors to get their opinion about my current form rendering

Re: FYI: added a proper "easy" field to Trac

Django documentation page Contributing to Django [1] has the same problem too [1] https://docs.djangoproject.com/en/1.3/internals/contributing/ On Wed, Jun 15, 2011 at 10:47 PM, Alex Kamedov wrote: > Wiki StartPage [1] has link on Custom Query page with keyword tag >

Re: FYI: added a proper "easy" field to Trac

Wiki StartPage [1] has link on Custom Query page with keyword tag "easy-pickings" with title ""Easy Pickings" Tickets" [1] https://code.djangoproject.com/wiki#Gettinginvolved On Thu, Apr 21, 2011 at 3:39 AM, Jacob Kaplan-Moss wrote: > Hi folks -- > > Just as a quick FYI, I

Re: ImportError catching in urlresolvers.py

On 15 jun, 07:36, Russell Keith-Magee wrote: > In this case, the underlying problem is that ImportError is actually > catching 2 different errors: >  1) The view specified doesn't exist >  2) The module containing the view contains an error. Agreed, in this case this

Django on Microsoft IIS

Hello! We have recently developed a solution to install and run Django applications on Microsoft IIS. Here is the link: http://www.helicontech.com/zoo/ Currently IIS 7, 7.5 and IIS Express are supported. We expect to demonstrate production level performance in this environment on release. To

Re: Customizable serialization. (Finally?)

> A suggestion though, is to be able to declare serializers in a > similar fashion as models or forms. Actually that's a fair point, yup - the proposal could be made a little closer to the existing Forms and Models APIs. Something along these lines... class ModelPKField(SerializerField):