Thanks for the info.  I have been living with a different issue.
Everything works just fine normally, but periodically, when generating
a PDF on the local dev environment, I get the same PDFMetrics error.
A restart of the dev environment get me back on track.  Normally, this
occurs when debugging a new report script.  Sometimes, there are 1, 2,
3 errors in my script.  When finally all script errors are resolved,
then the first time the pdf *should* generate successfully, the
PDFMetrics error pops up.  After the restart, I'm back on track.

Just adding my 2 cents to your 2 cents.

johnP

On Apr 17, 5:47 am, KenCorey <kenco...@googlemail.com> wrote:
> Oh bother.
>
> Just thought I'd post about my stupidity to hopefully make things
> smoother for someone else.
>
> For the record, I'm running XP Pro SP3, Python 2.5, GAE SDK 1.1.9,
> ReportLab's PDF library 2.3.
>
> In my investigations, I'd downloaded reportlab's .msi installer, which
> installed the pdf library in my python/lib/site-packages/reportlab
> directory.
>
> Then, I realised I couldn't do that on Google's servers, and read I
> could just install the files below the project directory.
>
> After that, I couldn't create even the simplest .pdf because it
> crashed saying the infamous error: "ImportError: No module named
> pdfmetrics".  Nothing that I did seemed to change it.
>
> Of course, once I removed the my python/lib/site-packages/reportlab
> directory, and let python get all the files from the project directory
> it all worked swimmingly, just as it did on the live web site.
>
> Go figure.  Hope this helps someone.
>
> -Ken
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to