Switch to using Python about httparchive.org HOT 1 CLOSED

Thanks Charlie.

I see three main components to this: back end, data viz, and front end.

• Setting up on App Engine takes care of some of the things you mentioned. We'll be using Python and GAE comes with a few data storage options like Cloud SQL and Datastore. The starter docs included a Flask demo, so that's what I've checked in so far, but Pyramid is supported too. Open to changing if it means we can reuse a lot of what you've already written, or at least have a resident expert for writing new stuff with it.
• For the visualizations, Highcharts has more of the features we're looking for. But we definitely want to start folding mobile/desktop together. For example: http://jsfiddle.net/rviscomi/1r6dpctd/
• We're working with an agency to design and develop a new front end. This will be entirely from scratch, but still carry forward some of the familiar visual elements like colors and the logo. It will be delivered as static HTML/CSS so we'll have to make it fit into whatever templating system we want to use - I've started using Jinja. JS frameworks like React are also on the table.

So we won't be able to salvage a whole lot, but it definitely won't go to waste. The routing logic especially.

from httparchive.org.