Re: [Numpy-discussion] Temporary error accessing NumPy tickets

2012-08-31 Thread Pauli Virtanen
01.09.2012 00:08, Ognen Duzlevski kirjoitti: [clip] > I personally think moving away from Trac (which IMHO is bloated and > awkward in addition to having a very weird way of being administered) > would be a better idea. Yes, moving away from Trac is planned, both for Numpy and Scipy. Also agreed o

Re: [Numpy-discussion] Temporary error accessing NumPy tickets

2012-08-31 Thread Ognen Duzlevski
On Fri, Aug 31, 2012 at 11:35 AM, Pauli Virtanen wrote: > Ondřej Čertík gmail.com> writes: >> When I access tickets, for example: >> >> http://projects.scipy.org/numpy/ticket/2185 >> >> then sometimes I get: >> >> Trac detected an internal error: >> OperationalError: database is locked >> >> For

Re: [Numpy-discussion] Temporary error accessing NumPy tickets

2012-08-31 Thread Ondřej Čertík
On Fri, Aug 31, 2012 at 9:35 AM, Pauli Virtanen wrote: > Ondřej Čertík gmail.com> writes: >> When I access tickets, for example: >> >> http://projects.scipy.org/numpy/ticket/2185 >> >> then sometimes I get: >> >> Trac detected an internal error: >> OperationalError: database is locked >> >> For e

Re: [Numpy-discussion] Temporary error accessing NumPy tickets

2012-08-31 Thread Pauli Virtanen
Ondřej Čertík gmail.com> writes: > When I access tickets, for example: > > http://projects.scipy.org/numpy/ticket/2185 > > then sometimes I get: > > Trac detected an internal error: > OperationalError: database is locked > > For example yesterday. A refresh in about a minute fixed the problem.