Bug 21237 - Extending Enum from uint in pyatspi/base.py causes NameError
Summary: Extending Enum from uint in pyatspi/base.py causes NameError
Status: RESOLVED FIXED
Alias: None
Product: at-spi2
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Mike Gorse
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-16 18:14 UTC by Willie Walker
Modified: 2009-04-17 12:31 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Patch to extend from dbus.UInt32 (399 bytes, patch)
2009-04-16 18:14 UTC, Willie Walker
Details | Splinter Review

Description Willie Walker 2009-04-16 18:14:46 UTC
Created attachment 24882 [details] [review]
Patch to extend from dbus.UInt32

Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "/export/home/wwalker/work/orca.svn/trunk/bld/lib/python2.4/site-packages/orca/orca.py", line 54, in ?
    import mouse_review
  File "/export/home/wwalker/work/orca.svn/trunk/bld/lib/python2.4/site-packages/orca/mouse_review.py", line 28, in ?
    import debug
  File "/export/home/wwalker/work/orca.svn/trunk/bld/lib/python2.4/site-packages/orca/debug.py", line 32, in ?
    import pyatspi
  File "/export/home/wwalker/work/at-spi2-core/bld/lib/python2.4/site-packages/pyatspi/__init__.py", line 17, in ?
    import registry
  File "/export/home/wwalker/work/at-spi2-core/bld/lib/python2.4/site-packages/pyatspi/registry.py", line 26, in ?
    from desktop import Desktop as _Desktop
  File "/export/home/wwalker/work/at-spi2-core/bld/lib/python2.4/site-packages/pyatspi/desktop.py", line 16, in ?
    from base import BaseProxyMeta
  File "/export/home/wwalker/work/at-spi2-core/bld/lib/python2.4/site-packages/pyatspi/base.py", line 36, in ?
    class Enum(uint):
NameError: name 'uint' is not defined

Extending from dbus.UInt32 works better.
Comment 1 Mike Gorse 2009-04-17 12:31:42 UTC
Applied.  Thanks for the patch.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.