--===============0619029317806440624==
Content-Type: multipart/alternative; boundary=047d7b4725da84a27204eafa98d3

--047d7b4725da84a27204eafa98d3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=E2=80=9Clink against it=E2=80=9D? it=E2=80=99s no native library, so that =
wouldn=E2=80=99t even be
possible.

but no, we don=E2=80=99t hard-depend on it: it=E2=80=99s just possible to l=
oad a P=C3=A2t=C3=A9
plugin which depends on it, and embeds a =E2=80=9CIPython Qt Console=E2=80=
=9D widget into
Kate=E2=80=99s bottom Toolview area. Like this <http://i.imgur.com/LEnwhDp.=
png>


2013/11/12 Todd <toddrjen@gmail.com>

> On Mon, Nov 11, 2013 at 5:57 PM, Sven Brauch <svenbrauch@googlemail.com>w=
rote:
>
>> On Monday 11 November 2013 12:55:06 J. Pablo Mart=C3=ADn Cobos wrote:
>> > Because the pep8,
>> > pyflakes and parse syntax checker will report errors, because the
>> syntax is
>> > different in python 2 and python 3.
>> Okay, I looked a bit more and this is indeed a valid concern.
>>
>> The problem is that some of the plugins (pep8 and the ipython console, a=
t
>> least) call straight into the mentioned tools and do something with them=
,
>> and
>> the tools (e.g. ipython console) will be the version of the language kat=
e
>> was
>> linked against.
>>
>> For most of the tools the solution is imo easy: e.g. pep8 should just be
>> called as a program and the output should be parsed. It's very simple ..=
.
>> yes,
>> not as elegant, but who cares.
>>
>> For ipython however it's less obvious ... I'm not sure how the problem
>> could
>> be solved here. The only solution I found is based on creating a widget
>> and
>> then letting a new process draw into the widget, but that sort of sucks
>> (especially I'm not sure how portable it is). That's more work and more
>> bad
>> than just keeping the current situation, so not worth it imo.
>>
>> What I said earlier in the thread was referring only to what language
>> should
>> be available for writing the plugins, assuming plugins which are just
>> doing
>> stuff but not actually _importing python tools and using them in-process=
_.
>> For this issue, I'm not sure how to proceed. Possibly the "link against
>> both
>> libs" is indeed the best solution.
>>
>
> Why, exactly, do we need to link against iPython?  Why can't there just b=
e
> a console that launches iPython, or an html canvas that iPython writes to=
?
>
>
> _______________________________________________
> KWrite-Devel mailing list
> KWrite-Devel@kde.org
> https://mail.kde.org/mailman/listinfo/kwrite-devel
>
>

--047d7b4725da84a27204eafa98d3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style class=3D"markdown-here-wrapper" id=3D"markdown-=
here-wrapper-177967"><p style=3D"margin:1.2em 0px!important">=E2=80=9Clink =
against it=E2=80=9D? it=E2=80=99s no native library, so that wouldn=E2=80=
=99t even be possible.</p>
<p style=3D"margin:1.2em 0px!important">but no, we don=E2=80=99t hard-depen=
d on it: it=E2=80=99s just possible to load a P=C3=A2t=C3=A9 plugin which d=
epends on it, and embeds a =E2=80=9CIPython Qt Console=E2=80=9D widget into=
 Kate=E2=80=99s bottom Toolview area. Like <a href=3D"http://i.imgur.com/LE=
nwhDp.png">this</a></p>

</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2=
013/11/12 Todd <span dir=3D"ltr">&lt;<a href=3D"mailto:toddrjen@gmail.com" =
target=3D"_blank">toddrjen@gmail.com</a>&gt;</span><br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
 class=3D"im">On Mon, Nov 11, 2013 at 5:57 PM, Sven Brauch <span dir=3D"ltr=
">&lt;<a href=3D"mailto:svenbrauch@googlemail.com" target=3D"_blank">svenbr=
auch@googlemail.com</a>&gt;</span> wrote:<br>


</div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Monday 11 No=
vember 2013 12:55:06 J. Pablo Mart=C3=ADn Cobos wrote:<br>
&gt; Because the pep8,<br>
&gt; pyflakes and parse syntax checker will report errors, because the synt=
ax is<br>
&gt; different in python 2 and python 3.<br>
</div>Okay, I looked a bit more and this is indeed a valid concern.<br>
<br>
The problem is that some of the plugins (pep8 and the ipython console, at<b=
r>
least) call straight into the mentioned tools and do something with them, a=
nd<br>
the tools (e.g. ipython console) will be the version of the language kate w=
as<br>
linked against.<br>
<br>
For most of the tools the solution is imo easy: e.g. pep8 should just be<br=
>
called as a program and the output should be parsed. It&#39;s very simple .=
.. yes,<br>
not as elegant, but who cares.<br>
<br>
For ipython however it&#39;s less obvious ... I&#39;m not sure how the prob=
lem could<br>
be solved here. The only solution I found is based on creating a widget and=
<br>
then letting a new process draw into the widget, but that sort of sucks<br>
(especially I&#39;m not sure how portable it is). That&#39;s more work and =
more bad<br>
than just keeping the current situation, so not worth it imo.<br>
<br>
What I said earlier in the thread was referring only to what language shoul=
d<br>
be available for writing the plugins, assuming plugins which are just doing=
<br>
stuff but not actually _importing python tools and using them in-process_.<=
br>
For this issue, I&#39;m not sure how to proceed. Possibly the &quot;link ag=
ainst both<br>
libs&quot; is indeed the best solution.<br></blockquote><div><br></div></di=
v><div>Why, exactly, do we need to link against iPython?=C2=A0 Why can&#39;=
t there just be a console that launches iPython, or an html canvas that iPy=
thon writes to? =C2=A0 <br>


</div></div></div></div>
<br>_______________________________________________<br>
KWrite-Devel mailing list<br>
<a href=3D"mailto:KWrite-Devel@kde.org">KWrite-Devel@kde.org</a><br>
<a href=3D"https://mail.kde.org/mailman/listinfo/kwrite-devel" target=3D"_b=
lank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br>
<br></blockquote></div><br></div>

--047d7b4725da84a27204eafa98d3--

--===============0619029317806440624==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel

--===============0619029317806440624==--