On Thu, Dec 15, 2011 at 10:19 AM, Alessandro Molina < [email protected]> wrote:
> I'm agree that if distribute/setuptools cared about the setup.cfg file > of tg whe wouldn't have this issue. > I'm not really proficient with distribute, but as far as I have been > able to see it cares about it only if you have tg.devtools already > installed, not while you are installing it. As I never changed the > version of setuptools that I use, I suspect that it has always been > like this and we just didn't notice it for 2.1.1. > Actually, I was very careful about it. While I don't remember which package it was, I do know that we had a similar type of conflict back then. You had to use our index, or you would get a newer version of some package that would cause failures. When I did the fix back then, it worked correctly. Like I said, I don't know what changed, or where it changed, but something outside of our control did change. I just wish I knew what that was. Have you tried asking on the distutils-sig mailing list if the > behavior we expect is the correct one? I have not. I don't know why, but I didn't think to do so. I'll do that, worst case, tonight. Today is going to be insanely busy for me as I get ready to leave the current job (tomorrow is last day). -- 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.
