django-poste-restante/django-poste-restante — pull request #1 by yedpodtrzitko (2013-07-31 19:22:39+00:00)
Title: move tests outside of project, some standard project environment changes

* tests moved outside of project level

motivation:

I cloned this project and tried to run it via `./manage.py shell`, but I got error about missing `django_nose`. And this was why I started modifying of project structure to way how it worked and how I'm used to have it.

- I think there's no need to have `django_nose` in `INSTALLED_APPS` because it's used only for tests, right? So I created standalone folder for tests with their own settings. There's also another point - I would probably like to deploy it somewhere later and I don't want to have tests on my production machine so it's much easier to distinct this single `tests` folder than multiple folders everywhere in project.

There's a few other changes which are usual way as it's used to create structure for django project:
- shallower project folder (is there some reason to create subfolder, when you need to symlink folder from root in there?)
- settings as a directory instead of file (common best practice: it's easier to customize settings for production/localhost etc. - see _ _ init _ _ .py in there)
- urls.py: patterns for static files for the time of localhost developement

I know it's a lot of changes, but it's shame to have two forks right now in the beginning of the project, isn't it?