Bug#1009970: retitle 1009970 to ITP: memray -- Python memory profiler

[Julian Gilbey <jdg@debian.org>]

On Tue, Jan 02, 2024 at 11:10:03PM +0100, Gürkan Myczko wrote:
> On 31.12.2023 18:16, Julian Gilbey wrote:
> > On Mon, Nov 06, 2023 at 04:27:35PM +0100, G��rkan Myczko wrote:
> > > retitle 1009970 ITP: memray -- Python memory profiler
> > > thanks
> > 
> > Hi G��rkan (and unfortunately your name got corrupted in your email
> > message),
> 
> Hi Julian
> 
> (i failed to find you on irc, you're maybe not using it?)

Hi!  No, I don't tend to use irc.

> > Have you made any progress on this?
> 
> Yes and no, here's the short summary:
> https://sid.ethz.ch/debian/memray/
> 1.10.0 seems to build and work?
> 1.11.0 doesn't seem to build.

Oh :(  Could it perhaps be to do with versions of dependencies?  (I
haven't looked at your packages, so I'm just guessing here.)

> >  It is now used in the new
> > upstream version of dask.distributed, which we need to use to fix some
> > Python 3.12 issues.  (I see that memray does depend on some other
> > stuff which has either not been packaged or needs to be updated, so
> > it's not a completely trivial task.)
> 
> You know more than I. Please go ahead if you have better packaging of it,
> take over the ITP.

I don't have the capacity to do it, unfortunately; it also turned out
that I can just skip those tests with dask.distributed.  If you are
able to package memray, then we can re-enable those tests.

Thanks!

   Julian