I'm going to interrupt the both of you with this, You're both headed down a path that you don't need to head down.
The problem that we have is not a problem of which piece of documentation is correct (they both should work as stated). The problem is not a case of "we must specify which version we need". The problem is not in the release process (though there is a different, specific problem, there, that I just figured out this morning). The problem is that something has changed outside of our system. I did this work for 2.1.1, and it worked. You could do exactly what the book describes, and it worked every time. It did so by modifying setup.cfg (to specify the allow_hosts parameter) and setup.py (to specify dependency_links). The result was a package, published on pypi, that would only use our index when you ran "easy_install tg.devtools" or "easy_install TurboGears2". If you did the easy_install on something else that happened to rely on one of those, it did not. The end result is that people could build their own index for their own package, giving them the level of control they needed for whatever they chose. Now, for some reason, the outside has changed. I don't know what, specifically, has changed, but something has. The result is that the install process isn't working the way it did, and people are running into problems. I wish I had the answer. I don't. I'm going to try to find it and fix it this weekend. Here's what I don't like, and don't see a good reason to do: * I don't like creating an installer script. If we require more than virtualenv / easy_install, we're doing something wrong, and people will realize this. * I don't like specifying revisions in the setup.py. Unless we have an extremely good reason (right now, we really don't, not even for the WebOb problem, since if the setup ran the way I got it working, we wouldn't need to do so), we shouldn't be forcing specific revisions on people. * I don't like having a complex command line for the install. Let's face it "easy_install -i http://www.turbogears.org/2.1/downloads/current/index/tg.devtools"; is a lot more complex than "easy_install tg.devtools". If anybody can help me figure out why distribute (and now, apparently, setuptools) are both ignoring the setup.cfg file, I would greatly appreciate it. If not, I'll fix it this weekend. Outside of that, though, let's not make things more complex. Stop trying to lock in revisions. Stop trying to add external tools to install. Stop making people use complex commands. All of these make problems. Oh, I did mention a problem in the release process, didn't I? Right now, if you look at setup.py, it specifies the "current" URL. It should specify the exact version number, so that people can do "easy_install tg.devtools==2.1.4", and always get 2.1.4 packaging. I'll fix that for the next go around. -- Michael J. Pedersen My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen Google Talk: [email protected] -- Twitter: pedersentg -- 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.
