Bug#781033: python-django: "manage dbshell" fails to transmit settings password to postgresql

On Mon, Mar 23, 2015 at 11:46:34PM +0100, Raphael Hertzog wrote: > So I submitted this suggestion there and have marked this bug as forwarded. I believe this has been fixed upstream in git for Django 1.9. No idea if it has been backported to 1.8, probably not. -- Brian May

Bug#781033: python-django: manage dbshell fails to transmit settings password to postgresql

Package: python-django Version: 1.7.6-1 Severity: minor Hi When one runs the generated ./manage.py with runserver argument, django find the host, dbname, username, and password and runs ok. But when one runs it with dbshell argument, django only uses host, dbname and username. Then a prompt

Bug#781033: python-django: manage dbshell fails to transmit settings password to postgresql

Hi, On Mon, 23 Mar 2015, Jean-Michel Nirgal Vourgère wrote: When one runs the generated ./manage.py with runserver argument, django find the host, dbname, username, and password and runs ok. But when one runs it with dbshell argument, django only uses host, dbname and username. Then a

Bug#781033: python-django: manage dbshell fails to transmit settings password to postgresql

Hi Raphael Hertzog wrote: On Mon, 23 Mar 2015, Jean-Michel Nirgal Vourgère wrote: (...) When one runs the generated ./manage.py with (...) dbshell argument, django only uses host,dbname and username. Then a prompt asks the user for the password. dbshell just runs psql with the appropriate

Bug#781033: python-django: manage dbshell fails to transmit settings password to postgresql

Control: forwarded -1 https://code.djangoproject.com/ticket/23658 On Mon, 23 Mar 2015, Jean-Michel Nirgal Vourgère wrote: Another possibility is PGPASSFILE env, that provide an alternate ~/.pgpass file. I believe a temporary file would work. This wouldn't require hacking any existing .pgpass.