I apologize if this has already been brought up and trampled to death. Towards the end, when Quentin makes his cameo appearance, he has a conversation with Django. I noticed he never uses the N-word (despite the movie being filled with it) and he opts for the word 'black' instead. Was there a purpose in this?

I'm a complete newbie to AJAX so I've to ask this question.

I'm starting a project for a web app using Django as the framework. It'll be heavily AJAX dependent, and there seem to be two popular ways of using AJAX in a Django project. One, simply using JQuery and it's AJAX methods. Two, using Dajaxice.

If anyone's used both of these here, can you tell me about the advantages and disadvantages of each method? Which one would you recommend?

Inglourious gets it for me.

Django didn't quite get the heart racing as much.

I enjoyed the strong female characters in Basterds (where django scarcely gave femmes a line), plus, the whole historical revenge deja vu removed a bit of Django's shine.

I did enjoy Django though, on many levels.

I am an amateur web technology tinkerer for quite some years now. I have good knowledge of PHP project workflow meaning: develop schema, use the framework, test and just deploy to remote host. Everything most of the times just works.

I've been learning about Django for about a month now and I am getting a good understanding of how stuff happens with it. My biggest gripe is deployment. I see people talking about Vagrant, Chef/Puppet etc and I am really confused what is the proper way to do stuff using these tools. Do I really need to go through these?

tl;dr: What is the easiest way to deploy Django apps?

In Django, one of our heros Christopher Walt'z' Dr. King Schultz at one point was a Dentist-which seems like a strange offbeat choice to have a character have that as an occupation at first. Dig a little deeper and start looking at the naming conventions of the film.

You have Dr. King Schultz, a third party outsider who's current job is to thwart the evils at hand and the spreading issue of racism and slavery running rampant throughout the south.

Fine- he used to be a Dentist- whatever- this is Tarantino right? He's wrought with quirky decision making.

But then take a look at who he's first hunting; The Brittle Brothers. Aside from a few things, the only thing that comes to mind when I hear the word Brittle is sweet sugary Brittle Candy- as in Peanut Brittle and Caramel brittle, all syrup cooked to sweet perfection. He finds and eradicates them with the help of freed slave Django, only to name his next target; Calvin Candie- owner of "Candie Land" In short- the south is an invented cavity laden cesspool. The infection of slavery is growing and Dr. King Schultz is the living remedy.

Not to mention to one look at Calvin Candie and you see-maybe more than anyone-is in need of a Dentist. He sucks down Coconut juice- pure, cavities causing straight cane sugar. So in context you see, He IS the cavity and Dr. Schultz is there to to eradicate him.

Tarantino uses the so-good but-so-bad for you analogy of candy as the infected spreading epidemic of slavery and racism in the south to highlight it's need to be stopped.

I keep a simple blog on my portfolio site for things I come across that might be useful or confusing with Django, but I find it difficult to come up with topics as it's hard to remember what was confusing about something after you have figured out and have been familiar with Django for a while!

Are there any parts of Django that people find particularly confusing or worthy of explanation, or any other topics that people might find interesting as a blog post (or aren't fully covered by the docs etc.)?

Sometimes in jobs ads the employer ask for an "experienced" Django developer.

What qualities does an employee expect in a developer when they're an "experienced" Django developer as opposed to a relative noob ?

I'm interested in specific parts of Django/add-ons that employees think an experienced developer might be familiar with.

Fantastic 1938 Footage of Django and Le Quintette du Hot Club de France.

Serious question. I have my reasons for asking. What features would you require in a web framework, that would make you abandon Django as your framework of choice?

Or if Django isn't your framework of choice, what features would make you consider a new framework?

James Remar plays both Ace Speck (the first guy shot in the movie by Schultz) and Butch pooch, the guy that eventually kills Dr. Schultz.

Could it be that he's the same guy? Imagine he survived the shot (the bride survived worse in Kill Bill) and lost his memory.

When Django shows up at the bar and sees him, he shows some sign of recognition and mentions that "no man wears a hat inside" as though maybe he had half his skull missing and that's why he wears a hat.

He even wears a hat while eating dinner.

Butch also never trusts Schultz and Django at all (maybe his subconscious considering he lost his memory?)

What do you think?

everything about it was very well done. Spoiler. with all the action and music, I really got into it at that part. I think that is something most filmmakers are unable to achieve. I also like how Samuel Jackson's character wasn't very Sam Jackson-like. the only thing I had a problem with (and not that big of a problem with) is Spoiler edit: it may have been wrong about it being the KKK but it was the same general thing edit: everyone knows that DiCaprio cut his hand

Django Unchained rocked. Quintessential Tarantino for Christmas Day. What a present. BTW Spike Lee should see the movie before offering an opinion

http://movies.netflix.com/WiMovie/Life_After_Django_Reinhardt/70217591?trkid=7115812

Life After Django Reinhardt isn't just about the man himself, but about how his influence has affected guitarists around the world. Great little documentary.

A lot of the django reviews I read say that django can do a lot but when you need to do something it wasn't designed for then there's a lot of jumping through hoops.

Can someone provide examples? I'm in the process of picking a framework to work and that idea scares me a bit. Right now it's django vs flask vs pyramid

I'll start with my own list:

• django-grappelli
• django-modeltranslation (fork)
• easy_thumbnails
• south
• userena
• django-guardian

I will add more later with links to projects repos (I'm on mobile right now)

Update:

Some have been quicker than me, but I'll list them anyway:

• django-elasticsearch
• django-haystack
• django-tastypie
• django-reversion
• django-debug-toolbar
• django-generic-flatblocks
• django-positions
• django-mptt

Those are some I developed and use frequently:

• django-seoutils
• django-courier
• grappelli-fit
• django-frontadmin

After a few years using php i'm dying to try something else and since i already know Python i'm looking for any tutorials/screencast django related. I'm currently watching the introduction to django from the last pycon but if you got anything else, feel free to share.

http://pyvideo.org/video/604/introduction-to-django

http://pyvideo.org/video/610/django-in-depth

El slides:

http://media.b-list.org/presentations/2012/pycon/django-in-depth.pdf

I'll start

Django Filebrowser (and Django Grappelli to a lesser extent)

Django Debug Toolbar

Django South

Django Extensions

Django Registration

(First of all! don't make this a flamewar)

1. I really like the assets management, all pluggable apps I found for Django are tricky or don't do all the job, it's something that you will like to have in the core of django, have preprocessors (to manage sass, or less), compilers, and minimizers for all the assets.

2. The support for multiple template engines is transparent and easy, I really will love to use HAML in django.

I've always hard that the best way to go about django, is to setup the proper environment with respect to IDE integration, django-extensions, extras, deployment script/tools, security measures, etc ...

I ask because after a years unemployment I think I've taught myself python and django, (I made some websites for charity that are happily working on the app engine), but I have no idea if my level of competence is laughably amateur.

oh and I do happen to have a phone interview on Friday, hence the slightly needy questioning

Please specify operating system, software, price, addons etc. I'm having problem finding a texteditor for my OSX which has the correct markup. Which one do you use?

EDIT: Thanks for replies, didn't expect that much activity. I see there are a lot of diffrent editors currently in use by us Django developers. I'll try to tl;dr the comments:

• Textmate with Django addon

• Vim with NERDTree

• Emacs with nxhtml , uniquify , flymake + pep8 & pylint & pyflakes , rope + ropemacs

• PyCharm

• Notepad++

• E-texteditor , Textmate for Windows

• Gedit

• Coda with addon

• WingIDE

• Komodo Edit

• Eric IDE

I'm interested in trying out a python web framework and the two big ones seem to be django and web2py (or others if you prefer something else?). I'm curious what others are using and why. I did a reddit search and didn't see a recent submission regarding this, but sorry if it's a commonly asked question.

Edit: Wow... pylons, Flask, Bottle, CherryPy, Django, web2py... I should have known that there would be a flurry of different projects out there each with their own niche. I guess if you have experience with any of them post your opinions for me :)

We wanted to post earlier why we like/use Django, but, we get pretty busy around here, so a bit late. Sorry if this is duping any existing threads.

Why

This is not a Drupal vs Django fight, we're not here to slag Drupal, Drupal has been important to The Onion, but The Onion decided to stop using Drupal a long time ago. The Onion deployed a Drupal site back in 2005, at the time it was the right decision given the resources, yet even then we were interested in using Python whenever possible. We feel it is a vastly better designed language than PHP and of course any framework you're using is only as good as the language. We started rolling out other projects, like The A.V. Club, in Django. Just this past weekend we switched over The Onion proper, and we're seeing immediate gains in speed, maintainability, and stability. As a team we have a pretty broad base of experience and I know we're all in agreement that what we've got now is better, enormously better. We're not just using Django, we have some other pieces that made our lives easier: git, PostgreSQL, VPS's. So this isn't just about The Onion using Django (and recommending it), but generally that you can make things better by investing time and energy into new technology.

How

It took us about 3 months to convert our old Onion site to Django while we also maintained and built on our other sites. We already had some components written for A.V. Club, including a strong article and image model, so we felt we could concentrate on coming up with good models that covered the necessary editorial cases. The hard part was more how to fit pieces of content from ten years ago consistently and cleanly than it was writing the code to make use of the final model. We broke out templates into nicely reusable components and made use of the Django template hierarchy. Multi-db made the conversion of data from a MySQL db to the PostgreSQL db fairly easy, so we could rerun importing old data into the new system and fix and tweak. There is an enormous advantage using Django, sorl and PIL for creating image crops based on templatetags which gives the editorial and design folk flexibility they need (no more css cropping odd-sized images into place). Again, lots of work went into actually cleaning a site that goes back to 1996, Django allowing for a relatively minimal amount of coding -- particularly when it comes to the admin side for content entry, Django trunk we found almost ready to go as-is (something we did not find with previous Django). That we could use the Django admin rather than create custom entry forms I think saved us 2 months work.

Because

Cleaner. Much cleaner. Proper unit testing. Real reusable components across applications. An ORM rather than a just a series of functional query helpers. Tighter conventions (q: how often do people using Python argue about bracing styles? a: they don't). We can update then test a Django core change without worrying about having to take apart our applications, and if we do need to make a change, it's easy to do because there's less, much more readable code. Every member of the tech team can meaningfully contribute because there are fewer specialized or hacked together pieces. We can move more quickly on large changes because of all these reasons. And we're more stable because of all the previously expressed points.

-- The Onion Tech Team