On Tue, Sep 10, 2013 at 9:05 AM, Curtis Maloney
wrote:
>
> On 9 September 2013 19:50, S Berder wrote:
>>
>> Gents,
>> to sum it up, arguments made and details of how I see the
>> implementation of a response/request encode/decode framework:
>>
>> * need a pluggable interface so current content-ty
On 9 September 2013 19:50, S Berder wrote:
> Gents,
> to sum it up, arguments made and details of how I see the
> implementation of a response/request encode/decode framework:
>
> * need a pluggable interface so current content-types are supported
> (`application/x-www-form-urlencoded`, `multipar
On Mon, Sep 9, 2013 at 5:30 AM, Jorge Cardoso Leitao <
jorgecarlei...@gmail.com> wrote:
> Hi Django dev mailing list.
>
> The objective of this email is two-fold:
> A: I want to share a book I've read about written communication. Since
> communication in Django, and open source in general, is main
Hi guys
A related question: What about repeated entries of apps in INSTALLED_APPS?
I remember seeing this once and, if I recall correctly, no errors were
raised. I guess ImproperlyConfigured would be a suitable exception.
Germán
On Tuesday, August 13, 2013 5:09:45 AM UTC-5, Stefano Crosta wrot
On Monday, September 9, 2013 3:30:41 AM UTC-7, Jorge C. Leitão wrote:
>
>
> Specifically, my suggestion is to add a new section, probably in
> https://docs.djangoproject.com/en/dev/internals/contributing/new-contributors/,
>
> on how to communicate in this project (which should be similar to o
BTW, the URLs
http://blog-amirouche.dotcloud.com/notes/2013/admin-next-a-new-api.html
http://amirouche.github.io/blog/django-admin-next-a-new-api.html
lead to 404s.
The correct one is
http://www.hypermove.net/notes/2013/admin-next-a-new-api.html
On Saturday, March 30, 2013 5:49:27 PM UTC-5, Amiro
very great task!
2013/9/8 German Larrain :
> I know there are different opinions on this topic but if anyone is
> interested, I created a repo for the tutorial. The idea is to have branches
> and tags that match those of the documentation.
>
> https://github.com/glarrain/django-tutorial-source-cod
There are caching/laziness-related functions and classes in
django.utils.functional, but none seem to be documented (apart from
cached_property which has documentation forthcoming).
django.utils.functional.memoize
Caches the output of a function in a dictionary. Could this be implemented as a
Hi Django dev mailing list.
The objective of this email is two-fold:
A: I want to share a book I've read about written communication. Since
communication in Django, and open source in general, is mainly written, some of
you may found interesting to take a look.
B: I want to suggest adapting some
Gents,
to sum it up, arguments made and details of how I see the
implementation of a response/request encode/decode framework:
* need a pluggable interface so current content-types are supported
(`application/x-www-form-urlencoded`, `multipart/form-data`), new
types (`application/json`), custom an
10 matches
Mail list logo