Permalink
Browse files

ci me

  • Loading branch information...
jbalogh committed Mar 28, 2013
1 parent c8366ed commit cff3b1c397d5a7c29843a394dbf799949d4c0845
Showing with 28 additions and 8 deletions.
  1. +17 −0 .travis.yml
  2. +11 −8 README.rst
View
@@ -0,0 +1,17 @@
+language: python
+python:
+ - "2.6"
+ - "2.7"
+before_install:
+ - export PIP_USE_MIRRORS=true
+ - export PIP_INDEX_URL=https://simple.crate.io/
+install:
+ - pip install south
+ - pip install Django==$DJANGO
+ - pip install -e .
+script:
+ - ./runtests.sh
+env:
+ - DJANGO=1.3.3
+ - DJANGO=1.4.1
+ - DJANGO=1.5
View
@@ -2,6 +2,9 @@
django-nose
===========
+.. image:: https://travis-ci.org/jbalogh/django-nose.png
+ :target: https://travis-ci.org/jbalogh/django-nose
+
Features
--------
@@ -265,21 +268,21 @@ Older Versions of Django
------------------------
Upgrading from Django <= 1.3 to Django 1.4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-In versions of Django < 1.4 the project folder was in fact a python package as
-well (note the __init__.py in your project root). In Django 1.4, there is no
+In versions of Django < 1.4 the project folder was in fact a python package as
+well (note the __init__.py in your project root). In Django 1.4, there is no
such file and thus the project is not a python module.
-**When you upgrade your Django project to the Django 1.4 layout, you need to
-remove the __init__.py file in the root of your project (and move any python
-files that reside there other than the manage.py) otherwise you will get a
+**When you upgrade your Django project to the Django 1.4 layout, you need to
+remove the __init__.py file in the root of your project (and move any python
+files that reside there other than the manage.py) otherwise you will get a
`ImportError: No module named urls` exception.**
-This happens because Nose will intelligently try to populate your sys.path, and
-in this particular case includes your parent directory if your project has a
+This happens because Nose will intelligently try to populate your sys.path, and
+in this particular case includes your parent directory if your project has a
__init__.py file (see: https://github.com/nose-devs/nose/blob/release_1.1.2/nose/importer.py#L134).
This means that even though you have set up your directory structure properly and
-set your `ROOT_URLCONF='my_project.urls'` to match the new structure, when running
+set your `ROOT_URLCONF='my_project.urls'` to match the new structure, when running
django-nose's test runner it will try to find your urls.py file in `'my_project.my_project.urls'`.

0 comments on commit cff3b1c

Please sign in to comment.