Roundup Tracker - Issues

Issue 655492

classification
roundup-admin initialise, TALPrefs error
Type: Severity: normal
Components: Installation Versions:
process
Status: closed works for me
:
: richard : richard, wbd
Priority: normal :

Created on 2002-12-18 00:07 by wbd, last changed 2002-12-22 00:35 by wbd.

Messages
msg543 Author: [hidden] (wbd) Date: 2002-12-18 00:07
This error occurred during installation, with Solaris 2.7, 
ActivePython 2.2.2.

Python complained during roundup-admin initialise, and 
the culprit was TALPrefs.py

#near bottom
import cgi
def quote(s, escape=cgi.escape):
   return '"%s"' % escape(s, 1)
del cgi

It complains that cgi.escape does not exist.  I think this 
is related to the new lexical scoping in Python 2.2.  
Changing to this, it works:

#near top
from cgi import escape as __cgi_escape

#near bottom
def quote(s, escape=__cgi_escape):
   return '"%s"' % escape(s, 1)

msg544 Author: [hidden] (richard) Date: 2002-12-18 00:15
Logged In: YES 
user_id=6405

Which version of Roundup are you using? I just installed and initialised a 
new tracker using python2.2 just fine... 
 
msg545 Author: [hidden] (richard) Date: 2002-12-18 00:17
Logged In: YES 
user_id=6405

Note that the code you quote works just fine in python 2.2.2. If you're using 
the latest version of Roundup, please attach the actual error you're getting. 
If not, please try upgrading to the latest version. 
 
msg546 Author: [hidden] (wbd) Date: 2002-12-18 04:23
Logged In: YES 
user_id=583237

Using latest stable release, 0.5.3, not the cvs head.  Maybe 
this is a Solaris or ActivePython specific bug?  At any rate, 
I'm playing it safe now and running roundup in python 2.1.2.  
It looks great; fast, too.
msg547 Author: [hidden] (richard) Date: 2002-12-18 04:30
Logged In: YES 
user_id=6405

If you could attach the actual error you get with py 2.2, that'd help :) 
 
msg548 Author: [hidden] (wbd) Date: 2002-12-22 00:35
Logged In: YES 
user_id=583237

I just reverted TALPrefs.py to the way it was, and changed 
my PATH and PYTHONPATH to use python2.2 again, to try 
and get the specific error message.  The problem is no longer 
occurring.  I can only guess that I didn't have Python 2.2 
configured correctly before, for the new account that I had 
created to initialize and run the tracker.  Sorry for the trouble; 
this incident can be closed.
History
Date User Action Args
2002-12-18 00:07:34wbdcreate