On Jul 7, 2014, at 7:28 AM, Sebastian Berg wrote:
> not sure that many use np.r_ or np.c_
I actually really like those ;-)
-Chris
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
If you are going to introduce this functionality, please don't call it
np.arr.
I agree, but..,
I would suggest calling it something like np.array_simple or
np.array_from_string, but the best choice IMO, would be
np.ndarray.from_string (a static constructor method).
Except the entire point of h
Hi,
* Francesc Alted [2014-07-07]:
[snip]
> There is also a handy command line and Python library for Blosc called
> Bloscpack (https://github.com/Blosc/bloscpack) that allows you to
> compress large binary datafiles on-disk.
For this list, you might be interested to know, that Bloscpack also
Indeed it was 1.2.4 the version just released and not 1.2.7. Sorry for
the typo!
Francesc
On 7/7/14, 8:20 PM, Francesc Alted wrote:
> =
> Announcing python-blosc 1.2.4
> =
>
> What is new?
>
>
> This is a maintenance release,
=
Announcing python-blosc 1.2.4
=
What is new?
This is a maintenance release, where included c-blosc sources have been
updated to 1.4.0. This adds support for non-Intel architectures, most
specially those not supporting unalign
On Mon, Jul 7, 2014 at 1:58 PM, Nathaniel Smith wrote:
> On Mon, Jul 7, 2014 at 3:28 PM, Sebastian Berg
> wrote:
> > On Mo, 2014-07-07 at 09:50 -0400, josef.p...@gmail.com wrote:
> >>
> >> On Mon, Jul 7, 2014 at 9:11 AM, Sebastian Berg
> >> wrote:
> >> On Mo, 2014-07-07 at 08:25 -0400,
On Mon, Jul 7, 2014 at 3:28 PM, Sebastian Berg
wrote:
> On Mo, 2014-07-07 at 09:50 -0400, josef.p...@gmail.com wrote:
>>
>> On Mon, Jul 7, 2014 at 9:11 AM, Sebastian Berg
>> wrote:
>> On Mo, 2014-07-07 at 08:25 -0400, Alan G Isaac wrote:
>> > On 7/7/2014 7:17 AM, Daπid wrote:
>>
On Mo, 2014-07-07 at 09:50 -0400, josef.p...@gmail.com wrote:
>
>
>
> On Mon, Jul 7, 2014 at 9:11 AM, Sebastian Berg
> wrote:
> On Mo, 2014-07-07 at 08:25 -0400, Alan G Isaac wrote:
> > On 7/7/2014 7:17 AM, Daπid wrote:
> > > How about a new one? np.matarray, for MATLAB
On Mon, Jul 7, 2014 at 9:11 AM, Sebastian Berg
wrote:
> On Mo, 2014-07-07 at 08:25 -0400, Alan G Isaac wrote:
> > On 7/7/2014 7:17 AM, Daπid wrote:
> > > How about a new one? np.matarray, for MATLAB array.
> >
> >
> > How about `str2arr` or even `build`, since teaching appears to be a
> focus.
>
On Mon, Jul 7, 2014 at 3:12 PM, Charles R Harris
wrote:
> On Mon, Jul 7, 2014 at 6:46 AM, Julian Taylor
> wrote:
>>
>> On Mon, Jul 7, 2014 at 2:34 PM, Charles R Harris
>> wrote:
>> > On Mon, Jul 7, 2014 at 2:02 AM, Julian Taylor
>> > wrote:
>> >>
>> >> On 07.07.2014 07:53, Charles R Harris wrot
On 7 Jul 2014 14:12, "Charles R Harris" wrote:.
>
> Yes, what I did was like one big cherry-pick. But I think we end up in
the same place with two divergent branches. I think git history is just a
string of changesets and each changeset has a hash. Same hash, same
changeset, and I think that was p
On Mon, Jul 7, 2014 at 6:46 AM, Julian Taylor wrote:
> On Mon, Jul 7, 2014 at 2:34 PM, Charles R Harris
> wrote:
> > On Mon, Jul 7, 2014 at 2:02 AM, Julian Taylor
> > wrote:
> >>
> >> On 07.07.2014 07:53, Charles R Harris wrote:
> >> > Just so. The fixes for 1.9.0b1 are now in that branch ready
On Mo, 2014-07-07 at 08:25 -0400, Alan G Isaac wrote:
> On 7/7/2014 7:17 AM, Daπid wrote:
> > How about a new one? np.matarray, for MATLAB array.
>
>
> How about `str2arr` or even `build`, since teaching appears to be a focus.
> Also, I agree '1 2 3' shd become 1d and '1 2 3;' shd become 2d.
> It
On Mon, Jul 7, 2014 at 2:34 PM, Charles R Harris
wrote:
> On Mon, Jul 7, 2014 at 2:02 AM, Julian Taylor
> wrote:
>>
>> On 07.07.2014 07:53, Charles R Harris wrote:
>> > Just so. The fixes for 1.9.0b1 are now in that branch ready for the next
>> > beta.
>> >
>>
>> how did you do that without a mer
On Mon, Jul 7, 2014 at 2:02 AM, Julian Taylor wrote:
> On 07.07.2014 07:53, Charles R Harris wrote:
> > Just so. The fixes for 1.9.0b1 are now in that branch ready for the next
> > beta.
> >
>
> how did you do that without a merge commit?
>
git branch tmp maintenance/1.9.x
git co tmp
git b
On 7/7/2014 7:17 AM, Daπid wrote:
> How about a new one? np.matarray, for MATLAB array.
How about `str2arr` or even `build`, since teaching appears to be a focus.
Also, I agree '1 2 3' shd become 1d and '1 2 3;' shd become 2d.
It seems unambiguous to allow '1 2 3;;' to be 3d, or even
'1 2;3 4;;5
On 7 July 2014 08:48, Jacco Hoekstra - LR wrote:
> How about using the old name np.mat() for this type of array creation?
How about a new one? np.matarray, for MATLAB array.
/David.
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://
Hi!
I gave appveyor a try this WE so as to build a minimalistic Python 3
project with a Cython extension. It works both with 32 and 64 bit
MSVC++ and can generate wheel packages. See:
https://github.com/ogrisel/python-appveyor-demo
However 2008 is not (yet) installed so it cannot be used for
On 07.07.2014 10:02, Julian Taylor wrote:
> On 07.07.2014 07:53, Charles R Harris wrote:
>> Just so. The fixes for 1.9.0b1 are now in that branch ready for the next
>> beta.
>>
>
> how did you do that without a merge commit?
> however you did it you have git has lost ancestry which is not so nice
On 07.07.2014 07:53, Charles R Harris wrote:
> Just so. The fixes for 1.9.0b1 are now in that branch ready for the next
> beta.
>
how did you do that without a merge commit?
however you did it you have git has lost ancestry which is not so nice
for backporting.
If there are no objections I'd like
20 matches
Mail list logo
