• napari-* packages in NEW

    From Guillem Jover@21:1/5 to All on Fri Oct 18 14:50:02 2024
    Hi!

    These seem to be python modules only packages, but their source package
    names are not currently namespaced. Given that they have not yet passed
    NEW, please namespace them with python- to avoid taking on the global namespace, so that we do not "prevent" packaging something that for
    example installs a command with the same name (or having to end up using
    a non-obvious one for that, or requiring a future rename), so that it's
    easier to see what it is about when doing archive-wide analysis from
    Sources, or dd-lists, or even reading changelogs via stuff like apt-listchanges, like the rest of the language specific teams are
    doing. :)

    Thanks,
    Guillem

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Scott Kitterman@21:1/5 to Guillem Jover on Fri Oct 18 21:20:01 2024
    On October 18, 2024 12:46:17 PM UTC, Guillem Jover <guillem@debian.org> wrote: >Hi!

    These seem to be python modules only packages, but their source package
    names are not currently namespaced. Given that they have not yet passed
    NEW, please namespace them with python- to avoid taking on the global >namespace, so that we do not "prevent" packaging something that for
    example installs a command with the same name (or having to end up using
    a non-obvious one for that, or requiring a future rename), so that it's >easier to see what it is about when doing archive-wide analysis from
    Sources, or dd-lists, or even reading changelogs via stuff like >apt-listchanges, like the rest of the language specific teams are
    doing. :)

    It looks to me like this is a pretty unique name to this project. Does this concern really apply to this case

    https://napari.org/stable/

    Scott K

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)