[prev in list] [next in list] [prev in thread] [next in thread]
List: nix-dev
Subject: Re: [Nix-dev] PyQt and packaging python-qscintilla
From: Daniel Hlynskyi <abcz2.uprola () gmail ! com>
Date: 2015-07-22 18:48:25
Message-ID: CANZg+ye1PfVjBb=FkydjO9j9Fd305d8=JW_12o+41-k8MZZ=qQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Ah, the problem was fixed with lndir. That is basically way 3), but does
not use extra space on disk
mkdir -p $out
lndir ${pkgs.pyqt4} $out
2015-07-19 17:36 GMT+00:00 Daniel Hlynskyi <abcz2.uprola@gmail.com>:
> For PyQt there is a library python-qscintilla, which is Python binding to
> qscintilla editor control. PyQt is already packaged here [1].
>
> The problem with packaging python-qscintilla is: it wants to be in PyQt
> directory. So we can do
>
> import PyQt4
> import PyQt4.Qsci
>
> Now [2] I have three choices how to resume packaging :
>
> 1) ask if someone knows hot to trick Python and sip where the Qsci.so is
> located (python-qscintilla creates .so file, not .py). I've tried to put
> Qsci.so into PYTHONPATH but Python doesn't load .so files (or I didn't
> figure out how it works)
>
> 2) modify PyQt, so it has optional argument qscintilla:
>
> pyqt4 = { pkgs, qscintilla ? null, ..} : ...
>
> and refer to python-qscintilla as
>
> [ pkgs.python27Packages.pyqt4 { pkgs = self.pkgs, qscintilla =
> pkgs.qscintilla } ]
>
> (alternative: implement it as override in nixpkgs)
>
> 3) create own build of PyQt in python-qscintilla. This will not change
> existing PyQt expression
>
> Which is better to continue and how to do it best?
>
> [1]
> https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/python-modules/pyqt/
> [2] https://gist.github.com/danbst/e4199acb6b4dee9cdfbf
>
[Attachment #5 (text/html)]
<div dir="ltr">Ah, the problem was fixed with lndir. That is basically way 3), but \
does not use extra space on disk<br><br>mkdir -p $out<br>lndir ${pkgs.pyqt4} \
$out<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-07-19 17:36 \
GMT+00:00 Daniel Hlynskyi <span dir="ltr"><<a href="mailto:abcz2.uprola@gmail.com" \
target="_blank">abcz2.uprola@gmail.com</a>></span>:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">For PyQt there is a library python-qscintilla, \
which is Python binding to qscintilla editor control. PyQt is already packaged here \
[1].<br><br>The problem with packaging python-qscintilla is: it wants to be in PyQt \
directory. So we can do<br><br> import PyQt4<br> import PyQt4.Qsci<br><br>Now \
[2] I have three choices how to resume packaging :<br><br>1) ask if someone knows \
hot to trick Python and sip where the Qsci.so is located (python-qscintilla creates \
.so file, not .py). I've tried to put Qsci.so into PYTHONPATH but Python \
doesn't load .so files (or I didn't figure out how it works)<br><br>2) modify \
PyQt, so it has optional argument qscintilla:<br><br> pyqt4 = { pkgs, qscintilla \
? null, ..} : ...<br><br>and refer to python-qscintilla as <br><br> [ \
pkgs.python27Packages.pyqt4 { pkgs = self.pkgs, qscintilla = pkgs.qscintilla } \
]<br><br>(alternative: implement it as override in nixpkgs)<br><br>3) create own \
build of PyQt in python-qscintilla. This will not change existing PyQt \
expression<br><br>Which is better to continue and how to do it best?<br><br>[1] <a \
href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/python-modules/pyqt/" \
target="_blank">https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/python-modules/pyqt/</a><br>[2] \
<a href="https://gist.github.com/danbst/e4199acb6b4dee9cdfbf" \
target="_blank">https://gist.github.com/danbst/e4199acb6b4dee9cdfbf</a></div> \
</blockquote></div><br></div>
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic