Description of problem:
/usr/lib/python3.3/site-packages/django/bin/django-admin.py has the following interpreter defined '#!/usr/bin/env python' however on Fedora 19 the default Python version is 2 therefore it fails to execute as django libraries cannot be found

Version-Release number of selected component (if applicable): 
Fedora release 19 (Schrödinger’s Cat)
python3-django-1.5.4-1.fc19.noarch

How reproducible:
Always

Steps to Reproduce:
1. Run /usr/lib/python3.3/site-packages/django/bin/django-admin.py


Actual results:
$ /usr/lib/python3.3/site-packages/django/bin/django-admin.py
Traceback (most recent call last):
  File "/usr/lib/python3.3/site-packages/django/bin/django-admin.py", line 2, in <module>
    from django.core import management
ImportError: No module named django.core


Expected results:

$ /usr/lib/python3.3/site-packages/django/bin/django-admin.py
Usage: django-admin.py subcommand [options] [args]

Options:
  -v VERBOSITY, --verbosity=VERBOSITY
                        Verbosity level; 0=minimal output, 1=normal output,
                        2=verbose output, 3=very verbose output
  --settings=SETTINGS   The Python path to a settings module, e.g.
                        "myproject.settings.main". If this isn't provided, the
                        DJANGO_SETTINGS_MODULE environment variable will be
                        used.
...


Additional info:
If the script is updated to reflect '#!/usr/bin/env python3' it works as expected.

Also can
ln -s /usr/lib/python3.3/site-packages/django/bin/django-admin.py /usr/bin/django-admin.py
be added to the rpm script so its immediately available on the path?