Bug 855194 - "from gi.repository import Gtk" fails
Summary: "from gi.repository import Gtk" fails
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: pygobject3
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: John (J5) Palmieri
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-07 00:21 UTC by Steven Usdansky
Modified: 2013-03-13 04:52 UTC (History)
4 users (show)

Fixed In Version: pygobject3-3.4.1.1-2.fc18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-09 15:00:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steven Usdansky 2012-09-07 00:21:35 UTC
Description of problem:
Cannot import from gi.repository

Version-Release number of selected component (if applicable):
pygobject3-3.3.4-8.fc18.x86_64
python3-gobject-3.3.4-8.fc18.x86_64
python3-3.3.0-0.4.rc1.fc18.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Open terminal window and run python3
2. "Type from gi.repository import Gtk" and press enter key
3.
  
Actual results:
>>> from gi.repository import Gtk
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python3.3/site-packages/gi/__init__.py", line 23, in <module>
    from ._gi import _API, Repository
ValueError: level must be >= 0
>>> Gtk.Window()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'Gtk' is not defined

>>> from gi.repository import cairo
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python3.3/site-packages/gi/__init__.py", line 23, in <module>
    from ._gi import _API, Repository
ValueError: level must be >= 0



Expected results:
Just works with no error

Additional info:
Worked properly several versions back. Not sure when it broke

Comment 1 Kalev Lember 2012-11-09 15:00:40 UTC
Thanks for reporting this!

I believe it's been fixed in later builds, so I'll just close the ticket. Please reopen if it's still an issue with a recent build.


Note You need to log in before you can comment on or make changes to this bug.