What's the policy about all those references to release notes in the
docs? For example, the autoescape template tag [1] has "New in Django
1.0: Please, see the release notes", with a link to the 1.0 release
notes. When can these be removed?
It's clearly a bad idea to rely on the release notes as
Hey Maxime
i think its a real awesome project. sometimes u need to work with designers
who know nothing about django(and they dont need to)
i will totally join you.
On Tue, Feb 16, 2010 at 9:02 AM, Alex Gaynor wrote:
> On Mon, Feb 15, 2010 at 11:55 PM, h3 wrote:
> > Hello,
> >
> > I would like
On Tue, Feb 16, 2010 at 1:43 PM, orokusaki wrote:
> Thank you Karen. I've been hushed so many times about this, yet there
> seems to be a growing concern (hence the search traffic, and number of
> results) about why you can't naturally do this with Django's built-in
> serializer.
I have no proble
On Mon, Feb 15, 2010 at 11:55 PM, h3 wrote:
> Hello,
>
> I would like to introduce a project I've just released in the wild.
> For the moment it is still just a working prototype, but hopefully it
> will grow and stabilize with time.
>
> On Google Code:
> http://code.google.com/p/django-ray/
>
> I
Hello,
I would like to introduce a project I've just released in the wild.
For the moment it is still just a working prototype, but hopefully it
will grow and stabilize with time.
On Google Code:
http://code.google.com/p/django-ray/
Introduction blog post:
http://haineault.com/blog/125/
Comment
-1 I think examples, broken or working, are very helpful for absolute
beginners. Maybe there should be strict warnings about the quality of
the code (in a similar fashion to the ones that warn you when you view
old docs).
--
You received this message because you are subscribed to the Google Group
Thank you Karen. I've been hushed so many times about this, yet there
seems to be a growing concern (hence the search traffic, and number of
results) about why you can't naturally do this with Django's built-in
serializer.
--
You received this message because you are subscribed to the Google Grou
On Mon, Feb 15, 2010 at 9:08 PM, Gary Reynolds
wrote:
> There is already a ticket for this (and possibly others).
>
> http://code.djangoproject.com/ticket/11244#comment:4
>
> It has been closed and marked wontfix, see the comments for why.
I believe the request here is to reconsider that wontfix
There is already a ticket for this (and possibly others).
http://code.djangoproject.com/ticket/11244#comment:4
It has been closed and marked wontfix, see the comments for why.
On 15 Feb 2010, at 21:53, orokusaki wrote:
Please visit the following URL, and when you do, put your focus into
the
Please visit the following URL, and when you do, put your focus into
the search form after "seri" and type the letter "a". You'll notice
the top search for anything related to Django serialization is "Single
Object". This is because people want to have this feature. Serializing
a single object can
Hi,
I thought I'd check with you before creating a ticket.
Django's aggregate documentation http://docs.djangoproject.com/en/dev/ref/models/querysets/#id8
states that return type for aggregates Max, Min and Sum is the same
as the input field.
However, currently values for all fields with i
Hi,
On Mon, Feb 15, 2010 at 03:27:27PM -0600, Jeremy Dunck wrote:
> On Mon, Feb 15, 2010 at 3:16 PM, Forest Bond
> wrote:
> ...
> > * Forbid premature draining of the content iterator via response.content by
> > only
> > evaluating the content iterator if accessed via iter(response) and raisin
On Mon, Feb 15, 2010 at 3:16 PM, Forest Bond wrote:
...
> * Forbid premature draining of the content iterator via response.content by
> only
> evaluating the content iterator if accessed via iter(response) and raising an
> exception if it is accessed via response.content.
...
> * Is this type o
Hi,
Django allows an iterator to be passed as response content when instantiating an
HttpResponse. However, doing so causes problems with the following classes and
functions:
UpdateCacheMiddleware:
Caches the response object using the configured cache backend, but most
iterators cannot be pi
On Mon, Feb 15, 2010 at 5:14 AM, Luke Plant wrote:
> I'm prompted by #12863 [1] to suggest that we remove the whole
> 'examples' directory, because:
+1.
Jacob
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send em
> I'm prompted by #12863 [1] to suggest that we remove the whole
> 'examples' directory, because:
>
> * The style of code contained in it is very atypical (it does not use
> templates), which makes it very poor 'example' code.
> * As documentation it is extremely limited, and we have great
> do
On Mon, Feb 15, 2010 at 7:14 PM, Luke Plant wrote:
> Hi,
>
> I'm prompted by #12863 [1] to suggest that we remove the whole
> 'examples' directory, because:
>
> * The style of code contained in it is very atypical (it does not use
> templates), which makes it very poor 'example' code.
> * As docum
Hi,
I'm prompted by #12863 [1] to suggest that we remove the whole
'examples' directory, because:
* The style of code contained in it is very atypical (it does not use
templates), which makes it very poor 'example' code.
* As documentation it is extremely limited, and we have great
documentati
On Monday 15 February 2010 09:20:28 Ivan Sagalaev wrote:
> Hello everyone!
>
> A couple of days ago we've noticed a (potentially big) backwards
> incompatibility that can bite users upgrading from 1.1 to 1.2.
>
> CSRF doc encourages users to enable CsrfViewMiddleware that will
> check all POST r
Hello everyone!
A couple of days ago we've noticed a (potentially big) backwards
incompatibility that can bite users upgrading from 1.1 to 1.2.
CSRF doc encourages users to enable CsrfViewMiddleware that will check
all POST requests for csrf_token and then suggests to alter all HTML
forms to
20 matches
Mail list logo
