Edgewall Software

Opened 13 years ago

Last modified 13 years ago

#8061 closed defect

0.11.3 ticket query error: NameError: global name 'set' is not defined — at Version 2

Reported by: dgaulke@… Owned by:
Priority: high Milestone: 0.11.4
Component: ticket system Version: 0.11.3
Severity: major Keywords: python23
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Christian Boos)

The python 2.3 incompatibility is back with 0.11.3. I get the following in the logs when going to "Custom Query". I wish I could upgrade python, but still not an option for me.

  File "/usr/lib/python2.3/site-packages/Trac-0.11.3-py2.3.egg/trac/ticket/query.py", line 577, in template_data
    wikify = set([f['name'] for f in self.fields
NameError: global name 'set' is not defined

Change History (2)

comment:1 by Christian Boos, 13 years ago

Keywords: python23 added
Milestone: 0.11.3
Priority: normalhigh

Hm, too bad, r7893 was not complete ;-)

comment:2 by Christian Boos, 13 years ago

Description: modified (diff)

One of the problem is that none of the Trac developers seem to be using 2.3 anymore.

Jonas, you mentioned on IRC that you couldn't run a buildbot for 2.3 as it doesn't support virtualenv. I'm not familiar with buildbot, so I don't know if the requirement for virtualenv comes from buildbot usage or if you just used virtualenv to setup the test environments for 2.4, 2.5 and 2.6. If it's the latter, then I think you could nevertheless have a test environment for Python 2.3 without virtualenv, as we have to test Trac 0.11-stable only with that version.

Note: See TracTickets for help on using tickets.