I just posted a new gluon.rewrite.py in trunk that should report more
details about your error.

Massimo


On May 11, 7:53 am, Chris S <sanders.ch...@gmail.com> wrote:
> The routes.py file that I am attempting to use is:
> -----------
> routes_in = (('/favicon.ico', '/init/static/favicon.ico'),
>              ('/robots.txt', '/init/static/robots.txt'),
> )
> routes_out = ()
> -----------
> I believe that is a direct copy and paste of the example from the
> online book.
>
> On May 10, 6:04 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > As far as I know it works well on GAE. The errors you get:
>
> > "Your routes.py has a syntax error. Please fix it before you restart"
>
> > indicates that there is an error in your routes.py.
> > If you post it we can help you isolate the problem.
>
> > Massimo
>
> > On May 10, 4:23 pm, Chris S <sanders.ch...@gmail.com> wrote:
>
> > > Does routes.py work on GAE?  I've recently deployed an app which used
> > > the 5-line routes.py from the book for routing robots.txt and
> > > favicon.icon.  I just wanted to get rid of that 100% error rate on
> > > those two files.  I recevied the following message.  Only after
> > > removing routes.py again did the app launch properly.
>
> > > ------------begin error message----------------
> > > #
> > > 05-10 01:18PM 34.771
> > > unable to import Rocket
>
> > > #
> > > E 05-10 01:18PM 34.774
> > > Your routes.py has a syntax error. Please fix it before you restart
> > > web2py
>
> > > #
> > > E 05-10 01:18PM 34.778
> > > <type 'exceptions.SyntaxError'>: invalid syntax (<string>, line 3)
> > > Traceback (most recent call last):
> > >   File "/base/data/home/apps/rms-solutions/beta.341858638445092536/
> > > gaehandler.py", line 44, in <module>
> > >     import gluon.main
> > >   File "/base/data/home/apps/rms-solutions/beta.341858638445092536/
> > > gluon/main.py", line 66, in <module>
> > >     rewrite.load()
> > >   File "/base/data/home/apps/rms-solutions/beta.341858638445092536/
> > > gluon/rewrite.py", line 63, in load
> > >     raise e

Reply via email to