[ANN] bloscpack v0.1.0

[Valentin Haenel]

Dear all,

just in time for my vacation, I released bloscpack v0.1.0 -- from Geneva
Airport:

https://github.com/esc/bloscpack/tree/v0.1.0

Both the changelog and the TODO are embedded in the README.rst

I have hopefully managed to gather all the TODOs that were raised during
the stringent review process, thanks again for all the feedback! I
really apprecaite it!

V-

[Francesc Alted]

On 6/14/12 7:34 PM, Valentin Haenel wrote:
> Dear all,
>
> just in time for my vacation, I released bloscpack v0.1.0 -- from Geneva
> Airport:
>
> https://github.com/esc/bloscpack/tree/v0.1.0
>
> Both the changelog and the TODO are embedded in the README.rst

Looks good! Everything runs fine, except for the extended tests that
still hugs lots of memory (good time for submitting a PR :)

>
> I have hopefully managed to gather all the TODOs that were raised during
> the stringent review process, thanks again for all the feedback! I
> really apprecaite it!

As we are going to meet physically soon, it would be nice to discuss
with you about possible roadmaps for extending bloscpack.

Enjoy your holidays!

--
Francesc Alted

[Valentin Haenel]

Hi,

* Francesc Alted <fal...@gmail.com> [2012-06-14]:

> On 6/14/12 7:34 PM, Valentin Haenel wrote:
> >just in time for my vacation, I released bloscpack v0.1.0 -- from Geneva
> >Airport:
> >
> >https://github.com/esc/bloscpack/tree/v0.1.0
> >
> >Both the changelog and the TODO are embedded in the README.rst
>
> Looks good! Everything runs fine, except for the extended tests
> that still hugs lots of memory (good time for submitting a PR :)

Yeah I kinda messed that one up. I put it in the changelog, not the
TODO, so it kinda went under, sorry:

https://github.com/esc/bloscpack/commit/e0569afc0450ed7b0568e41775e67e969db5d24e

:/

But, it should be easy enough to split the tests into some, that run for
some time, but are nice to memory and some that run for some time and
are heavy on memory.

> >I have hopefully managed to gather all the TODOs that were raised during
> >the stringent review process, thanks again for all the feedback! I
> >really apprecaite it!

> As we are going to meet physically soon, it would be nice to discuss
> with you about possible roadmaps for extending bloscpack.

Yes, absolutely.

> Enjoy your holidays!

Thanks!

V- (now boarding)

[Valentin Haenel]

Hey,

* Valentin Haenel <valenti...@gmx.de> [2012-06-14]:

> * Francesc Alted <fal...@gmail.com> [2012-06-14]:
> > On 6/14/12 7:34 PM, Valentin Haenel wrote:
> > >just in time for my vacation, I released bloscpack v0.1.0 -- from Geneva
> > >Airport:
> > >
> > >https://github.com/esc/bloscpack/tree/v0.1.0
> > >
> > >Both the changelog and the TODO are embedded in the README.rst
> >
> > Looks good! Everything runs fine, except for the extended tests
> > that still hugs lots of memory (good time for submitting a PR :)
>
> Yeah I kinda messed that one up. I put it in the changelog, not the
> TODO, so it kinda went under, sorry:
>
> https://github.com/esc/bloscpack/commit/e0569afc0450ed7b0568e41775e67e969db5d24e
>
> :/
>
> But, it should be easy enough to split the tests into some, that run for
> some time, but are nice to memory and some that run for some time and
> are heavy on memory.

I have fixed this issue in master a few days ago. There are now two
additional tests that do not run by default, a 'hard' and an 'extreme'
one. They can be run as described here:

https://github.com/esc/bloscpack#∴-testing

Let me know if it's better now, thanks.

V-

[Francesc Alted]

Yep, much better. I see now memory peaks of just 72 MB for the hard
one, which is much less than before. I did not run the 'extreme' as it
should consume a scary 6 GB (omg!). But at leat this is documented now ;)

--
Francesc Alted

[Valentin Haenel]

Hi,

* Francesc Alted <fal...@gmail.com> [2012-07-15]:

> On 7/10/12 7:41 PM, Valentin Haenel wrote:
> >* Valentin Haenel <valenti...@gmx.de> [2012-06-14]:
> >>* Francesc Alted <fal...@gmail.com> [2012-06-14]:
> >>>On 6/14/12 7:34 PM, Valentin Haenel wrote:
> >>>>just in time for my vacation, I released bloscpack v0.1.0 -- from Geneva
> >>>>Airport:
> >>>>
> >>>>https://github.com/esc/bloscpack/tree/v0.1.0
> >>>>
> >>>>Both the changelog and the TODO are embedded in the README.rst
> >>>Looks good! Everything runs fine, except for the extended tests
> >>>that still hugs lots of memory (good time for submitting a PR :)
> >>Yeah I kinda messed that one up. I put it in the changelog, not the
> >>TODO, so it kinda went under, sorry:
> >>
> >>https://github.com/esc/bloscpack/commit/e0569afc0450ed7b0568e41775e67e969db5d24e
> >>

> >>But, it should be easy enough to split the tests into some, that run for
> >>some time, but are nice to memory and some that run for some time and
> >>are heavy on memory.
> >I have fixed this issue in master a few days ago. There are now two
> >additional tests that do not run by default, a 'hard' and an 'extreme'
> >one. They can be run as described here:
> >
> >https://github.com/esc/bloscpack#∴-testing
> >
> >Let me know if it's better now, thanks.
>
> Yep, much better. I see now memory peaks of just 72 MB for the hard
> one, which is much less than before.

Great! I am happy it works. FYI: I have just released the first
maintenance release of v0.1.x:

https://github.com/esc/bloscpack/tree/v0.1.1

> I did not run the 'extreme' as
> it should consume a scary 6 GB (omg!). But at leat this is
> documented now ;)

My desktop machine has exactly 6GB and it will not run that suite. :)

V-