I don't know about default, but "optional and trivial" sounds good to me. There is not much to stop us from switching to putting the startup command in a "command.py" file in the project folder and importing/running from start-<projectname>.py. From there setup.py can have a console script line provided but commented out. (like the turbogears.* keywords are now)
Pros: * Very easy to migrate to console-script based startup * Provides a convenient place by default for command extensions * Startup procedures migrate with the project, convenient place for initialization * Able to retain original user interaction model Cons: * Adds another file to the project directory (and another letter to controllers.py file name completion!) * Not many other uses for console scripts in TG (due to scheduler, tg-admin extensions, etc) * Few people know about and/or use console scripts or command extensions. Overall I think it is a +1, but then again I've been looking for an easier way to start TG apps for a while now. -Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
