This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author higery
Recipients Peter.Waller, alexis, carljm, eric.araujo, higery, meatballhat, michael.mulich, tarek
Date 2011-08-18.15:54:16
SpamBayes Score 3.87872e-10
Marked as misclassified No
Message-id <>
>>IOW, in my opinion, support for setuptools develop command is not needed in packaging core

Then do you also mean support that for setuptools install is also not necessary in packaging core?

>>and still be taken care directly be the users wanting to run python develop: I don't see any reason to make it avaible on the stdlib.

I think the current implemention way of Packaging 'install' command just offers an executing router to run a proper 'install', which users doesn't need to know. It also the same to 'develop'. BTW, I think it's ok if setuptools is already installed when a user try to run 'python develop', if not, python will report error. In addition, Packaging use a different way to issue commands - cd to the source directory, and use 'pysetup run develop' to do the job. Old will be supported only by issuing commands under the source directory containing the, and if setuptools exists, Packaging will dispatch the job to it.
Date User Action Args
2011-08-18 15:54:16higerysetrecipients: + higery, tarek, carljm, eric.araujo, meatballhat, Peter.Waller, alexis, michael.mulich
2011-08-18 15:54:16higerysetmessageid: <>
2011-08-18 15:54:16higerylinkissue8668 messages
2011-08-18 15:54:16higerycreate