- **status**: open --> invalid - **Comment**: Works for me now:
~~~~ $ python Python 2.7.3 (default, Apr 12 2012, 21:46:02) [GCC 4.1.2 20080704 (Red Hat 4.1.2-50)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import allura.controllers.root >>> ~~~~ --- ** [tickets:#5206] Resolve import error on allura.controllers.root** **Status:** invalid **Milestone:** forge-backlog **Created:** Tue Oct 30, 2012 02:18 PM UTC by Cory Johns **Last Updated:** Tue Oct 30, 2012 02:18 PM UTC **Owner:** nobody Since the changes [#3883] to separate the repo tools from the core, the list of tools available on project creation is now populated dynamically. To both populate the inputs on the `add_project` page and handle validation properly, the fields need to be populated in the `NeighborhoodAddProject` form's `__init__`. However, the form is instantiated on import and the necessary setup (registring `app_globals` with pylons) has not been done yet, causing it to fail. This causes issues with the test suite (since `allura.controllers.test_neighborhood_root` gets discovered and imported, which imports `allura.controllers.root`) and the push process (since it runs the smoke test which tries to verify that `allura.controllers.root` imports without error). These have temporary work-arounds in place (commits [ade7d6] and [c11f79], and using `--nosmoking` during Allura push), but the underlying issue needs to be resolved. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
