4 ms·
Finally Zappa(https://github.com/Miserlou/Zappa https://github.com/Miserlou/Zappa) would be able to support web services written in python 3!
by abhirag 10y ago
Finally Zappa(https://github.com/Miserlou/Zappa https://github.com/Miserlou/Zappa) would be able to support web services written in python 3!
- Mizza 10y agoYep! Follow the progress here: https://github.com/Miserlou/Zappa/issues/793 https://github.com/Miserlou/Zappa/issues/793
- ak217 10y agoI much prefer Chalice (https://github.com/awslabs/chalice https://github.com/awslabs/chalice) which just got a synchronized release supporting Python 3 as well.
- scrollaway 10y agoHave you tried both? Can you explain what you prefer in Chalice over Zappa?
- ak217 10y agoYes. In my impression Chalice is designed to be a microframework (emphasis on micro) with the bare minimum of glue necessary to make deploying Lambda apps easy. Zappa is designed around an ill-fitting API (while WSGI is widespread, it's clunky and a layering violation of sorts when put in the Lambda runtime environment) and has a development philosophy that I don't agree with.
- Mizza 10y agoI wrote up a comparison of the two here: https://blog.zappa.io/posts/comparison-zappa-verus-chalice https://blog.zappa.io/posts/comparison-zappa-verus-chalice Zappa has even more features now. Basically, you can't even build real server-less apps with Chalice, plus Zappa has support for tons of other magic features.
- wahnfrieden 10y agoI stopped using Chalice in favor of Zappa because Zappa made it trivial to run a local dev environment (it's just Flask/Django/WSGI). Have I missed something about this with Chalice?
- ak217 10y agoChalice does provide a local mode, yes. It worked well for me.