3 ms·

First suggestion: show the 2nd level in your Table of Contents. That's helpful for customers like me who would buy the book if they knew a bit more details ab

by hknews 14y ago

First suggestion: show the 2nd level in your Table of Contents. That's helpful for customers like me who would buy the book if they knew a bit more details about what's inside (I don't want to buy something and then find out I know most of the contents already). Another suggestion that would get me to buy the book: does the book addressed particular issues that I know I need to figure out (and will save me from having to do my own research). In particular, would be useful if the marketing of the book told me that it would discuss specific tasks/decisions. Some examples of tasks: -how to code my django app so it works in both python 2.7 and python 3? What's the best way to do that? Django six? How do I setup virtualenv to support my dual configuration? I think this is what the django core team is doing nowadays so I can also adopt the same strategy, right? -what's the best way to replace django templates with jinja2? -for python 3, what is the alternative to PIL? -as mentioned elsewhere, how do I do database migration when the models change. Especially, what are the different alternatives for doing the migration (django south seems too complicated -- can I just make sure the manage.py db schema and the actual db schema are the same as the docs suggest?) -should I use store much of my model data in a json field so I don't have to deal with db migration? Any software packages or coding tips about this? -how do I use SQL Alchemy with django? Issues with doing this (besides not getting a lot of django goodies). -how do I configure django-social-auth ( https://github.com/omab/django-social-auth https://github.com/omab/django-social-auth ) beyond the default setting (ie: the pipeline) -what is a good web host for django. Answer: webfaction. How do I set up virtualenv on webfaction?

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.

by hknews 14y ago

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.