Mercurial > p > roundup > code
view test/test_pythonexpr.py @ 6614:e9dc8e526dd0
Remove fix for old mysql bug; try to improve postgresql perf
Supposedly mysql bug that causes
test_mysql.mysqlDBTest.testFilteringSpecialChars to fail was fixed in
8.0.1 in 2017: https://bugs.mysql.com/bug.php?id=74901
Also disable fsync for postgres as we prefer speed to durability of
data when running test suite. Need to find correct path for
postgrsql.conf, so ls command added as well.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 12 Feb 2022 00:50:02 -0500 |
| parents | e70885fe72a4 |
| children |
line wrap: on
line source
""" In Python 3, sometimes TAL "python:" expressions that refer to variables but not all variables are recognized. That is in Python 2.7 all variables used in a TAL "python:" expression are recognized as references. In Python 3.5 (perhaps earlier), some TAL "python:" expressions refer to variables but the reference generates an error like this: <class 'NameError'>: name 'some_tal_variable' is not defined even when the variable is defined. Output after this message lists the variable and its value. """ import unittest from roundup.cgi.PageTemplates.PythonExpr import PythonExpr as PythonExprClass class ExprTest(unittest.TestCase): def testExpr(self): expr = '[x for x in context.assignedto ' \ 'if x.realname not in user_realnames]' pe = PythonExprClass('test', expr, None) # Looking at the expression, only context and user_realnames are # external variables. The names assignedto and realname are members, # and x is local. required_names = ['context', 'user_realnames'] got_names = pe._f_varnames for required_name in required_names: self.assertIn(required_name, got_names)
