Where can I find the output of the tests on GitHub? I seem to be having
trouble locating them.
-Joe
Sent from my LG Optimus L70™
-- Original message--From: Jaime Fernández del RíoDate: Thu, Jan 21,
2016 02:17To: Discussion of Numerical Python;Subject:Re:
On Do, 2016-01-21 at 09:38 +, Robert Kern wrote:
> On Tue, Jan 19, 2016 at 5:35 PM, Sebastian Berg <
> sebast...@sipsolutions.net> wrote:
> >
> > On Di, 2016-01-19 at 16:28 +, G Young wrote:
> > > In rand range, it raises an exception if low >= high.
> > >
> > > I should also add that
On Thu, Jan 21, 2016 at 7:06 AM, Jaime Fernández del Río <
jaime.f...@gmail.com> wrote:
>
> There doesn't seem to be much of a consensus on the way to go, so leaving
things as they are and have been seems the wisest choice for now, thanks
for all the feedback. I will work with Greg on documenting
On Tue, Jan 19, 2016 at 5:35 PM, Sebastian Berg
wrote:
>
> On Di, 2016-01-19 at 16:28 +, G Young wrote:
> > In rand range, it raises an exception if low >= high.
> >
> > I should also add that AFAIK enforcing low >= high with floats is a
> > lot trickier than it is
Hi all,
Just as a heads up: Nathaniel and I wrote a draft PEP on binary linux
wheels that is now being discussed on distutils-sig, so you can check that
out and participate in the conversation if you're interested.
- PEP on python.org: https://www.python.org/dev/peps/pep-0513/
- PEP on github
I fixed the issue by checking if x.size > 2 before the calculation. An
error should never need to be raised at that point. The build passes
now and the results appear to be correct.
On Thu, Jan 21, 2016 at 2:17 AM, Jaime Fernández del Río
wrote:
> The tests are not passing,
Due to a mistake I made in my branch structure, I have replaced this
PR with #7090: https://github.com/numpy/numpy/pull/7090. All of the
changes and fixes so far are squashed into the new request.
-Joe
On Thu, Jan 21, 2016 at 1:51 AM, Joseph Fox-Rabinovitz
wrote:
>
On Thu, Jan 21, 2016 at 4:05 PM, Sebastian Berg
wrote:
> Hi all,
>
> should we try to set FutureWarnings to errors in dev tests? I am
> seriously annoyed by FutureWarnings getting lost all over for two
> reasons. First, it is hard to impossible to find even our own
Hi all,
should we try to set FutureWarnings to errors in dev tests? I am
seriously annoyed by FutureWarnings getting lost all over for two
reasons. First, it is hard to impossible to find even our own errors
for our own FutureWarning changes. Secondly, we currently would not
even see any
So it turns out that ndarray.data supports assignment at the Python
level, and what it does is just assign to the ->data field of the
ndarray object:
https://github.com/numpy/numpy/blob/master/numpy/core/src/multiarray/getset.c#L325
This kind of assignment been deprecated at the C level since
Warnings filters can be given a regex matching the warning text, I think?
On Jan 21, 2016 5:00 PM, "Sebastian Berg"
wrote:
> On Do, 2016-01-21 at 16:51 -0800, Nathaniel Smith wrote:
> > On Thu, Jan 21, 2016 at 4:44 PM, Sebastian Berg
> >
On Do, 2016-01-21 at 16:15 -0800, Nathaniel Smith wrote:
> On Thu, Jan 21, 2016 at 4:05 PM, Sebastian Berg
> wrote:
> > Hi all,
> >
> > should we try to set FutureWarnings to errors in dev tests? I am
> > seriously annoyed by FutureWarnings getting lost all over for
On Do, 2016-01-21 at 17:07 -0800, Nathaniel Smith wrote:
> Warnings filters can be given a regex matching the warning text, I
> think?
Doesn't cut it, because you need to set the warning to "always", so
then if you don't want to print it, you are stuck
I wrote a context manager + func
On Thu, Jan 21, 2016 at 4:44 PM, Sebastian Berg
wrote:
> On Do, 2016-01-21 at 16:15 -0800, Nathaniel Smith wrote:
>> On Thu, Jan 21, 2016 at 4:05 PM, Sebastian Berg
>> wrote:
>> > Hi all,
>> >
>> > should we try to set FutureWarnings to
On Do, 2016-01-21 at 16:51 -0800, Nathaniel Smith wrote:
> On Thu, Jan 21, 2016 at 4:44 PM, Sebastian Berg
> wrote:
> > On Do, 2016-01-21 at 16:15 -0800, Nathaniel Smith wrote:
> > > On Thu, Jan 21, 2016 at 4:05 PM, Sebastian Berg
> > >
Does this apply in any way to the .data attribute in scipy.sparse matrices?
I fiddle with that quite often!
On Fri, Jan 22, 2016 at 11:21 AM, Nathaniel Smith wrote:
> So it turns out that ndarray.data supports assignment at the Python
> level, and what it does is just assign to
On Jan 21, 2016 6:17 PM, "Juan Nunez-Iglesias" wrote:
>
> Does this apply in any way to the .data attribute in scipy.sparse
matrices?
Nope!
-n
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
I am pleased to announce version v0.7.0 of xarray, the project formerly
known as xray.
xarray is an open source project and Python package that aims to bring the
labeled data power of pandas to the physical sciences, by providing
N-dimensional variants of the core pandas data structures. These
On 1/21/2016 8:32 PM, Nathaniel Smith wrote:
> Does this apply in any way to the .data attribute in scipy.sparse
matrices?
Nope!
-n
How about the .data attribute of masked arrays? I'm guessing there may
be a decent amount of code that uses array.data to try to duck-type
ndarrays and
19 matches
Mail list logo