Discussion:
napari-* packages in NEW
(too old to reply)
Guillem Jover
2024-10-18 12:50:02 UTC
Permalink
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
Scott Kitterman
2024-10-18 19:20:01 UTC
Permalink
Post by Guillem Jover
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

Loading...