Nixpkgs: Should Lektor be packaged as Python application?

[das-g]

Issue description

Lektor is currently packaged as a Python library, i.e. using buildPythonPackage. Its primary use seems to be as an application, so I wonder whether it should be packaged as one, either additionally to the library by using toPythonApplication or instead of it, using buildPythonApplication.

Steps to reproduce

Try to get started with Lektor. You'll notice you're more likely to use its executables than importing it in your own Python code.

Technical details

n/a

[FRidh]

Yes, it most likely should.

[das-g]

Do you think it should also be kept as a Python library? I guess when using the Lektor API from templates, one would still rely on the application, but maybe for developing Lektor plugins that's different and a Python library would be more appropriate?

[FRidh]

In that case it should be kept here, and one would use toPythonApplication in all-packages.nix.

[stale[bot]]

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
2. Ask on the NixOS Discourse.
3. Ask on the #nixos channel on irc.freenode.net.

[das-g]

Still important to me, but I think #85476 should be fixed before making Lektor "officially" available as an application.