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 684271 - Invalid python3 syntax in examples/magFocusTracker.py
Invalid python3 syntax in examples/magFocusTracker.py
Status: RESOLVED FIXED
Product: pyatspi2
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
: 689957 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-09-18 07:01 UTC by Daniel Holbach
Modified: 2021-06-10 08:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to fix the issue. (360 bytes, patch)
2012-09-18 07:01 UTC, Daniel Holbach
none Details | Review

Description Daniel Holbach 2012-09-18 07:01:06 UTC
Created attachment 224577 [details] [review]
Patch to fix the issue.

daniel@daydream:~/pyatspi-2.5.92+dfsg$ python3 -tt examples/magFocusTracker.py 
  • File "examples/magFocusTracker.py", line 285
    print 'Magnification service not available. Exiting.'
SyntaxError: invalid syntax
daniel@daydream:~/pyatspi-2.5.92+dfsg$
Comment 1 Daniel Holbach 2012-09-18 07:26:47 UTC
Ubuntu bug about this: https://bugs.launchpad.net/ubuntu/+source/pyatspi/+bug/1052331
Comment 2 André Klapper 2013-08-14 10:07:13 UTC
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Comment 3 Magdalen Berns (irc magpie) 2015-06-05 14:05:45 UTC
Review of attachment 224577 [details] [review]:

Not tested it's master compatible but the change makes sense to me. Mike are you able to review this patch?
Comment 4 Mike Gorse 2019-05-21 00:09:22 UTC
Sorry--I'd apparently overlooked this bug. Anyway, finally merged the patch.
Comment 5 André Klapper 2021-06-10 08:03:22 UTC
*** Bug 689957 has been marked as a duplicate of this bug. ***