Gael Varoquaux wrote:
>
> I was just wondering, could we ask Microsoft for some help here. A build
> bot, or a Windows 64 license... They are helping porting the SAGE project
> to windows, so they do have interest in getting open source scientific
> software working on windows.
>
Windows 64 is
On Sat, May 31, 2008 at 12:01:10PM +0900, David Cournapeau wrote:
> On Fri, May 30, 2008 at 8:35 PM, Hanni Ali <[EMAIL PROTECTED]> wrote:
> > I would also like to see a 64bit build for windows as well if possible.
> Unfortunately, this is difficult: windows 64 is not commonly available
> (I don'
On Saturday 07 June 2008 18:15:45 Charles R Harris wrote:
> On Sat, Jun 7, 2008 at 3:46 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
> > Folks,
> > Can anybody confirm that ? The tests look like they pass OK on my
> > machine...
>
> Yep,
>
> =
On Sun, Jun 8, 2008 at 6:49 PM, Nathan Bell <[EMAIL PROTECTED]> wrote:
> On Sun, Jun 8, 2008 at 6:15 AM, Alan McIntyre <[EMAIL PROTECTED]> wrote:
>> Right now there's "if __name__ == '__main__'" boilerplate at the end
>> of every test module; nose can find and run tests without that being
>> there.
On Sun, Jun 8, 2008 at 6:15 AM, Alan McIntyre <[EMAIL PROTECTED]> wrote:
> Right now there's "if __name__ == '__main__'" boilerplate at the end
> of every test module; nose can find and run tests without that being
> there. I wanted to get the list's take on removing that--it just
> means that if
All,
is there a reason why in some functions (min, max...) optional parameters are
parsed by position instead of by keyword ?
OK, let me give you an example:
#---
def amin(a, axis=None, out=None):
try:
amin = a.min
except AttributeError:
Folks,
I recently revamped some of the functions of numpy.ma to handle explicit
output parameters (eg, sum, std, var...). As a consequence, ticket #812
should be solved. Could anybody give a recent SVN (>=5259) a try and let me
know if I can close the ticket ?
Thanks a lot in advance.
P.
___
On Sun, Jun 8, 2008 at 7:02 AM, Vineet Jain (gmail) <[EMAIL PROTECTED]> wrote:
> Currently my code handles market returns and stocks as 1d arrays. While the
> function below expects a matrix. Is there an equivalent of the function
> below which works with numpy arrays?
>
> I'd like to do:
>
> beta,
Currently my code handles market returns and stocks as 1d arrays. While the
function below expects a matrix. Is there an equivalent of the function
below which works with numpy arrays?
I'd like to do:
beta, resids, rank, s = mp.linalg.lstsq(mrkt_1d_array, stock_1d_array)
If not, how do:
1. crea
la, 2008-05-31 kello 22:49 +0300, Pauli Virtanen kirjoitti:
> Hi,
>
> I'd like to adjust the way numpy.core.umath ufunc docstrings are defined
> to make them more easy to handle in the ongoing documentation marathon:
>
> - Remove the signature magic in ufunc_get_doc
> - Define ufunc docstrings in
Hi all,
Later this week (after finals are done ;) I'll be checking in some
changes to switch NumPy tests over to nose, and I just wanted to give
the list a heads up and see if there's any concerns, etc.
On Mon, Jun 2, 2008 at 11:04 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
> * is there a way to se
That fixes it, thanks! Apparently I forgot the -U when I tried to
update numscons via easy_install yesterday. ;)
On Sun, Jun 8, 2008 at 2:11 AM, David Cournapeau
<[EMAIL PROTECTED]> wrote:
> Alan McIntyre wrote:
>> I just updated my NumPy tree from svn trunk, and the SCons install now
>> fails wit
12 matches
Mail list logo
