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 575982 - pitivi has syntax errors when using Python 2.6
pitivi has syntax errors when using Python 2.6
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: General
0.13.x
Other opensolaris
: Normal normal
: 0.13.1
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-19 16:23 UTC by Brian Cameron
Modified: 2009-05-14 14:10 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch fixing problem (1.21 KB, patch)
2009-03-19 16:24 UTC, Brian Cameron 		none Details | Review

Description Brian Cameron 2009-03-19 16:23:25 UTC 
When I build pitivi to use Python 2.6, I get these syntax errors when I try to run it:

Traceback (most recent call last):

+ Trace 213627

  • File "/usr/bin/pitivi", line 122 in <module> 
    _run_pitivi()
  • File "/usr/bin/pitivi", line 111 in _run_pitivi 
    import pitivi.pitivi as ptv
  • File "/usr/lib/pitivi/python/pitivi/pitivi.py", line 33 in <module> 
    from project import Project, file_is_project
  • File "/usr/lib/pitivi/python/pitivi/project.py", line 30 in <module> 
    from timeline.timeline import Timeline
  • File "/usr/lib/pitivi/python/pitivi/timeline/timeline.py", line 198 
    as = self.audiocomp._getAutoSettings()
SyntaxError: invalid syntax 

I am guessing that "as" is a reserved word or something.  I notice that changing the variable name to "asfoo" fixes the problem.  I'm sure this isn't the best thing to rename the variable, but since I am not familiar with the code I'm unsure of a better name.  Perhaps you could rename this upstream to
something more sensible to avoid this error?

Providing a patch that fixes this problem.
Comment 1 Brian Cameron 2009-03-19 16:24:51 UTC 
Created attachment 130979 [details] [review]
patch fixing problem
Comment 2 Edward Hervey 2009-03-19 16:40:27 UTC 
this patch doesn't apply to current git. Are you sure it's not already fixed ?
Comment 3 Brian Cameron 2009-03-19 16:47:15 UTC 
Sorry, looking at the latest git code, I don't see this code anymore.  I think
this is a non-issue.