Re: Streaming sitemaps

But then it still makes it better on the Python side. You still have psycopg memory problems but don't you have that now all the time anyways? On Friday, July 26, 2013 11:50:57 AM UTC+2, Aymeric Augustin wrote: > > On 26 juil. 2013, at 09:40, julianb <julia...@gmail.com > >

Re: Streaming sitemaps

I don't think the queryset needs to be loaded into memory. There is an iterator() method available: https://docs.djangoproject.com/en/dev/ref/models/querysets/#iterator On Thursday, July 25, 2013 11:56:09 AM UTC+2, Aymeric Augustin wrote: > > Hi Julian, > > Thanks for the suggestion. This is

Streaming sitemaps

Since 1.5 we have streaming responses. What is the state of contrib.sitemaps in this regard? I have some very large sitemaps and experimented with making them faster a few years ago. If the do not yet stream, I think this would be a good idea to get memory usage down. Is there anything to keep

Re: URL dispatcher fallthrough?

s is easier > said than done. So it would be nice to have an idiomatic solution. > > An alternative might be a kwarg on the url function, such as > 'fallthrough_on_404'. But it all feels a bit hackish to me :/ > > Regards, > Andy > > > On 18 March 2013 15:23, julianb &l

URL dispatcher fallthrough?

Hi, imagine the following use case: You build an online store where you have sorted products into several categories and maybe associated an occasion. Now you want to build URLs. So the URL schema that all of the store's owners agree on is: // // // Look simple. Because product slugs should

Re: #717 (If-Modified-Since checked for exact match) should be fixed

Uuh, so what's with this? Nothing happened with the ticket and no further comments here either... :( On Aug 9, 12:28 pm, julianb <julian@gmail.com> wrote: > #717 was posted 5 years ago and closed as wontfix, supposedly cause > Django was in it's early stages and it was not an imp

Re: #717 (If-Modified-Since checked for exact match) should be fixed

I just discovered that the condition decorator does check for exact match only, too. Thus, the ticket should be changed to also include this issue. Is someone going to reopen the ticket? On Aug 9, 11:46 pm, Łukasz Rekucki wrote: > On 9 August 2010 22:48, Paul McMillan

Re: #717 (If-Modified-Since checked for exact match) should be fixed

On Aug 9, 11:46 pm, Łukasz Rekucki wrote: > On 9 August 2010 22:48, Paul McMillan wrote:> I agree with > the person who closed the ticket again, since this should > > have been discussed on the mailing list prior to re-opening it. > > That would be me ;)

#717 (If-Modified-Since checked for exact match) should be fixed

#717 was posted 5 years ago and closed as wontfix, supposedly cause Django was in it's early stages and it was not an important issue. I propose that it's getting reopened and fixed now. Like the ticket description says, in ConditionalGetMiddleWare the Last- Modified date is checked for exact

Re: Decision for ticket #6362 - Remove blank spaces with strip when validating the data

On May 13, 2:56 am, Russell Keith-Magee wrote: > We need to wait until we're not trying to get v1.1 out the door. Since the ticket is one year old, that time had come and passed. --~--~-~--~~~---~--~~ You received this message because you

URL mapping and percent-encoded reserved characters

Hi, currently it seems that the URL dispatcher makes no difference between e.g. "/" and "%2F", which is the same if you decode it but has special meaning in URLs. The "/" separates path segments and you would have to encode it to "%2F" if used in such a segment. (http://en.wikipedia.org/

Re: Search facility for new documentation

On Aug 31, 12:07 am, "Ramiro Morales" <[EMAIL PROTECTED]> wrote: > From what i?ve heard I'd say facilities offered by Sphinx > (seehttp://sphinx.pocoo.org/markup/para.html#dir-versionadded) > are going to be used for this. That would be good then. Currently it is written directly as text, which

Re: Search facility for new documentation

On Aug 30, 9:31 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > The latest docs will always be at //dev/; versions frozen with > each release will be at ///. On this occasion, why not change "New in Django development version" remarks to "New in this version"? That makes much more sense,

Re: Call for testing: new docs

I have just a tiny suggestions... could you make the headlines a bit bigger or with more space around them? When scrolling, there is no real distinction between different parts. I always found that a bit unusable in the Django docs. You just have a large stream of text and your eyes are unable to