t;brew reinstall pygobject3 gtk+3
>
> which did not fix the problem.
>
> Does someone have an idea of what may be going on?
> _______
It's girepository, not gi. And you don't usually want to import it, you want to
e.g.
from girepositor
> On Apr 28, 2017, at 8:42 AM, Christoph Reiter
> wrote:
>
> On Fri, Apr 28, 2017 at 4:11 PM, John Ralls wrote:
>> This doesn't make sense.
>
> I'll try to clarify.
>
> At least I consider the documentation and documentation generation to
> be a
sole motivation for all of the work?
At this moment the Github repo contains the fork of PyCairo and some projects
that seem to be about automatically generating API docs for PyGobject. That's
very far indeed from "everything Python + GObject related". Are you planning
also to for
ment variable or something I can (temporarily)
>> point at CPython 2.7 while doing this, without actually ending up with a
>> CPython 2.7 living in /usr/local/cpython-3.3?
>>
>> Thanks!
>
> Anyone?
That's a pretty basic question for this list. You'll
ffset really should be or if it's a pointer that's
getting overwritten.
Regards,
John Ralls
___
python-hackers-list mailing list
python-hackers-list@gnome.org
https://mail.gnome.org/mailman/listinfo/python-hackers-list
r investigation or for a workaround?
Regards,
John Ralls
#0 0x02bb9fe9 in g_type_class_meta_marshal (closure=0x76745b0,
return_value=0x0, n_param_values=3, param_values=0xbfff86e0,
invocation_hint=0xbfff8660, marshal_data=0x7677570) at gclosure.c:968
#1 0x02bba02e in g_type_class_meta_m
criterion for destruction. You can
force an object to run its first-stage destructor with run_dispose(), but that
won't free the memory. It's provided to break reference loops. Signals are just
a way of registering callbacks, and have nothing to do with this process.
Regards,
John Ralls
___
On Jul 8, 2012, at 1:20 AM, Robert Park wrote:
> On Fri, Jul 6, 2012 at 4:52 PM, John Ralls wrote:
>> WTF? Button and Label are both descendants of GtkWidget, which, according to
>> the PyGObject tutorial [0] is supposed
>> to implement drag_dest_set(). The example in th
On Jul 8, 2012, at 1:20 AM, Robert Park wrote:
> On Fri, Jul 6, 2012 at 4:52 PM, John Ralls wrote:
>> WTF? Button and Label are both descendants of GtkWidget, which, according to
>> the PyGObject tutorial [0] is supposed
>> to implement drag_dest_set(). The example in th
ial [0] is supposed
to implement drag_dest_set(). The example in the tutorial also fails with this
error.
Git master within the last 36 hrs or so of GLib, Gtk, GI, and PyGObject (and
everything else), built with llvm-gcc on OSX 10.7.
Regards,
John Ralls
[0] http://python-gtk-3-tutorial.readthe
On Jul 3, 2012, at 9:40 AM, Tomeu Vizoso wrote:
> On Mon, Jul 2, 2012 at 6:25 PM, John Ralls wrote:
>> How does one do this in pygobject?
>> Pygtk exposed the GDK_WINDOWING_FOO macros as a Gdk.Windowing constant; Gtk3
>> in C defines both those macros for compile time a
How does one do this in pygobject?
Pygtk exposed the GDK_WINDOWING_FOO macros as a Gdk.Windowing constant; Gtk3 in
C defines both those macros for compile time and GDK_IS_FOO_DISPLAY (display)
for runtime detection, but neither of them seem to be exposed by pygobjet.
Regards,
John Ralls
12 matches
Mail list logo
