Ticket #2130 (closed defect: wontfix)
routes is asserting that the application is deployed in zip-unsafe way
| Reported by: | faide | Owned by: | faide |
|---|---|---|---|
| Priority: | high | Milestone: | 2.1rc1 |
| Component: | TurboGears | Version: | trunk |
| Severity: | normal | Keywords: | |
| Cc: |
Description
you cannot create a zipsafe application using tg2 since routes is based on the assumption it will be able to scan directories inside your application.
This is considered a problem in some deployment scenarios where a single zipped egg is really preferred.
see routes.utils.controller_scan() for the offending (first one to explode, may not be the only one) function in routes.
Change History
comment:2 Changed 3 years ago by mramm
- Priority changed from normal to high
- Milestone changed from 2.0b5 to 2.0b6
Either we fix this now, or we will delay it to 2.1 because I want to do a feature freeze on or before Febuary 8th.
comment:3 Changed 3 years ago by mramm
- Milestone changed from 2.0b6 to 2.1
I would like to fix this, but it requires working with routes (and perhaps others) so I don't think it can happen in time for the tg 2.0 release. Re-targeting to 2.1
Note: See
TracTickets for help on using
tickets.
I think the wsgi app in turbogears actually does the controller lookups, so it could use a setuptools rather than raw disk lookups.
(IIRC routes just puts the routing info into the environ dictionary)