psycopg2.ProgrammingError: autocommit cannot be used inside a transaction
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Django |
Fix Released
|
Unknown
|
|||
python-oops-tools |
Fix Released
|
High
|
Gavin Panella |
Bug Description
When running tests I get:
Creating test database for alias 'default'...
Traceback (most recent call last):
File "bin/test", line 49, in <module>
djangorecip
File ".../eggs/
management.
File ".../parts/
utility.
File ".../parts/
self.
File ".../parts/
self.
File ".../parts/
output = self.handle(*args, **options)
File ".../eggs/
super(Command, self).handle(*args, **kwargs)
File ".../parts/
failures = test_runner.
File ".../parts/
old_config = self.setup_
File ".../parts/
test_db_name = connection.
File ".../eggs/
f(*args, **kwargs)
File ".../parts/
self.
File ".../parts/
self.
File ".../parts/
self.
psycopg2.
Related branches
- Diogo Matsubara (community): Approve
-
Diff: 25 lines (+4/-0)2 files modifiedsetup.py (+1/-0)
versions.cfg (+3/-0)
Changed in django: | |
status: | Unknown → Fix Released |
Changed in python-oops-tools: | |
status: | Triaged → Fix Committed |
assignee: | nobody → Gavin Panella (allenap) |
Changed in python-oops-tools: | |
status: | Fix Committed → Fix Released |
See https:/ /code.djangopro ject.com/ ticket/ 16250. There's an incompatibility between Django 1.3 and python-psycopg2 2.4.2 (oneiric version). Suggested workaround is to use a previous version of python-psycopg2 or to update to django trunk since this won't be in the next point release and AFAICT there's no 1.4 release yet.