After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 705154 - xxx not in range 0 to 4294967295 when is clearly accepts 0->2**64-1
xxx not in range 0 to 4294967295 when is clearly accepts 0->2**64-1
Status: RESOLVED DUPLICATE of bug 678928
Product: pygobject
Classification: Bindings
Component: introspection
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2013-07-30 16:10 UTC by maksimilijans
Modified: 2013-07-31 00:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description maksimilijans 2013-07-30 16:10:50 UTC 
On a piece of code i'm porting there's this line:

self.pipeline.set_start_time(Gst.CLOCK_TIME_NONE)

and i got a trace back saying:

exceptions.ValueError: -1 not in range 0 to 4294967295

But when i change the line to:

self.pipeline.set_start_time(2**64-1)

it works
Comment 1 Dan Winship 2013-07-30 17:34:59 UTC 
that error comes from pygobject, not glib
Comment 2 Simon Feltman 2013-07-30 20:39:25 UTC 
Hi,

What version of PyGObject and Gst is this with (use gi.version_info and  Gst.version()) ? what is the architecture of the machine?
Comment 3 Simon Feltman 2013-07-31 00:29:54 UTC 
It looks like this was a problem in gobject-introspection which has already been fixed. Please re-open if you are seeing this problem in newer versions of PyGObject (>= 3.4 I think).

*** This bug has been marked as a duplicate of bug 678928 ***