Re: ImportError: cannot import name actions

2013-10-17 Thread y venkatesh
ModelAdmin, actions > [Tue Oct 15 12:50:36 2013] [error] [client 127.0.0.1] ImportError: cannot > import name actions > > by doing the following change, I could get rid of what looked like a > circular import issue: > --- a/django/contrib/admin/sites.py > +++ b/djang

Re: ImportError: cannot import name actions

2013-10-16 Thread the . paper . men
Hi, Tom and rok! I didn't mean to start http server flame war, Apache obviously has it's upsides and we also use it. What I've proposed is a simple, albeit dirty, workaround to run non-forked Django 1.6 in production. For Django devs to be able to address the root of the issue and solve it pro

Re: ImportError: cannot import name actions

2013-10-16 Thread Tom Evans
On Wed, Oct 16, 2013 at 3:20 PM, wrote: > Ouch! I should have read your post more carefully! If you don't have any > other options than to use Apache, you could run it as proxy to gunicorn. Or > you could use Nginx instead of Apache... What, precisely, is wrong with Apache httpd/mod_wsgi as a ho

Re: ImportError: cannot import name actions

2013-10-16 Thread rok
Hi, I am not a particular evangelist of one or the other but since we use apache+mod_wsgi for several apps throughout the company, we obviously want to stick with one, easier for deployment and maintenance. On Wednesday, October 16, 2013 5:17:35 PM UTC+2, Tom Evans wrote: > > On Wed, Oct 16, 20

Re: ImportError: cannot import name actions

2013-10-16 Thread the . paper . men
ck. > > Rok > > On Wednesday, October 16, 2013 9:39:28 AM UTC+2, the.pa...@gmail.comwrote: >> >> Hi! >> >> Original Message ---- >> Subject: Re: ImportError: cannot import name actions >> Date: Wed, 16 Oct 2013 11:26:33 +0400 >> From: Iv

Re: ImportError: cannot import name actions

2013-10-16 Thread rok
gt; Hi! > > Original Message > Subject: Re: ImportError: cannot import name actions > Date: Wed, 16 Oct 2013 11:26:33 +0400 > From: Ivan Kharlamov > > To: django-d...@googlegroups.com > > On 10/15/2013 04:56 PM, rok wrote: > > I have recently been

Re: ImportError: cannot import name actions

2013-10-16 Thread the . paper . men
Hi! Original Message Subject: Re: ImportError: cannot import name actions Date: Wed, 16 Oct 2013 11:26:33 +0400 From: Ivan Kharlamov To: django-develop...@googlegroups.com On 10/15/2013 04:56 PM, rok wrote: > I have recently been testing the 1.6b4 tag with a new app we

ImportError: cannot import name actions

2013-10-15 Thread rok
b/admin/sites.py", line 3, in [Tue Oct 15 12:50:36 2013] [error] [client 127.0.0.1] from django.contrib.admin import ModelAdmin, actions [Tue Oct 15 12:50:36 2013] [error] [client 127.0.0.1] ImportError: cannot import name actions by doing the following change, I could get rid of what