[google-appengine] Re: Rendring data on django from ulrfetch

2009-01-20 Thread djidjadji 

If I fetch the given page I get a HTML file of size ~51000 bytes.
If I just save the text of the document I need ~11000 bytes.
If you find this on the development server you can edit the django
file and insert some debug.
What are the 'bits' that need to be joined? There individual length?
How many 'bits' can you join (use slices - bits[:n])?
These debug texts could be the result of the function instead of the join.
What is the difference for the fetchurl and the dataStore version?

2009/1/20 anand :
> Also I would like to tell that if I store the content of my doc to
> dataStore then my django can easy render that. I face problem only
> when it is from fetchurl.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---

[google-appengine] Re: Rendring data on django from ulrfetch

2009-01-20 Thread anand 

Hi!

Thanks for reply. Yes I tried with smaller content and it works.
However I would also need a bigger content.

I would be happy to remove the double  tag if that will solve my
issue.

Also I would like to tell that if I store the content of my doc to
dataStore then my django can easy render that. I face problem only
when it is from fetchurl.

Thanks again.

Regards
Anand


On Jan 20, 1:52 am, djidjadji  wrote:
> Have you tried it with a smaller/shorter 'full_page_content'?
> template_values = {'full_page_content': 'My Test String', }
> The doc in the example is pretty big. Or after your conversion it is big.
> Python complains that the data is too large for a string.
>
> > page_content = '%s'
> > My test_page_date.html contains :
> > {{ full_page_content }}
>
> Why do you need a pre-tag inside a pre-tag?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---

[google-appengine] Re: Rendring data on django from ulrfetch

2009-01-20 Thread djidjadji 

Have you tried it with a smaller/shorter 'full_page_content'?
template_values = {'full_page_content': 'My Test String', }
The doc in the example is pretty big. Or after your conversion it is big.
Python complains that the data is too large for a string.

> page_content = '%s'
> My test_page_date.html contains :
> {{ full_page_content }}

Why do you need a pre-tag inside a pre-tag?

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---