Got this while tried to laucnh Djangos test suite on
fb1e3435a4d7e0265f19a1a9f130c9485fb8dfe9
On Tuesday, October 15, 2013 4:56:56 PM UTC+4, rok wrote:
>
> I have recently been testing the 1.6b4 tag with a new app we are writing,
> using apache and wsgi. However, I could not get rid of the follo
Can you perhaps try it with a check out of Django and use git bisect to
find the cause? That might give us an indication of how the code base has
changed to break it for you. Without a means of reproduction it is hard for
us to do anything.
Marc
On 17 Oct 2013 09:12, "rok" wrote:
> Hi everyone,
Hi everyone,
unfortunately I am not able to reproduce it from a "scratch-point", I am
sorry.
Also, we are not using gunicorn, just apache+mod_wsgi.
I read somewhere that this could be related to the python path so I checked
it in dev and production environments, and simply set the same path in
Hi!
On 10/15/2013 04:56 PM, rok wrote:
> I have recently been testing the 1.6b4 tag with a new app we are
> writing, using apache and wsgi. However, I could not get rid of the
> following issue happening on every request:
>
> ...
> [Tue Oct 15 12:50:36 2013] [error] [client 127.0.0.1] File
> "/
Hi Rob,
If you're able to generate a cyclic import error in 1.6b4, then that's
definitely a release blocker.
The first step is obviously to reproduce the bug. This isn't something I've
seen in my testing, and that particular file (sites.py) hasn't changed in 5
months (at least, not in the 1.6 bra
On Tue, Oct 15, 2013, rok wrote:
>I thought since the 1.6 release is in the final stretch this might be
>somewhat related to bugfixing. I posted it to the users forum.
Well it could indeed be a bug of course. Is it feasible for your to reduce it
to something easily reproducible?
Daniele
--
Thanks Daniele,
I thought since the 1.6 release is in the final stretch this might be
somewhat related to bugfixing. I posted it to the users forum.
Rok
On Tuesday, October 15, 2013 5:11:36 PM UTC+2, Daniele Procida wrote:
>
> On Tue, Oct 15, 2013, rok > wrote:
>
> >I have recently been testin
On Tue, Oct 15, 2013, rok wrote:
>I have recently been testing the 1.6b4 tag with a new app we are
>writing, using apache and wsgi. However, I could not get rid of the
>following issue happening on every request:
You'll be better off asking this question over on the Django users email list,
rat
