>> 1) The use of string constants to identify NumPy processes. It would
>> seem better to use library defined constants (ufuncs?) for better
>> future-proofing, maintenance, etc.
>
> I don't see how this would help with future-proofing or maintenance --
> can you elaborate?
>
> If this were C, I'd
The idea is to allow people to test-out YouTrack for a few weeks and get to
know it while we migrate bugs to it. it looks like it is straightforward to
export the data out of YouTrack should we eventually decide to use something
else.
The idea is to host it on an external server (Rackspace
Hi,
I moved projects.scipy.org Tracs to run on mod_python (instead of CGI),
in order to try to combat the present performance issues. Let's see if
this helps with the "database is locked" problem.
Please drop me a message if something stops working.
Pauli
___
It doesn't work because numpy.append(a, ...) doesn't modify the array a
in-place: it returns a copy.
Then in your append method, doing "self = numpy.append(...)" won't have any
effect: in Python such a syntax means the "self" local variable will now
point to the result of numpy.append, but it won't
Hi Ralf
sorry for the late reply.
On Tue, Mar 27, 2012 at 22:29, Ralf Gommers wrote:
>
>
> On Wed, Mar 21, 2012 at 12:28 AM, Sandro Tosi wrote:
>>
>> Hello,
>> I've reported http://projects.scipy.org/numpy/ticket/2085 and Ralf
>> asked for bringing that up here: is anyone able to replicate the
>
