Adam Jones schrieb: > 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)
+1 (but I would call it 'startup.py' or something similar) I very often have a few modifications in my start scripts, and it would be nice to have the code in my project package, so that different versions can be installed at the same time. > Cons: > * Adds another file to the project directory (and another letter to > controllers.py file name completion!) I don't get this. Which file completion do you mean? > * Not many other uses for console scripts in TG (due to scheduler, > tg-admin extensions, etc) Oh, I could think of a few. Off-line database maintenance scripts for example. > * Few people know about and/or use console scripts or command > extensions. That's no real argument. I, for one, didn't know much about how to build eggs at all, before I started using TG... Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
