* Package name    : python-psleak
  Version         : 0.1.5
  Upstream Contact: Giampaolo Rodola <g.rodola@gmail.com>
* URL             : https://github.com/giampaolo/psleak
* License         : BSD 3-Clause License
  Programming Lang: Python, C
  Description     : Test framework to detect memory and resource leaks in Python C extensions.

A testing framework for detecting memory leaks and unclosed resources created by Python functions,
particularly those implemented in C extensions.

This package is necessary for upgrading python-psutil. This used to be
part of the psutil project, but it was splitoff in its own project.
I do believe, either the Python team or the OpenStack team could be a
good place for this.
I will need a sponsor.

why is a team that do not maintain psutil "a good place" to maintain
this strong dependency of psutil?

Since it's a dependency to multiple top level projects of the OpenStack
ecosystem, there is an interest for Debian OpenStack maintainer to maintain
it.

And since the psutil library is, as it looks like, under a single debian
maintainer (you), it felt strange for a random (me) to just pin another
dependency on them.
Of course, it makes more sense for the psutil maintainer to maintain this
strong psutil dependency.

I wouldn't mind taking over python-psleak and maintaining it along
side psutil, but I also don't want to dismiss the work you've already
done.

I could redo the packaging from scratch (to avoid copyright
complications), but that would essentially mean your time would have
been wasted.

Id like to hear your thoughts on this

Thanks,

I want to move forward with packaging a newer psutil, which require
psleak. If i dont hear back from you by May 18th, i'll proceed with
packaging psleak from scratch and uploading to debian unstable.

thanks,
Sandro