I think everybody involved agrees that screencasts are almost guaranteed to generate LOTS of interst. And it's not for lack of understanding that (or lack of effort) on the part of the developers that Django doesn't have any official ones. I know everyone's impatient to see Django take over the world, but I think there's a conscious effort (at least on my part) to restrain some of the concerted "universal" marketing for the 1.0 release.
As David Ascher pointed out, there are some key changes to be made for 1.0 (including the new-admin integration and other backwards-incompatible changes) that will make Django itself significantly more cohesive and accessible. I personally am wary of making a concerted effort to attract wider adoption of Django from non-early-adopter-types until those changes are done. No matter what, new adoption is going to mean new users for the community to support, and I'd much rather that effort was being put into giving instructions that aren't going to change tomorrow. As has been oft repeated, first impressions matter. I'd hate for the inevitable interest generated by things like screencasts to be squandered if half the people that check out Django it's too confusing. Django has already attracted a great community of developers and early-adopters that have made huge contributions to improve it. There's a good chance that community is going to go on full-time n00b support duty the day Django releases a screencast. Think about it. Do YOU want to be the one to explain core fields to 100 new Django users? Let's keeping pushing to a 1.0 release candidate, and I bet some frighteningly compelling screencasts will be on their way sooner than you think.
