Bob Ippolito <[EMAIL PROTECTED]> writes: > You also don't want your production environments to be very different from > your development environments.
Exactly! I also don't want to worry with things I don't need on my production environment. The cleaner the better. > Why care? If you weren't paying attention to the list or svn, you probably > wouldn't even have noticed. I pay attention to both... > It's absolutely useful to have the capability to test on a production server, > especially right before you deploy. If I'm testing what I'm deploying, I'll test the whole chain. If sqlite is in it, then I'll use it. If it is not, why would I care what happens with it? > So you propose that instead of adding a little code, we require users to read > more documentation? That's backwards. The idea is to make things easier, > and having something get installed for you is a hell of a lot easier than > reading docs. I find it easy to read documentation. If it is installed and not documented, it is probable that it won't be noticed... > I don't think that avoiding a couple unused files in a directory that you > never look at on a production server is a very good justification for > anything, especially not if it's in exchange for ease of use. What ease of use? More things to install, to maintain, etc. If you use sqlite, then it is a plus, if you don't, why having it there? > It's easier to require it than to document it and make people read the docs. > People don't read documentation unless something goes wrong. And people don't use the tools unless they know it is there... How to tell them it is there? > TurboGears is great because it's easy to get up and going, the only thing you > need to remember how to do is run tg-admin and adjust your db uri. To that > end, I've proposed that the quickstart db uri should default to an > in-project-dir SQLite database to remove that requirement for prototyping. > It also makes the barrier to entry a lot lower for someone who just wants to > download TurboGears and go through some of the tutorials. I agree that it makes it easy, but making this a requirement for those that already know turbogears and are using it for real projects is a bit different. > There's a shitload of things in Python and TurboGears that you don't use in a > production environment, but it doesn't mean the space they take up on disk > does any harm. They aren't additional security risks, they don't get in the I'm not concerned with space. And two wrongs doesn't make one right. I don't believe that just because there's a lot that isn't used more should be added. If it is, I'll live with that, but I don't see why adding it. > way, and they don't make TurboGears harder to install or deploy. I really > don't see any justified reason to avoid their inclusion. We think in opposite directions. It will an infrutiferous discussion in the end, since none of us will make the other change his mind. If there were good reasons, it could lead somewhere, but arguing that just because there are more things there and because it is small enough is not what I believe to be the right thing to do... My vote is -1 for adding this. Your is +1. If there are more "+" than "-", then I'll have to live with that. If there are more "-" than "+" then you'll have to live with that... In the end, it's up to Kevin :-) We just comment and he decides... -- Jorge Godoy <[EMAIL PROTECTED]>
