e need help with the bindings!
>
> I’d really like to revive my IPython console in Kate :D
>
> Best, Philipp
>
> Shaheed Haque schrieb am Sa., 13. Jan. 2018 um
> 19:06 Uhr:
>
>> Thanks to some upstream fixes, I have the cppyy-based bindings for KF5
>> and also
Hi Luca,
On 15 January 2018 at 08:24, Luca Beltrame wrote:
> Il giorno Sat, 13 Jan 2018 18:05:45 +
> Shaheed Haque ha scritto:
>
> Hello Shaheed,
>
> >1. The packaging has advanced to the point where I think ECM-based
> >framework-by-framework bindings a
Thanks to some upstream fixes, I have the cppyy-based bindings for KF5 and
also Qt5 (see below) showing signs of life. Notes:
1. The packaging has advanced to the point where I think ECM-based
framework-by-framework bindings are a real possibility, with both Py2 and
Py3. AFAICS, this add
Hi all,
I just realised that the Python binding effort is not setting the default
visibility for symbols using the -fvisibility=xxx option when processing
the header files [1]. Of course I can see the export macros set by the
likes of attica_exports.h, but I don't see where the compiler default is
I have made an attempt to get roughly all the bindings I was previously
attempting with SIP to be (a) generated and (b) built.
As of now, we have:
- Customisations with a diffstat that reads "21 files changed, 20
insertions(+), 48 deletions(-)".
- All but 5-6 of the formal tier 1, 2 and 3 framewo
Philipp,
On 5 November 2017 at 14:48, Philipp A. wrote:
> Hi Shaheed, Chris,
>
> Shaheed Haque schrieb am Sa., 4. Nov. 2017 um
> 18:35 Uhr:
>
>> FWIW, I already tried that (types.ModuleType is itself a perfectly
>> subclassable class!) […]
>>
>> Now, n
e on to the TODOs listed
earlier.
On 4 November 2017 at 17:35, Shaheed Haque wrote:
> Wim, Philipp,
>
> On 4 November 2017 at 16:45, Philipp A. wrote:
>> Hi Wim!
>>
>>> So now I have a (C++) namespace 'A' that bears no relationship to anything
>>
Wim, Philipp,
On 4 November 2017 at 16:45, Philipp A. wrote:
> Hi Wim!
>
>> So now I have a (C++) namespace 'A' that bears no relationship to anything
>> to do with the file system or any type of Python packaging: it exists only
>> in memory for the duration of the python session.
>
>
> Yeah, coo
Hi Philipp,
On 3 November 2017 at 14:09, Philipp A. wrote:
> Hi Shaheed,
>
> Shaheed Haque schrieb am Fr., 3. Nov. 2017 um 14:16
> Uhr:
>>
>> Philipp,
>>
>> - my overall understanding of this technique is that it may end up
>> being fragile, especia
Philipp,
On 3 November 2017 at 12:52, Philipp A. wrote:
> Hi Shaheed,
>
> Thank you so much for all your work!
>
>> a framework-by-framework integration of the binding generation logic (as
>> previously pioneered by Steve) probably cannot work in general because there
>> are cases where multiple
Albert,
On 2 November 2017 at 21:43, Albert Astals Cid wrote:
> El dijous, 2 de novembre de 2017, a les 18:22:38 CET, Shaheed Haque va
> escriure:
>> A progress update...
>>
>> On 24 October 2017 at 13:05, Shaheed Haque wrote:
>> > Hi all,
>> >
>
A progress update...
On 24 October 2017 at 13:05, Shaheed Haque wrote:
> Hi all,
>
> I have a preliminary version of the Cppyy bindings generator CMake
> support available here:
>
>
> https://bitbucket.org/wlav/cppyy-backend/pull-requests/6/an-interim-experimen
H_DIR some_framework_INCLUDE_DIRS
H_FILES )
Thanks, Shaheed
On 16 October 2017 at 16:16, Shaheed Haque wrote:
> As promised, here is an interim update on the investigation into the
> use of cppyy-based bindings for KF5 (and more...) instead of SIP-based
> bindings.
>
> Th
of
effort, I am hopeful that we can get to some REALLY
easy-to-develop-and-maintain bindings.
[1] There is a bug with the binding producing stuff for private definitions.
[2] There is a bug with missing globals.
On 7 September 2017 at 10:23, Shaheed Haque wrote:
> [ Copying in kde-frameworks-
Hi Luca,
On 5 September 2017 at 23:12, Luca Beltrame wrote:
> Il giorno Tue, 5 Sep 2017 22:12:26 +0100
> Shaheed Haque ha scritto:
>
> Hello Shaheed,
>
> first of all, thanks for continuing work on the bindings!
>
>> https://github.com/ShaheedHaque/extra-cmake-modul
[ Copying in kde-frameworks-devel as suggested ]
On 5 September 2017 at 22:12, Shaheed Haque wrote:
> A lot of progress has been made in the last 18 months or so:
>
> THE TOOLING
> ===
>
> We have:
>
> - A pretty powerful KDE-independent automatic bindi
/TemplateParsermod.sip
tmp/ThreadWeaver/ThreadWeaver/ThreadWeavermod.sip
tmp/wtf/wtfmod.sip
tmp/XsltKde/XsltKdemod.sip
On 26 March 2016 at 22:30, Shaheed Haque wrote:
> Hi all,
>
> I've given up on trying to get the twine2 PyKDE bindings generator
> working [1] because not on
On 1 September 2017 at 12:39, Jan Grulich wrote:
> Hi,
>
> On pátek 1. září 2017 12:46:54 CEST Shaheed Haque wrote:
>> Hi all,
>>
>> The Python bindings effort recently ran into the need for
>> https://phabricator.kde.org/D5185 to prevent clashes between Qt
Hi all,
The Python bindings effort recently ran into the need for
https://phabricator.kde.org/D5185 to prevent clashes between Qt's use
of "signals" and libnm via networkmanager-qt's ipconfig.h. However, it
seems to me that the fix is incomplete in current Git master as there
are at least two othe
Exactly.
On 23 May 2017 at 20:40, Albert Astals Cid wrote:
> El dimarts, 23 de maig de 2017, a les 2:04:54 CEST, Aleix Pol va escriure:
>> On Mon, May 22, 2017 at 7:54 PM, Shaheed Haque wrote:
>> > On 21 May 2017 at 22:27, Aleix Pol wrote:
>> >> On Sat, May 20,
> I don't understand what you're trying to do.
Me neither :-). Let me take a step back to try to provide some
context. It is my assessment that part of the problem with the
maintenance of bindings has been the lack of automation both in
support of the initial development of the bindings, and then
On 21 May 2017 at 22:27, Aleix Pol wrote:
> On Sat, May 20, 2017 at 7:41 PM, Shaheed Haque wrote:
>> Actually, there is one thing about "target CMake"-based KF5 that I
>> don't quite understand: is there a way to get to the C++ compile flags
>> needed from C
on targets I have tried.
Perhaps these are only set if somehow the compiler name etc. is specified?
Thanks, Shaheed
On 18 May 2017 at 18:04, Shaheed Haque wrote:
> Hi,
>
> On 18 May 2017 at 12:51, Andreas Hartmetz wrote:
>> On Samstag, 13. Mai 2017 23:48:33 CEST Shaheed Ha
Hi,
On 18 May 2017 at 12:51, Andreas Hartmetz wrote:
> On Samstag, 13. Mai 2017 23:48:33 CEST Shaheed Haque wrote:
>> Hi,
>>
>> On 13 May 2017 at 22:04, Sven Brauch wrote:
>> > Hi,
>> >
>> > On 05/13/2017 06:06 PM, Shaheed Haque wrote:
Hi,
On 13 May 2017 at 22:04, Sven Brauch wrote:
> Hi,
>
> On 05/13/2017 06:06 PM, Shaheed Haque wrote:
>> The printed output shows that the variable KF5KIO_INCLUDE_DIRS is not
>> set. In poking around, I see references to a (new-to-me) target-based
>> system, and
Hi,
I'm a bit confused as to how the current KF5 CMake support works. I
have a small fragment that looks like this:
find_package(KF5KIO REQUIRED)
message(STATUS "KF5KIO includes = ${KF5KIO_INCLUDE_DIRS}")
The printed output shows that the variable KF5KIO_INCLUDE_DIRS is not
set. In pokin
I automated manual step #3 and the related difficulty over traversing
the fanout (see [1] for the gory details). That in turn enabled the
CLI wrapper around the SIP compiler to be reworked so now we can
trivially run the tooling over all of KF5 to see where all the errors
are. The steps are in a pr
Hi all,
This is a quick update on the Py*5 bindings generation attempt, and
specifically on PyKF5. The binding generator with the PyKF5-specific
rules can now [1] generate a set of SIP files [2] which require just a
couple of simple hand edits [3] to process KDECoreAddons with no
syntax errors, bu
I'm fine with this. The non-KF5 project (okular, marble, whatever)
would in any case have a dependency on KF5/Tier1 and so the fact that
the tooling lives there is probably fine. (And this essentially means
no change from how I am currently working, plus-or-minus a change of
repo name at some point
2016 at 23:14, Albert Astals Cid wrote:
> El diumenge, 3 d’abril de 2016, a les 23:04:48 CEST, Ingo Klöcker va escriure:
>> On Sunday 03 April 2016 20:27:27 Shaheed Haque wrote:
>> > What seems to be causing ripples is my suggestion that I call the
>> > *tool* to creat
s on getting something working...
Thanks, Shaheed
> Shaheed Haque schrieb am So., 3. Apr. 2016 um 14:32
> Uhr:
>>
>> On 1 April 2016 at 23:18, Albert Astals Cid wrote:
>> > El dijous, 31 de març de 2016, a les 23:04:07 CEST, Shaheed Haque va
>> > escriure:
>
On 1 April 2016 at 23:18, Albert Astals Cid wrote:
> El dijous, 31 de març de 2016, a les 23:04:07 CEST, Shaheed Haque va escriure:
>> Thanks for all the feedback. Here is what I am thinking:
>>
>> - The basic tooling might as well keep the PyKDE5 name because the
>>
to work through.
On 29 March 2016 at 09:01, Luca Beltrame wrote:
> Il Sat, 26 Mar 2016 22:30:18 +0000, Shaheed Haque ha scritto:
>
> Hey Shaheed,
>
>> about 800 lines of Python code [2] which can already create 684 .sip
>> files [3].
>
> As someone who occasional
need (think krita, konsole,
okteta, ...) too.
On 27 March 2016 at 14:41, Boudewijn Rempt wrote:
> On Sat, 26 Mar 2016, Shaheed Haque wrote:
>
>> Hi all,
>>
>> I've given up on trying to get the twine2 PyKDE bindings generator
>> working [1] because not only
Hi all,
I've given up on trying to get the twine2 PyKDE bindings generator
working [1] because not only is the code there broken, but it seems a
Sysiphusian task to maintain a C++ parser. Instead, a few evenings
with clang 3.9 have yielded what I hope is the basis of a way forward:
about 800 lines
On 29 May 2013 23:07, Albert Astals Cid wrote:
> El Dilluns, 20 de maig de 2013, a les 21:26:07, Shaheed Haque va escriure:
> > HI,
>
> Hi
>
> >
> > Over in Kate's mailing list (
> > http://lists.kde.org/?l=kwrite-devel&m=136804130419019&w=2) t
HI,
Over in Kate's mailing list (
http://lists.kde.org/?l=kwrite-devel&m=136804130419019&w=2) there is a
discussion about how to support the discovery of plugins written in Python.
Currently, this is done in a very Python-centric way using KStandardDirs to
find the plugins, and then docstrings wit
37 matches
Mail list logo