4 ms·
Thanks for the comments! I'm one of the authors! 1. For Python 2/3 compatibility, we recommend SIX. 2. We recommend using Jinja2 where you need it, not as a re
by pydanny 14y ago
Thanks for the comments! I'm one of the authors!
1. For Python 2/3 compatibility, we recommend SIX.
2. We recommend using Jinja2 where you need it, not as a replacement.
3. PIL on Python 3 is not yet solved. This is part of the reason why the Python web world has not transitioned over completely. It's a huge blocker.
4. We plan to cover South in depth. In the BETA or FINAL editions of the 1.5 book.
5. You implement SQLAlchemy in DJango via "import sqlalchemy". You do lose lots of goodies (ModelForms, Admin, a bunch of views, etc)
6. django-social-auth is something we hope to cover before FINAL
7. On web hosts (webfaction, Heroku, et al), we didn't want to turn the book into a tome about deployment. Each provider does things differently, and we would have to keep track of all that and update when host providers change their services. So rather than describe deployments in depth, we're going to link to their documentation and let them handle it.