Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #901 (closed defect: fixed)

Opened 13 years ago

Last modified 9 years ago

py23 test failures

Reported by: HalWine <hal.wine@…> Owned by: anonymous
Priority: normal Milestone: 1.0
Component: Tests Version: 0.9a6
Severity: normal Keywords: py23 nosetests
Cc:

Description

Under py23, something definately isn't working as expected in the tests.

from one specific test:

$ nosetests turbogears/widgets/tests/test_forms.py
ERROR: turbogears.widgets.tests.test_forms.test_nested_variables
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"/usr/lib/python2.3/site-packages/nose-0.9.0a2-py2.3.egg/nose/case.py",
line 52, in runTest
    self.testFunc()
  File
"/home/hwine/lib/python2.3/TurboGears-0.9a6-py2.3.egg/turbogears/widgets/tests/test_forms.py",
line 176, in test_nested_variables
    assert newroot.foo
!AttributeError: 'NestedController' object has no attribute 'foo'

I've instrumented the code, and the method NestedController.checkform is not called in py23, but is in py24 (which passes the test).

My python meta-programming is too weak to diagnosis this. If someone can point me to the issue, I can apply at the other locations. Here's the relevant source code starts at http://trac.turbogears.org/turbogears/browser/tags/0.9a6/turbogears/widgets/tests/test_forms.py#L154

Change History

comment:1 Changed 13 years ago by kevin

I see something definitely wrong. In turbogears.util there are generator expressions.

comment:2 Changed 13 years ago by roger.demetrescu

Hmmm... you are talking about flatten_sequence(), aren't you ? :/

If so, it is related to #678 and #680...

comment:3 Changed 13 years ago by kevin

nevermind... I was wrong.

comment:4 Changed 13 years ago by jorge.vargas

  • Component changed from TurboGears to tests

comment:5 Changed 13 years ago by jorge.vargas

  • Milestone changed from 1.0b1 to 1.0b3

comment:6 Changed 12 years ago by alberto

  • Milestone changed from 1.0b3 to 1.1

comment:7 Changed 12 years ago by jorge.vargas

is this still happening?

comment:8 Changed 12 years ago by HalWine

I don't know if this is still happening. With no activity, we had to abandon TG for our py 2.3 boxes. We only use it on boxes where we can deploy 2.4 now.

comment:9 Changed 12 years ago by alberto

  • Milestone changed from 1.1 to __unclassified__

Batch moved into unclassified from 1.1 to properly track progress on the later

comment:10 Changed 11 years ago by khorn

  • Status changed from new to closed
  • Resolution set to fixed

Closing as fixed. The related tickets have been closed and no further problems have been reported.

If you are reading this and still have this problem, please reopen the ticket.

comment:11 Changed 9 years ago by chrisz

  • Milestone changed from __unclassified__ to 1.0
Note: See TracTickets for help on using tickets.