Nixpkgs: Package request: mu editor

[das-g]

Project description
A small, simple editor for beginner Python programmers. Written in Python and Qt5.

Metadata

• homepage URL: https://codewith.mu/
• source URL: https://github.com/mu-editor/mu
• license: gpl3+
• platforms: linux, darwin

[IDF31]

I think Mu can be a nice addition to the repos since it is a very nice tool for learning, and it can probably extend the use of NixOS. I'll try to package it.

[das-g]

I've started some work on this at https://github.com/das-g/nixpkgs/tree/mu-editor-init. (See diff to NixPkgs upstream.)

Currently on that branch, nix build -f . mu-editor fails with

builder for '/nix/store/ip56mljhgpk4g6s3m6ni68l7g3z7kmwx-pyqtchart-5.12.drv' failed with exit code 1; last 8 log lines:
  qmakePrePhase
  unpacking sources
  unpacking source archive /nix/store/vjlyz9ih2dya2wgrvjqbin1n8ghy5v8n-PyQtChart_gpl-5.12.tar.gz
  source root is PyQtChart_gpl-5.12
  setting SOURCE_DATE_EPOCH to timestamp 1549293609 of file PyQtChart_gpl-5.12/sip/QtChart/qxyseries.sip
  patching sources
  configuring
  Error: Unable to import PyQt5.QtCore. Make sure PyQt5 is installed.
cannot build derivation '/nix/store/9pa4wpj4mfv48vp51vig85lwx5z4flgn-mu-editor-1.1.0-alpha.2.drv': 1 dependencies couldn't be built
[0 built (1 failed), 0.0 MiB DL]
error: build of '/nix/store/9pa4wpj4mfv48vp51vig85lwx5z4flgn-mu-editor-1.1.0-alpha.2.drv' failed

I don't really know how to continue, so feel free to pick up from there or start fresh.

[jtojnar]

@das-g The Python libraries might need to go to propagatedBuildInputs.

[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.

[jtojnar]

Ugh.

On Sun, 31 May, 2020 at 21:25, stale[bot] [e-mail]
wrote:

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:

Search for maintainers and people that previously touched the
related code and @ mention them in a comment. Ask on the NixOS
Discourse. 3. Ask on the #nixos channel on
irc.freenode.net.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[das-g]

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.

still important to me :hugs:

[david-sawatzke]

I've continued @das-g work at https://github.com/david-sawatzke/nixpkgs/tree/mu-editor-init, with some copy-pasta for pyqtchart, but it seems the python qscintilla package contains PyQt5?

Found duplicated packages in closure for dependency 'PyQt5':
  PyQt5 5.14.2 (/nix/store/viyh6yf9gjs4a55kyainh3d3vash3k0w-python3.7-PyQt5-5.14.2/lib/python3.7/site-packages)
  PyQt5 5.14.2 (/nix/store/bs29a9abcdkrk9damk8dac9zniagvljh-python3.7-qscintilla-2.11.2/lib/python3.7/site-packages)

If that's fixed mu may even work, but I wouldn't count on it and it needs some cleanup work.
@lsix Is there a reason python3Packages.qscintilla-qt5 include PyQt5?

It seems the PyQt5 tree is mirrored with lndir for qscintilla-qt5

[lsix]

Sorry for the late reply.

I am not quite sure why this was done this way… I’ll need to check. I’ll let you know if I come with a cleverer approach.