New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pythonPackages.qscintilla: enable for python3 #54834
Conversation
3a7267a
to
32656d8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer using a unified expression for both, Python 2 and 3. Can't we use pyqt5 for both?
meta = with pkgs.lib; { | ||
description = "A Python binding to QScintilla, Qt based text editing control"; | ||
license = licenses.lgpl21Plus; | ||
maintainers = with maintainers; [ danbst ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's not you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed.
I propagated the value of the current maintainer of the python2 only version. I’ll add myself shortly.
@dotlambda I used this approach (python2+pyqt4 / python3+pyqt5) to minimize the impact on existing derivations. I did not check yet what would be the impact of migrating the python2 binding to qt5 inside nixpkgs, but it will be a breaking change for people relying on it outside of nixpkgs. I’ll have a look ASAP at it and let you know what are the impacts within nixpkgs. |
If it's not possible to use pyqt5 everywhere, I suggest having 4 packages: |
I've tried to upgrade pyqt4 to pyqt5 (tortoisehg, uses pyqscintilla) and failed. So I agree, let's leave |
32656d8
to
f1e82b1
Compare
@dotlambda I have pushed an updated version, with both |
description = "A Python binding to QScintilla, Qt based text editing control"; | ||
license = licenses.lgpl21Plus; | ||
maintainers = with maintainers; [ lsix ]; | ||
platforms = platforms.unix; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason for specifying this? buildPythonPackage
will set an appropriate default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I re-used what was already present in pkgs/development/python-modules/qscintilla/default.nix
. I can leave it unspecified.
d49088e
to
eadab46
Compare
updates done. |
src = qscintillaCpp.src; | ||
format = "other"; | ||
|
||
buildInputs = [ lndir qscintillaCpp sip ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't sip
be propagated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sip is actually a binding generator tool. Is is not required at runtime. It generates artefacts. I am just not sure if it should go into nativeBuildInputs
of if buildInputs
is fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I opted for the nativeBuildInputs
approach
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still not sure about that since I don't know anything about cross-compiling Python packages.
eadab46
to
3323c0f
Compare
3323c0f
to
6c2bb2a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I didn't test it in any way though.
Cool! I'm looking forward to having it available on NixOS. #35669 Can we help in any way? |
Motivation for this change
I plan to add Qgis3 into nixpkgs, and for that qscintilla for python3 is required.
This work is somehow based on #38022
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)