openhatch/oh-mainline — pull request #75 by briandant (2012-10-11 20:38:52+00:00)
Title: Updated Django to 1.3.3 (Issue #753)

*Sorry if I'm abusing Markdown. I'm just learning it, so I'm trigger-happy!*

I *think* everything is ok with this commit because the tests before and after the Django install showed the same results. However, there are a few things I'd like you to look at before merging:

I created a pastebin of output pertaining to the issues below: http://pastebin.mozilla.org/1864267

**Running Entire Suite vs One-By-One:**
When I ran the entire suite, it said there were only 2 `failures`, 1 `error`, and 83 `skipped`. When I ran them one-by-one I got more `errors` (16), but the same amount of `failures` and `skipped` tests. Why is that?

**Why so many skipped tests?**
83 `skipped` tests is a lot. Why is it skipping so many? I'm not able to get the `lxml` module. Is that the reason? (If so, I could use some guidance on that b/c I'm fairly confident I have the proper headers and don't know what to do next).

**No output on some tests?**
There was a test output behavior that confused me: some of the tests didn't ouput anything -- I didn't even get the `ran 0 tests` output. These tests are highlighted in the pastebin.

**Summary: `Skipped`, `Failures`, and `Errors`:**
83 tests `skipped`:
* customs: 68 `skipped`
* accounts: 2 `skipped`
* profile: 2 `skipped`
* search: 11 `skipped`

2 `failures`:
* accounts: `2 failures`

16 `errors`:
* accounts: 1 `error`
* invitation: 2 `errors`
* registration: 13 `errors`

**Other Stuff:**
`git autocrlf`: When I cloned the repo, my commits were failing with this message: `fatal: CRLF will be replaced by LF` [This question](http://stackoverflow.com/q/1967370) on Stack Overflow addresses the issue (although I was getting the inverse: CRLF to LF (and it was `fatal`)). How do you normally handle this? I ended up changing my local setting `core.autocrlf` to `false` and it cleared up the issue. (**Which makes me wonder if that is now the setting in what I am pushing to you in `.git`? I bet it is. Is that a prob?**)

The Django root directory currently has a big `D` in Django, and when I installed the new Django from `Pip` it comes with a small `d'. This isn't a huge deal, but might trip somebody up in the future. The tests initally failed, complaining of a missing module. Let me know if you like me to change this (although I'm guessing it's more work to change it instead of just dealing with it like I did. And, don't really know what the other option would be).