GSoC 2007 Status Update VIII: Django REST interface

and, of course, to the community of Django developers in general. I hope you like and use the Django REST interface. Cheers, Andreas Stuhlmüller [1] http://code.google.com/p/django-rest-interface/ [2] http://www.aiplayground.org/artikel/improving-django/ [3] http://django-rest-interface.googlecode.com/svn

Re: GSoC 2007 Status Update VII: Django REST interface

On 8/17/07, David Larlet <[EMAIL PROTECTED]> wrote: > Just one (latest?) thought, it's a bit hard to debug because > 400 errors are not really verbose, is it possible to find a > way to make debug easier? For the moment, I have: if > settings.DEBUG: print i.errors but I'm sure it can be better.

GSoC 2007 Status Update VII: Django REST interface

utorial [2] that describes how to provide an API for an existing Django application using the REST interface. If you have any questions, ideas, can't get the interface to work or want to contribute bugfixes and other enhancements, please go ahead. Regards, Andreas Stuhlmüller [1] http://code.google.co

Re: GSoC 2007 Status Update VI: Django REST interface

end up with is "work on your own, supported by your mentor" (which, admittedly, works quite well). Regards, Andreas Stuhlmüller --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django develo

Re: GSoC 2007 Status Update VI: Django REST interface

ait at least until Fri, August 24th before using the REST interface in any kind of production environment. By then I hope to have done more thorough testing. If you stumble upon a bug, please let me know. Thanks for your feedback. Regards, Andreas Stuhlmüller [1] http://django-rest-inte

GSoC 2007 Status Update VI: Django REST interface

er on best practices for REST-oriented architectures with short notes on where the REST interface still needs improvement. If you feel that there are important issues I am missing, please write me or just open a ticket [4]. Regards, Andreas Stuhlmüller [1] http://code.google.com/p/django-rest-int

Re: GSoC 2007 Status Update IV: Django REST interface

On 7/13/07, David Larlet <[EMAIL PROTECTED]> wrote: > * About users, how can I handle django users' permissions? John > Sutherland had already done some work on django-crudapi [1] and it > could be interesting to allow this access control. Good question. I would subclass one of the

Re: GSoC 2007 Status Update V: Django REST interface

On 7/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Would it be possible to, instead of passing in collection_url_pattern > to the Collection, pass in the name of a named url pattern, which > internally would get reverse()'d? Yes. After talking to Malcolm about how URL customization could

Re: GSoC 2007 Status Update V: Django REST interface

On 7/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I would love to try it out with one of my apps, but maybe a really > quick HOWTO on how it's supposed to be set up with a project? Thanks for the suggestion! I just added a short tutorial to the project page [1]. The five steps contain

GSoC 2007 Status Update V: Django REST interface

or the other and that we can take care of? Expect the next update around July 20th. Regards, Andreas Stuhlmüller [1] http://code.google.com/p/django-rest-interface/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

GSoC 2007 Status Update IV: Django REST interface

This is the fourth weekly status update for my Summer of Code project, a generic REST interface for Django [1]. Issues I worked on this week: 1. Authentication. I added authentication hooks to the Collection class, an implementation of HTTP Basic and Digest authentication (stateless, header is

GSoC 2007 Status Update III: Django REST interface

This is the third weekly status update for my Summer of Code project, a generic REST interface for Django [1]. I spent the SoC-part of this week mostly thinking about automated URL pattern generation, wrote some code and added a few tests that demonstrate how to use this feature. Currently, you

GSoC 2007 Status Update II: Django REST interface

This is the second weekly status update for my Summer of Code project, a generic REST interface for Django [1]. This week, I was mostly working on improving the architecture of the code, in particular by splitting ModelResource into two classes, Collection (for querysets) and Entry (for

Re: GSoC 2007 Status Update: Django REST interface

ls on the other hand. I will take a closer look at the tickets you opened when I get to the second half of my proposal, but note that what I am working on is not XMLRPC or SOAP. Regards, Andreas On 6/2/07, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > On 6/1/07, Andreas Stuhlmüller &

GSoC 2007 Status Update: Django REST interface

This is the first weekly status update for my Summer of Code project, a generic REST interface for Django. If you haven't seen it, take a look at http://code.google.com/p/django-rest-interface/. This week, I have started checking in code. I am always happy about feedback. Add a few lines to your

Re: magic-removal: where_constraints

On 2/14/06, Ian Holsman <[EMAIL PROTECTED]> wrote: > my first stumbling block I have found is that I was using > 'where_constraints' to automatically set the SITE_ID. > > how does one do this in magic_removal? I replaced the where_constraints by overwriting the default query sets. See

Re: Magic - removal branch .. is the API stable yet?

On 1/23/06, Jason Davies <[EMAIL PROTECTED]> wrote: > I'm keen to get the "semantics of subtyping" stuff done. If you have > any implementation hints to help me along that would be really helpful, > thanks. Same here. I'd love to see a working subtyping implementation for magic removal, the