--===============6188545388514067815== Content-Type: multipart/alternative; boundary=001a11c24b0a1e74b804eae9d492 --001a11c24b0a1e74b804eae9d492 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2013/11/11 Sven Brauch > 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 a= nd > 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 b= ad > than just keeping the current situation, so not worth it imo. > why is it necessary to keep an ipython compatible with python 2? no other IDE/editor does it, they all embed just one (the python3 one). that includes sublime text 3, spyder, notepad++, eric. What I said earlier in the thread was referring only to what language shoul= d > be available for writing the plugins, assuming plugins which are just doi= ng > 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. > i don=E2=80=99t think that=E2=80=99s possible (c name/address space), and i= t will make our situation worse: not only will we have to continue to support both python versions of some plugins, but also (if we manage to do it at all), we=E2=80= =99ll have to support the linking of both, and we=E2=80=99ll have to depend on bo= th. and finally, i think using PyQt/PyKDE bindings to the same widgets from multiple places will create mayhem. --001a11c24b0a1e74b804eae9d492 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
2013= /11/11 Sven Brauch <svenbrauch@googlemail.com>
For ipython however it's less obvious ... I'm not sure how the prob= lem 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.

why is it necessary to keep an ipython compatible with python 2= ? no other IDE/editor does it, they all embed just one (the python3 one). t= hat includes sublime text 3, spyder, notepad++, eric.

What I said earlier in the thread was referring only to what language shoul= d
be available for writing the plugins, assuming plugins which are just doing=
stuff but not actually _importing python tools and using them in-process_.<= br> For this issue, I'm not sure how to proceed. Possibly the "link ag= ainst both
libs" is indeed the best solution.

i don=E2=80=99t think that=E2=80=99s possible (c name/address space), and = it will make our situation worse: not only will we have to continue to supp= ort both python versions of some plugins, but also (if we manage to do it a= t all), we=E2=80=99ll have to support the linking of both, and we=E2=80=99l= l have to depend on both. and finally, i think using PyQt/PyKDE bindings to= the same widgets from multiple places will create mayhem.
--001a11c24b0a1e74b804eae9d492-- --===============6188545388514067815== 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 --===============6188545388514067815==--