django-admin.py shebang

Hi devs, Is there a good reason for having the shebang line in django-admin.py at #!/usr/bin/python "instead" of #!/usr/bin/env python ? My problem is I have a newer version of Python installed in */usr/local/opt/* declared in my PATH that I want to test but the hardcoded path to

Re: django-admin.py shebang

Hi Stan, In the source, it's looks like it's been using #!/usr/bin/env python for almost 10 years: https://github.com/django/django/blame/master/django/bin/django-admin.py My quick guess is that gets modified when installing. Did you use the newer version of python to install django? Collin

Re: django-admin.py shebang

Hi Stan, how did you install Django? As a system package via the system's package manager or via pip. If its the system package manager, please raise that bug in the bug tracker of your Linux distribution. If the answer is "via pip", from where? PyPI or something obscure? As Collin already

Re: django-admin.py shebang

On Wednesday, April 1, 2015 at 3:58:13 PM UTC+2, Collin Anderson wrote: > > Hi Stan, > > In the source, it's looks like it's been using #!/usr/bin/env python for > almost 10 years: > https://github.com/django/django/blame/master/django/bin/django-admin.py > I didn't check that... > > My

Re: django-admin.py shebang

On Wednesday, April 1, 2015 at 4:15:25 PM UTC+2, Markus Holtermann wrote: > > Hi Stan, > > how did you install Django? As a system package via the system's package > manager or via pip. If its the system package manager, please raise that > bug in the bug tracker of your Linux distribution.

Re: django-admin.py shebang

On Wed, Apr 1, 2015 at 10:28 AM, Stan wrote: > A classical pip install Django command without --mirrors or --use-mirrors > modifier. > > I did some --upgrade, but the first installation is not 10 years old (2 > maybe). > > > Pip is a Debian package (1.1.3) > > [$

Re: django-admin.py shebang

Hi Stan, If possible, I'd recommend (somehow) getting a pip built against your /usr/local/bin/python, then "/usr/local/bin/pip install django" should do what you want. Collin On Wednesday, April 1, 2015 at 11:28:33 AM UTC-4, Stan wrote: > > > > On Wednesday, April 1, 2015 at 4:15:25 PM UTC+2,

Re: django-admin.py shebang

On Wednesday, April 1, 2015 at 5:34:55 PM UTC+2, James Bennett wrote: > > This right here is the giveaway that what you're looking at is Debian's > version of Django (they modify the name from 'django-admin.py' to > 'django-admin' to suit their policies for file naming). > Newer Django

Re: django-admin.py shebang

On Wednesday 01 April 2015 18:34:35 James Bennett wrote: > On Wed, Apr 1, 2015 at 10:28 AM, Stan wrote: > > A classical pip install Django command without --mirrors or --use-mirrors > > modifier. > > > > I did some --upgrade, but the first installation is not 10 years

Re: Pre-DEP: community support of unmaintained versions of Django

Carl, your proposal sounds good to me. I would be happy to contribute to a DEP, if formalization of the process is necessary. Christian, let's coordinate to set up a public/private repo pair with the appropriate warnings and have one of us apply for the pre-release notifications (if you haven't

[ANNOUNCE] Django 1.8 released

Django 1.8, the next long-term support release, is now available: https://www.djangoproject.com/weblog/2015/apr/01/release-18-final/ With the release of Django 1.8, Django 1.6 has reached end-of-life. As such, Django 1.6.11 is the final release of the 1.6 series. Django 1.7 will continue to

Using AbstractBaseUser without django.contrib.auth

While trying out Django 1.8 with one of my sites that uses a custom User model (and doesn't have django.contrib.auth in INSTALLED_APPS), I noticed a few unexpected deprecation warnings: /Users/dcwatson/Documents/Environments/reader/lib/python3.4/site-packages/django/contrib/auth/models.py:41:

Re: Using AbstractBaseUser without django.contrib.auth

Does your model inherit from PermissionsMixin? If you're using Admin, or any of Django's permissions machinery, you will need django.contrib.auth in there to use the Group and Permission models. -- Curtis On 2 April 2015 at 13:47, Dan Watson wrote: > While trying out

Re: Using AbstractBaseUser without django.contrib.auth

On Wednesday, April 1, 2015 at 10:50:17 PM UTC-4, Curtis Maloney wrote: > > Does your model inherit from PermissionsMixin? > > If you're using Admin, or any of Django's permissions machinery, you will > need django.contrib.auth in there to use the Group and Permission models. > > I'm using my own