Next steps towards 0.2

[Ludwig Hähne]

Hi,

the work on the branch for dividing the heapmonitor has been merged back
into the trunk and I've tried to improve the API and the docs of the new
or derived modules. With those changes applied, I've reached my
"personal milestones" for the next (minor) release of Pympler. Some
platform-specific quirks will probably arise with new modules but it
should be possible to fix these easily.

Therefore, I'd like to know what you consider critical for Pympler 0.2?
Some potential points from the list of issues and the ReleaseTasks wiki:

* Python 3 compliance (at least all tests should work with Python 3)
* extended Tests
* Unified documentation (library docs and tutorials)
* Rename asizeof => sizer?

Actually, I consider none of the above critical but YMMV.

I also don't want to rush into another release, it's just that it'll be
increasingly difficult for me to devote time to Pympler during the next
months and if there is anything else I can do to push Pympler forward,
I'd rather do it now ;)

Best, Ludwig

[Robert Schuppenies]

Ludwig Hähne wrote:
> Hi,
>
> the work on the branch for dividing the heapmonitor has been merged back
> into the trunk and I've tried to improve the API and the docs of the new
> or derived modules. With those changes applied, I've reached my
> "personal milestones" for the next (minor) release of Pympler. Some
> platform-specific quirks will probably arise with new modules but it
> should be possible to fix these easily.
>
> Therefore, I'd like to know what you consider critical for Pympler 0.2?
> Some potential points from the list of issues and the ReleaseTasks wiki:
>
> * Python 3 compliance (at least all tests should work with Python 3)
> * extended Tests
> * Unified documentation (library docs and tutorials)
> * Rename asizeof => sizer?

I would like to see all of them before the next release, and would
also like to work on at least some of them. Much to my regret my
thesis is high priority and I won't be able to address these issues
before March.

> Actually, I consider none of the above critical but YMMV.

Same here and under the perspective of "release early, release
often", a release with just the current changes may be valid as
well. Jean, what do you think?

> I also don't want to rush into another release, it's just that it'll be
> increasingly difficult for me to devote time to Pympler during the next
> months and if there is anything else I can do to push Pympler forward,
> I'd rather do it now ;)

Again, I would like to see the above mentioned things getting done,
but although I would like to work on those things it is probably
better to get them done sooner rather than later. Latter. Therefore
feel free to do whatever bugs you, I am sure other issues will come
up once these have been dealt with :)

cheers,
robert

[Jean Brouwers]

I haven't had a chance to look at the proposed changes in detail. But
my take would be to do these 4 topics in 2 steps. First add 3.0
support and the extended tests and perhaps release that as 0.2. Then,
unify the docs and do the renaming and that is 0.3+.

/Jean

[Ludwig Hähne]

Thanks for your feedback!

So Python 3.0 support and extended tests are considered mandatory and
the other items optional for Pympler 0.2. I will add this information to
the Issue tracker and start to look at the Python 3.0 test failures.

Ludwig