2011/9/20 Stéfan van der Walt
> On Tue, Sep 20, 2011 at 12:43 AM, Robert Kern
> wrote:
> > If the array is short in a dimension, it gets implicitly continued
> > with Falses. You can see this in one dimension:
>
> [...]
>
> > I honestly don't know if this is documented or tested anywhere or even
On Wed, Sep 21, 2011 at 17:29, Sandro Tosi wrote:
> On Wed, Sep 21, 2011 at 23:20, Robert Kern wrote:
>> On Wed, Sep 21, 2011 at 16:15, Filipe Pires Alvarenga Fernandes
>> wrote:
>>> Don't know about about Debian, but this works OK for RPM distros:
>>>
>>> PYTHONPATH="%{buildroot}%{py_sitedir}"
On Wed, Sep 21, 2011 at 23:20, Robert Kern wrote:
> On Wed, Sep 21, 2011 at 16:15, Filipe Pires Alvarenga Fernandes
> wrote:
>> Don't know about about Debian, but this works OK for RPM distros:
>>
>> PYTHONPATH="%{buildroot}%{py_sitedir}" %{__python} -c \
>> "im
On Wed, Sep 21, 2011 at 23:15, Filipe Pires Alvarenga Fernandes
wrote:
> Don't know about about Debian, but this works OK for RPM distros:
>
> PYTHONPATH="%{buildroot}%{py_sitedir}" %{__python} -c \
> "import pkg_resources, numpy ;
> numpy.test()"
>
> The only t
On Wed, Sep 21, 2011 at 16:15, Filipe Pires Alvarenga Fernandes
wrote:
> Don't know about about Debian, but this works OK for RPM distros:
>
> PYTHONPATH="%{buildroot}%{py_sitedir}" %{__python} -c \
> "import pkg_resources, numpy ;
> numpy.test()"
>
> The only t
Don't know about about Debian, but this works OK for RPM distros:
PYTHONPATH="%{buildroot}%{py_sitedir}" %{__python} -c \
"import pkg_resources, numpy ; numpy.test()"
The only thing you are missing is the "import pkg_resources", let me
know if that works for yo
On Wed, Sep 21, 2011 at 15:56, Sandro Tosi wrote:
> Hello,
> at (Debian) package build time, it would be really important to run
> the tests suite, but I'm not getting how to do that.
The way that nosetests imports packages in order to navigate to find
test files is a bit wonky. It doesn't respec
Hello,
at (Debian) package build time, it would be really important to run
the tests suite, but I'm not getting how to do that.
The simple approach doesn't work:
>>>
$ PYTHONPATH=build/lib.linux-x86_64-2.6 python -c "import numpy; numpy.test()"
Traceback (most recent call last):
File "", line 1
I have installed numpy with my own ATLAS, but trying to install PyMC,
it can't find the ATLAS libs. I also have an older package that
formerly installed but no longer does. I'm being a bit lazy, but am I
missing something? Briefly checking, it looks like the
conventions/assumptions for site.cfg in
Yet again, the issue of distributing scientific Python software was
raised, this time on the mpi4py mailing list. Since that wasn't really
the right forum, and we weren't really sure what was the right forum, we
started a blog instead.
The idea is to get a diverse set of people describe their e
10 matches
Mail list logo
