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
qt5.qtbase: python2 -> python3 #75916
Conversation
Does this not mean this is broken? Future won't be included, and this is native. |
No, python2 added a |
Oh, |
That is above my pay grade, I don't know! :o |
The only python reference in qtbase's dev output is a python script which imports print from __future__ (mkspecs/features/uikit/devices.py). It's not clear whether it depends on python or it just provides a python script. But I believe it's still good to have in buildInputs so it has a proper shebang. Co-authored-by: worldofpeace <worldofpeace@protonmail.ch>
5256de1
to
ef96a4a
Compare
Ahh nixpkgs, we're really blessed in needless pings sometimes. |
We should surely wait for ofborg to test this one now :) |
in python3, EDIT: what i said isn't technically true, but the most common use case it to allow for python2 to run python3 code. |
The only python reference in qtbase's dev output is a python script
which imports print from future (mkspecs/features/uikit/devices.py)
so I guess it is good enough.
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @