Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16376 > unrolled thread
| Started by | Guillem Jover <guillem@debian.org> |
|---|---|
| First post | 2024-10-18 14:50 +0200 |
| Last post | 2024-10-18 21:20 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.maint.python
napari-* packages in NEW Guillem Jover <guillem@debian.org> - 2024-10-18 14:50 +0200
Re: napari-* packages in NEW Scott Kitterman <debian@kitterman.com> - 2024-10-18 21:20 +0200
| From | Guillem Jover <guillem@debian.org> |
|---|---|
| Date | 2024-10-18 14:50 +0200 |
| Subject | napari-* packages in NEW |
| Message-ID | <JyUAy-2s6U-13@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Date | 2024-10-18 21:20 +0200 |
| Message-ID | <Jz0FX-2vX9-7@gated-at.bofh.it> |
| In reply to | #16376 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web