Source: python-editor Version: 1.0.3-3 Severity: normal X-Debbugs-Cc: a.t.chadw...@gmail.com
Dear Maintainer, There is a new upstream version of this package available, version 1.0.4, released in Feb 2019. Please can it be packaged for Debian? Git: https://github.com/fmoo/python-editor PyPi: none? Interface: editor.edit() Author: fmoo However, and perhaps more notably, there is an unrelated package called “editor” in PyPi that does the same thing, but which turns out to be significantly more modern and more regularly maintained. Git: https://github.com/rec/editor PyPi: https://pypi.org/project/editor/ Interface: editor.editor() Author: rec (Tom Ritchford) I suspect that *this* is what many Python application devs will be using when they need to launch an editor, because they’ll be looking in PyPi first. I’ve made that mistake myself, thinking it’s a newer version of the Debian packaged “editor”, then got worried by the apparently huge version bump and changed interface before twigging that the two projects are unrelated. I suppose handling the name clash is really a policy matter for Debian’s Python team. Does it even matter? Do, or should, Debian builds of python packages generally have the same name as their PyPi equivalents? It’s pretty confusing if they don’t match up. Perhaps the solution would be to rename “python-editor” to “python-editor-fmoo” or similar, with sensible migration headers, and package a new “python-editor” whose name matches PyPi. Or some virtual package or Alternatives mechanism, maybe. Anyway, thanks for your consideration, whichever way this goes :) regards, Andrew
