Live data from Hacker News

Our Django Book is Launched

pydanny.com

101–110 of 136 posts

Re: Our Django Book is Launched

#102
As a new django user, one of the most confusing issues to deal with is deployment. Many guides say a few hand-wavy things about deployment, and then move on. Can anybody summarize what this book says about deployment?

By the way, congratulations on releasing this! I've been looking forward to seeing what the "mad secret project" was.

Re: Our Django Book is Launched

#104
post #102

As a new django user, one of the most confusing issues to deal with is deployment. Many guides say a few hand-wavy things about deployment, and then move on. Can anybody summarize what this book says about deployment? By the way, congratulations on releasing this! I've been looking forward to seeing what the "mad secret project" was.

Chapter 25 is a short 4 page chapter on deployment. I do look forward to having a chance to read it all.

Re: Our Django Book is Launched

#106

Just bought the book, not really spelunked it much yet but looks pretty cool so far - I'm just getting to grips with django and other python web frameworks generally. One tiny annoyance is the lack of pre-generated bookmarks based on the contents page. See [1] for example of how Uncle Bob's clean code PDF ships with these (my PDF reader is Foxit). These bookmarks save a hell of a lot of time navigating back and forth…

Just so you know, I'm one of the authors.

I agree with you 100%.

Unfortunately, the tool we used to format the book doesn't do this for us, so we either have to use a third-party product to do it manually OR write a Python script to generate the bookmarks.

We intend to start working on the Python script tomorrow, and I really want to get it into the BETA release.

Thanks for the feedback!

Re: Our Django Book is Launched

#108
I develop Django professionally, bought the book, and just finished a quick read through. I am very impressed. Some may rightly say you can get all the information in the book elsewhere and for free, I wouldn't want to. This book would have saved me many hours over the last few years. $12 is a bargain. I think the depth and breadth is just right and would highly suggest it for (nearly) every level of Django developer.

My one complaint, to not just this book, but pretty much the community at large is there exists scant documentation dealing with 'enterprise grade'database migration (..both data and schema, for some reason data is always left out) with Django and South.

Nice work.

P.S. - I've made a small pull request to your django template as it doesn't work in it's current form.

Re: Our Django Book is Launched

#109
I develop Django professionally, bought the book, and just finished a quick read through. I am very impressed. Some may rightly say you can get all the information in the book elsewhere and for free, I wouldn't want to. This book would have saved me many hours over the last few years. $12 is a bargain. I think the depth and breadth is just right and would highly suggest it for (nearly) every level of Django developer.

My one complaint, to not just this book, but pretty much the community at large is there exists scant documentation dealing with 'enterprise grade'database migration (..both data and schema, for some reason data is always left out) with Django and South.

Nice work.

P.S. - I've made a small pull request to your django template as it doesn't work in it's current form.

Re: Our Django Book is Launched

#110
post #4

So, full disclaimer: I was one of the editors of this book. This is a really great 'best practices' book for Django developers of all skill levels. In the Django community, there are a variety of practices that people tend to use: webapp structure, coding conventions, library preferences, etc. As a Django developer, finding out 'which way should I do X' is often harder than it seems: there are tons of articles on Goo…

Having recently started Django for a small gig, I have found searching for Django documentation, tips, and practices, to be extremely difficult and confusing, especially coming from the Rails world where blog posts seem a dime a dozen.

I spent a long time looking for good info only to find outdated or poorly maintained docs, and a very little sense of "community".

I'll probably grab this book to get me jumpstarted. I'm happy, yet sad that I have to find my information this way -- says something about the community IMO (not a bash on you, but just a nag on the Django community as a whole as I feel it doesn't really like helping beginners).

Post reply on HN