From: Nicolas Palix <nicolas.palix@univ-grenoble-alpes.fr>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] coccinelle depends on unmaintained pygtk
Date: Thu, 27 Feb 2020 10:56:08 +0100 [thread overview]
Message-ID: <1183e7d0-b6e4-834d-5b27-47c43661bae6@univ-grenoble-alpes.fr> (raw)
In-Reply-To: <alpine.DEB.2.21.2002271044550.4309@hadrien>
Le 27/02/2020 à 10:45, Julia Lawall a écrit :
>
>
> On Thu, 27 Feb 2020, Nicolas Palix wrote:
>
>> Hi Emmanuel,
>>
>> Instead of porting to GObject directly,
>> can we use PyGTKCompat ?
>>
>> https://wiki.gnome.org/Projects/PyGObject/PyGTKCompat
>
> The problem is resolved by removing the python file that relied on the
> unavailable library. I don't think that that python file is useful.
It looks like python/coccilib/coccigui contains the offending files:
coccigui.py, pygui.glade and pygui.gradep.
But according to vimcom.py and vimembed.py, these laters also depend of GTK.
Should the coccigui folder be entirely removed ?
>
> julia
>
>>
>> Regards,
>>
>> Le 04/02/2020 à 16:25, eamanu a écrit :
>>> Hi!
>>>
>>> On 04/02/2020 11:59, Julia Lawall wrote:
>>>> On Tue, 4 Feb 2020, eamanu wrote:
>>>>
>>>>> Hi everybody,
>>>>>
>>>>> Sorry if this issues is duplicated, I am new in the mailing list
>>>>> and in a very quickly searching I didn't found about this issue.
>>>>>
>>>>> I am working on Coccinelle package on Debian
>>>> Thanks!
>>>>
>>>>> and currently
>>>>> exist the next bug [1].
>>>>>
>>>>> There is any plan to port to use GObject Instrospection?
>>>>>
>>>>> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885267
>>>> I think we should just drop the code that depends on it. It was added for
>>>> a MS thesis more than 10 years ago, and I don't think anyone has used it
>>>> since.
>>>>
>>>> I will look into it.
>>>
>>> Great, if you need help, I can help :-)
>>>
>>> I will wait for any news. Thanks
>>>
>>> eamanu
>>>>
>>>> julia
>>>
>>> _______________________________________________
>>> Cocci mailing list
>>> Cocci@systeme.lip6.fr
>>> https://systeme.lip6.fr/mailman/listinfo/cocci
>>>
>>
>>
>> --
>> Nicolas Palix
>> http://lig-membres.imag.fr/palix/
>>
>
--
Nicolas Palix
http://lig-membres.imag.fr/palix/
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-02-27 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 14:48 [Cocci] coccinelle depends on unmaintained pygtk eamanu
2020-02-04 14:59 ` Julia Lawall
2020-02-04 15:25 ` eamanu
2020-02-27 9:43 ` Nicolas Palix
2020-02-27 9:45 ` Julia Lawall
2020-02-27 9:56 ` Nicolas Palix [this message]
2020-02-27 10:04 ` Julia Lawall
2020-02-28 11:39 ` Emmanuel Arias
2020-02-28 12:45 ` Julia Lawall
2020-02-28 15:14 ` eamanu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1183e7d0-b6e4-834d-5b27-47c43661bae6@univ-grenoble-alpes.fr \
--to=nicolas.palix@univ-grenoble-alpes.fr \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).