On Wed, Feb 6, 2013 at 4:18 AM, Dag Sverre Seljebotn <
d.s.seljeb...@astro.uio.no> wrote:
> On 02/06/2013 08:41 AM, Charles R Harris wrote:
> >
> >
> > On Tue, Feb 5, 2013 at 11:50 PM, Jason Grout
> > mailto:jason-s...@creativetrax.com>>
> wrote:
> >
> > On 2/6/13 12:46 AM, Charles R Harris wr
On 6 February 2013 08:41, Charles R Harris wrote:
>
> More Python craziness
>
> In [6]: print None or 0
> 0
>
> In [7]: print 0 or None
> None
Just for clarifying this behaviour:
In [1]: print None or 0
0
In [2]: print 0 or None
None
In [3]: val = 0 or None
In [4]: print val
None
On Wed, 2013-02-06 at 10:18 +0100, Dag Sverre Seljebotn wrote:
> On 02/06/2013 08:41 AM, Charles R Harris wrote:
> >
> >
> > On Tue, Feb 5, 2013 at 11:50 PM, Jason Grout
> > mailto:jason-s...@creativetrax.com>> wrote:
> >
> > On 2/6/13 12:46 AM, Charles R Harris wrote:
> > > if we decide t
On 02/06/2013 08:41 AM, Charles R Harris wrote:
>
>
> On Tue, Feb 5, 2013 at 11:50 PM, Jason Grout
> mailto:jason-s...@creativetrax.com>> wrote:
>
> On 2/6/13 12:46 AM, Charles R Harris wrote:
> > if we decide to do so
>
> I should mention that we don't really depend on either behavior
On Tue, Feb 5, 2013 at 11:50 PM, Jason Grout wrote:
> On 2/6/13 12:46 AM, Charles R Harris wrote:
> > if we decide to do so
>
> I should mention that we don't really depend on either behavior (we
> probably should have a better doctest testing for an array of None
> values anyway), but we noticed
On 2/6/13 12:46 AM, Charles R Harris wrote:
> if we decide to do so
I should mention that we don't really depend on either behavior (we
probably should have a better doctest testing for an array of None
values anyway), but we noticed the oddity and thought we ought to
mention it. So it doesn't
On Tue, Feb 5, 2013 at 11:14 PM, Charles R Harris wrote:
>
>
> On Tue, Feb 5, 2013 at 10:23 PM, Jason Grout
> wrote:
>
>> On 2/4/13 12:04 AM, Ondřej Čertík wrote:
>> > Hi,
>> >
>> > Here are the last open issues for 1.7, there are 9 of them:
>> >
>> >
>> https://github.com/numpy/numpy/issues?mil
On Tue, Feb 5, 2013 at 10:23 PM, Jason Grout wrote:
> On 2/4/13 12:04 AM, Ondřej Čertík wrote:
> > Hi,
> >
> > Here are the last open issues for 1.7, there are 9 of them:
> >
> >
> https://github.com/numpy/numpy/issues?milestone=3&sort=updated&state=open
> >
>
> Here's something we noticed while w
On 2/4/13 12:04 AM, Ondřej Čertík wrote:
> Hi,
>
> Here are the last open issues for 1.7, there are 9 of them:
>
> https://github.com/numpy/numpy/issues?milestone=3&sort=updated&state=open
>
Here's something we noticed while working on getting 1.7rc1 into Sage
with one of our doctests. With nump
On Mon, Feb 4, 2013 at 7:04 AM, Ondřej Čertík wrote:
> Hi,
>
> Here are the last open issues for 1.7, there are 9 of them:
>
> https://github.com/numpy/numpy/issues?milestone=3&sort=updated&state=open
>
> >From these, 3 are very simple PRs that I just posted.
> Let's polish these, get them in.
>
>
Hi,
Here are the last open issues for 1.7, there are 9 of them:
https://github.com/numpy/numpy/issues?milestone=3&sort=updated&state=open
>From these, 3 are very simple PRs that I just posted.
Let's polish these, get them in.
I propose to release rc2 after that and if all is ok, do the final
re
11 matches
Mail list logo
