Yeah, that'll work. django-discover-runner is less invasive, IMO, though, and works really nicely with standard Django testing setups or more-package-oriented ones.
sure. discover-runner is still more convenient than the default one. from what I read on django-dev, 1.6 will probably switch to unittest2 which has a better discovery, not sure about the details though since I switched to nose.
Just started it up (personally), but I blog about...shit, don't really know yet. Likely programming, personal life (dad, husband, etc), and the like. http://blog.gigantuan.net
My professional blog, mostly about Python and Django, is at http://brack3t.com
I'm running VirtualBox 4.2.4 but I would think, since it creates the VM when you `vagrant up`, that it wouldn't matter what version of VB you were running. So that's odd.
The Vagrant version I have is 1.0.5, just for completeness sake.
I just downloaded the zip file again to check, and there's nothing in there (at least that I can find) that mentions a version of VirtualBox. You're also the first person to mention a problem like this (one other person had a problem after running the VM with getting packages from Google).
You could try downgrading, or, since you're on a sane OS, just running everything sans VM. You'll need to install Git and PostgreSQL yourself, though.
Let me know if anything changes, please. I'll ask around and let you know if I find anything out.
Looks like my problems were completely my fault. On my ThinkPad the virtualization setting is in the BIOS under Security and it was not set correctly. There were some
other settings under CPU that I initially thought were the right ones. I'm sorry to waste your time.
Is it worth putting a link to the kickstarter on the front page? Would certainly help explain a lot about the project and if it's still running people can chip in.
