Mastering Django: Core: The Complete Guide to Django 1.8 LTS

I think it's quite good, covers lot of topics, but i had wanted more details and examples in some topics like forms.

Great guide to Django. The first 7 chapters are an excellent, in-depth, explanation of how Django works. This information is critical knowledge before you can go off and start building applications.

This book gets u started real quick to django development.

Does a very good job of explaining MVC architecture for web development, also covers interfacing external resources using Python. This will serve as a good reference for development. Would like a little clearer description of differences with previous versions (migration path), so applications written using new features aren't "dead on arrival" when releasing to older installations.

Good update to newer versions of Django. Provides good tutorial information but can also be used as a reference.

I found this book to be confusing and not very helpful. I feel it could've been written better and you'll be better off reading the how-to guide for free on the Dango site. I end up returning the item for a refund.

This book is worthless. It appears to have been authored by a techwriter based off the original book with zero knowledge of the history or problems solved and unread by anyone on the development staff. Modern Django apps require knowledge of Django data modeling, forms, serializers, generic views, routers, admin pages, authentication and authorization. Each of these components was developed external to Django and sloppily integrated later so one must become familiar with all such Python modules that must be imported and sadly, it isn't immediately obvious which have obsoleted which. Further, Django originally supported small apps so data models were managed by instance methods. This strategy failed to scale when developing API with more than 10 models so standardization was imposed then buried in the framework so knowledge of modern preferred URL syntax and use of generic classes instead of instance methods is now expected except for special cases in order to reducing training and allow code to be easily ported. Unfortunately, one cannot just wing it from a few examples obtained online. One must learn what is expected and how it is managed via hidden imported code. Given that legacy code will still reference instance methods and customizations will require them, users new to Django should become familiar with the history of each component via examples and explanation. Sadly, the author is ignorant of practically all of these needs and Django in general so merely rehashes bits and pieces of perhaps half incoherently.Each of these components also requires automated tests developed by the Software Engineer not a QA Engineer. A test fixture framework also exists developed with the limited imagination of a Software Engineer so only a subset of common negative test cases are possible via the fixture framework. Nonetheless, data fixtures are expected so, users with varying permissions and objects models with varying attributes need to be created once then saved as fixtures which are auto-loaded by tests into a hidden test database. None of this is possible without in-depth knowledge of authentication and authorization which exists as instance methods, generic classes and inherited generic classes. Automated tests expect HTML validation so Selenium and BeautifulSoup knowledge is expected. Also, modern test automation expects code coverage analysis but the Python coverage tool will not adjust to several newer versions of Django so Google Search python coverage django broken to avoid banging your head against the wall. Again, the author neglected to mention any of this.In addition, web app development has evolved to solve several common problems that were oddly left out: reading large data sets with pagination, the need for CSRF when creating, modifying or deleting records, use of a deleted attribute to avoid re-indexing if RDBMS, versioning the API to avoid downtime when deploying, support for HTTP PATCH, and data model modification on large legacy data sets. Some discussion of Python Celery, RabbitMQ, AWS SNS/SQS and current strategies for integration with common NoSQL solutions would have been nice even if just bundled in a single chapter about beyond vanilla Django. Reading left one wondering why so much was deliberately left out while touting the latest greatest. It would be easy to imagine frustration in users new to Django. Don't waste your money. Google Search django, component, example to find helpful examples and read the classes imported to detect buried magic. But also Google Search django, component, problem to find explanations for common mistakes caused by very poor example free documentation such as this book.

I just received this book and so far like it's writing style, but please note that this book targets Python 3.x and the author has chosen to ignore Python 2.x (which are not compatible languages). While I understand the author's choice to use and promote 3.x, sometimes the work environment rather than the developer makes that choice for you. I wish the author had included 2.x compatible code snippets as well.

Ho iniziato a leggere questo libro e devo dire che ha un modo di spiegare le cose che ti apre la mente sul perchè la logica di django si afatta così. Veramente utile. In realtà se uno non vuole il libro quello che si trova su djangobook è identico.A me piaceva però avere il cartaceo.

Bom livro, bastante abrangente sobre o assunto Django. Ideal para quem já fez o tutorial do site e deseja se aprofundar no framework.

This book is hard to navigate as no table of content. I need TOC so i can jump to a different topic easily.

Exactly what I was looking for. Simple and efficient.