I would just use waitress until things are settled
Ellison Marks <gty...@gmail.com>
Sent by: firstname.lastname@example.org
11/14/2012 04:57 PM
Please respond to
Re: Recommendations for having a static index page
Thanks for the quick reply.
No, I think you had it right the first time, the index page will probably
change almost never. Out of curiosity, would it be a good idea to mock up
some sort of index page and still use waitress for development, or go to
an actual web server now?
On Wednesday, November 14, 2012 1:50:26 PM UTC-8,
On second reading, I am not sure that what I
wrote makes sense. I think you want something
a bit different. Are your trying to automatically
generate the index page? How often do you expect
the index page to change?
[In general, pyramid does not do a great job of
handling purely static data. It works, and it is
fine for debugging, but it is relatively slow and
may require more memory than systems tailored for
pylons-...@googlegroups.com wrote on 11/14/2012 04:20:08 PM:
You received this message because you are subscribed to the Google Groups
To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/HReaqwx9wnYJ
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en