On Mon, Jun 1, 2009 at 12:41 AM, Antoine Pitrou
Tarek Ziadé
writes: Now the major problem with this is : the last setuptools commit is 7 months old, and right now people are trying to obtain a new setuptools version for svn 1.6 compatiblity for quite a time now.
I don't have any take in this, but perhaps a solution would be a friendly fork of setuptools. Apparently, it's not like there would be much competition between both branches. :)
If I fork setuptools to fix those problem, I will have to release it under another name, and ask people to change their setup.py file. This can lead to a messy situation in the Python community imho. People are already quite disturbed by the fact that we have distutils *and* setuptools I think the solution is that Phillip bless someone that have time to spend on it, to work on fixing those problems in setuptools. I have volunteered to maintain distutils, and I am currently pushing the good bits of setuptools in Distutils. I can work a bit on setuptools side too since it's located on the same Subversion. But I need Phillip insights and blessing for that.
Not being able to test setuptools-requiring software with 2.7 is rather annoying.
Yes, I agree. Regards Tarek -- Tarek Ziadé | http://ziade.org