* Package name    : nbdime
  Version         : 2.1.0
  Upstream Author : Jupyter Development Team <jupyter@googlegroups.com>
* URL             : https://nbdime.readthedocs.io/
* License         : BSD
  Programming Lang: Python
  Description     : Jupyter Notebook Diff and Merge tools

nbdime provides tools for diffing and merging of Jupyter Notebooks.
.
  * nbdiff - compare notebooks in a terminal-friendly way
  * nbmerge - three-way merge of notebooks with automatic conflict resolution
  * nbdiff-web - shows you a rich rendered diff of notebooks
  * nbmerge-web - gives you a web-based three-way merge tool for notebooks
  * nbshow - present a single notebook in a terminal-friendly way

Hi Joe,

Xuanteng (in CC) is working on packages jupyter-cache and myst-nb, both
of which make use of nbdime in their test suites. We were wondering if
you could provide us with a status update for nbdime?

We gave our own brief look, after upgrading nbdime to 4.0.1, but the
build fails because npm tries to download source-map-loader:

We've added it [1] and node-jupyterlab [2] to B-D as a stab in the dark,
but that didn't fix it. Unfortunately, we don't have experience with
node stuff in Debian.

Do you have an idea what's going on here? Otherwise I could ask on the
debian-js list.

Best,
Christian

[1] https://packages.debian.org/sid/node-source-map-loader
[2] https://packages.debian.org/sid/node-jupyterlab

Dear Jonas,
that the source package name should be prefixed with python-, to avoid
polluting the global namespace.

This package may be a bit different, as it will also be providing some
JavaScript packages (Provides: node-*).  Should its source package
also be prefixed with python- then?

Best wishes,

   Julian

Hi Christian,

Joe seems to have disappeared from this package, so I'll give it a
go.  It may well take me a few weeks - I'm also not very experienced
with JavaScript (either in Debian or outside it).

The current version is on salsa
(https://salsa.debian.org/python-team/packages/nbdime) but I'll work
locally until I've made some progress.

Best wishes,

   Julian

Hi Julian,
I would be interested in this package too. Was the attempt that you started on
Wed, 14 Aug 2024 successful?

Thanks,
Francesco

Hi Francesco,

I've made progress, but it's not yet building.  I haven't pushed my
work-in-progress to salsa.  I got delayed by various other packaging
things, I'm afraid.  I hope to be able to pick it up in a couple of
weeks.

Best wishes,

   Julian

block 975509 by 1111481
thanks

Here's an update.  My current WIP is available at:

https://salsa.debian.org/jdg/nbdime

It's a fork of the DPT version, but doesn't yet build because of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111481

Best wishes,

   Julian

Dear all,

With my relatively new job, I'm finding that I have almost no time to
do Debian packaging work.  I have been almost single-handedly
maintaining all of the Spyder-related packages and recently
contributed to a good number of Jupyter-related packages.  All of
these packages are (at least nominally) team-maintained in either the
Debian Python or Debian Science teams.

Please feel free to upload updates to these packages as needed without
asking me, though you are welcome to drop me an email if you want.

A few points worth noting (there are probably others that I've
forgotten at the moment):

* python-bytecode -> pydevd -> debugpy

  Each of these packages is used to build the next package in the
  list, by copying the code into it in place of the vendored code.  In
  particular, pydevd and debugpy are currently developed together,
  with pydevd being embedded in debugpy, so any updates to pydevd
  should be accompanied by a corresponding update to debugpy.

* pydevd and debugpy

  These are only developed upstream for the amd64 architecture.  As
  they make use of lots of the innards of Python (that I don't
  understand), there are multiple test failures on other archs that
  upstream will not address.  These are handled in
  debian/get_test_exclusions, which needs regular updating when the
  autobuilders or autopkgtests fail.

* spyder

  The autopkgtest setup is somewhat involved.  Experience has shown
  that this is needed, so it would be unwise to try to collapse it
  back to a single test.

* nbdime (ITP #975509)

  This ITP is currently blocked by node-rjsf.  I doubt that I'll have
  time to finish packaging it once node-rjsf is fixed, though.

Thanks for everyone's help in advance!

Best wishes,

   Julian