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 Eloff
Recipients Eloff
Date 2008-01-12.20:14:26
SpamBayes Score 0.006711675
Marked as misclassified No
Message-id <1200168868.22.0.518070014613.issue1815@psf.upfronthosting.co.za>
In-reply-to
Content
There seems to be no way to skip the build step when running "setup.py
install" The behavior in such a case should be to skip build and use the
existing binaries as created in a separate build step or else print an
error. That way you can do "setup.py build" followed by "setup.py
install --skip-build" and you only have one build taking place.

The purpose of this would be to allow build to take place on a separate
computer to install. Currently I do this on Vista because MSVC 2003 is
not recommended or supported, and distutils won't use the installed MSVC
2005. So I do the build on a (virtual) XP machine and then install by
hand for lack of this option. I think Vista is a strong enough use case
to justify adding this feature.
History
Date User Action Args
2008-01-12 20:14:28Eloffsetspambayes_score: 0.00671167 -> 0.006711675
recipients: + Eloff
2008-01-12 20:14:28Eloffsetspambayes_score: 0.00671167 -> 0.00671167
messageid: <1200168868.22.0.518070014613.issue1815@psf.upfronthosting.co.za>
2008-01-12 20:14:27Elofflinkissue1815 messages
2008-01-12 20:14:26Eloffcreate