Ok, I took the plunge. I still have not moved the header files since they are
mostly used by static bindings and I have not removed the pygtk.pth file.
Please make sure to clean out your install and build roots and test against
PyGtk and other static bindings to make sure I didn't just break t
Quoting "Tomeu Vizoso" :
Why would that be a kludge? For maintainability reasons, I tend myself
to introspection-only,
Up until now I had the impression that we were going to be supposed to work
like that: use on of both, but never both systems together. So the point of
the "do not mix" warning
On Tue, Nov 23, 2010 at 20:15, Dieter Verfaillie
wrote:
> Quoting "Tomeu Vizoso" :
>>
>> On Tue, Nov 23, 2010 at 13:46, Dieter Verfaillie
>> wrote:
>>>
>>> Quoting "Tomeu Vizoso" :
>>> It's not up to me to decide anything, but is a kludge like that really
>>> planned to be supported? Maybe I miss
Quoting "Tomeu Vizoso" :
On Tue, Nov 23, 2010 at 13:46, Dieter Verfaillie
wrote:
Quoting "Tomeu Vizoso" :
It's not up to me to decide anything, but is a kludge like that really
planned to be supported? Maybe I missed the point of the whole gi effort,
I thought the goal was that static bindings
On Tue, Nov 23, 2010 at 13:46, Dieter Verfaillie
wrote:
> Quoting "Tomeu Vizoso" :
>>> Building on the above, we could have part of a reliably method to
>>> detect [2] if the static bindings get imported but you already have
>>> imported gi (but not necessarily the inverse!) and raise a
>>> wa
Quoting "Tomeu Vizoso" :
* Where are the following going to be installed?
* tests and testhelper?
Do we really need to install those?
On mswindows they are (well, will be with the next stable release
anyway) installed into site-packages/gtk-2.0/tests/pygobject. The
pygtk package installs i
On Fri, Nov 19, 2010 at 13:30, Dieter Verfaillie
wrote:
> Quoting "John Palmieri" :
>>
>> If you feel this is a really bad idea, speak now.
>
> It's a great idea, maybe a bit overdue even ;)
> Some questions/thoughts:
>
> * Where are the following going to be installed?
> * tests and testhelper
Quoting "John Palmieri" :
If you feel this is a really bad idea, speak now.
It's a great idea, maybe a bit overdue even ;)
Some questions/thoughts:
* Where are the following going to be installed?
* tests and testhelper?
* codegen/
I suppose this one can stay in site-packages/g
On Thu, Nov 18, 2010 at 12:49 PM, John Palmieri wrote:
> If you feel this is a really bad idea, speak now.
Frankly, I can't believe this wasn't done sooner. Good luck!
--
http://exolucere.ca
___
pygtk mailing list pygtk@daa.com.au
http://www.daa.com
Hi all,
I'm taking a stand on the issue of PyGObject modules being placed in the
gtk-2.0 directory. This causes path issues when built in a buildroot and
causes confusion issues when developers aren't sure if they should import pygtk
and call pygtk.require('2.0'). Not to mention that PyGObjec
10 matches
Mail list logo
