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 #2130 (closed defect: wontfix)

Opened 11 years ago

Last modified 9 years ago

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:1 Changed 11 years ago by mramm

  • Milestone changed from 2.0 to 2.0b4

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)

comment:2 Changed 10 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 10 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

comment:4 Changed 9 years ago by mramm

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

Waiting on distribute and the next gen of packaging to determine how this should work.

comment:5 Changed 9 years ago by percious

  • Milestone changed from 2.1 to 2.1rc1
Note: See TracTickets for help on using tickets.