Bug#798009: ITP: python-editor -- programmatically open an editor, capture the result

[Guido Günther <agx@sigxcpu.org>]

Hi,
On Fri, Sep 04, 2015 at 02:30:26PM +0200, Thomas Goirand wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Thomas Goirand <zigo@debian.org>
> 
> * Package name    : python-editor
>   Version         : 0.4
>   Upstream Author : Peter Ruibal <ruibalp@gmail.com>
> * URL             : https://github.com/fmoo/python-editor
> * License         : Apache-2.0
>   Programming Lang: Python
>   Description     : programmatically open an editor, capture the result
> 
>  python-editor is a library that provides the editor module for
>  programmatically interfacing with your system's $EDITOR. The user can then
>  enter a commit message for example.
>  .
>  Editor first looks for the ${EDITOR} environment variable.  If set, it uses
>  the value as-is, without fallbacks. If no $EDITOR is set, editor will search
>  through a list of known editors, and use the first one that exists on the
>  system. For example, on Linux, editor will look for the following editors in
>  order:
>   * vim
>   * emacs
>   * nano
>  .
>  When calling the edit() function, editor will open the editor in a
>  subprocess, inheriting the parent process's stdin, stdout

Given that this is on Debian should it take sensible-editor into account
form the start?
Cheers,
 -- Guido