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 eric.araujo
Recipients Peter.Waller, alexis, carljm, eric.araujo, higery, meatballhat, michael.mulich, tarek
Date 2011-08-18.17:48:19
SpamBayes Score 6.23557e-13
Marked as misclassified No
Message-id <1313689699.97.0.619268474073.issue8668@psf.upfronthosting.co.za>
In-reply-to
Content
> [...] so I keep this command name as 'develop' and the simple usage
> of this command is :
> pysetup run develop
So far, so good.

> BTW, most developers in this list have agreed that 'develop' is a
> kind of install command, so I also add an entry funtion
> 'install_editable' for it,
That can be useful.  On the other hand, pip uses subprocesses instead of calling Python functions, to make sure an error in the called code does not stop pip.  I still think it’s a nice function to have.  The name should be changed: “editable” is not used in our current terminology, so install_develop would be IMO better.

I also think that “pysetup install --develop path/to/project” would be a nice high-level way to use develop, in the future.

About supporting setup.py develop: I think too that it is not needed.  Supporting setup.py install is a needed feature for *users*, as Alexis said; conversely, having a packaging-only develop feature can help seduce *developers* to use the new standards and tools.  My vote is for removing setup.py develop support.
History
Date User Action Args
2011-08-18 17:48:20eric.araujosetrecipients: + eric.araujo, tarek, carljm, meatballhat, Peter.Waller, alexis, michael.mulich, higery
2011-08-18 17:48:19eric.araujosetmessageid: <1313689699.97.0.619268474073.issue8668@psf.upfronthosting.co.za>
2011-08-18 17:48:19eric.araujolinkissue8668 messages
2011-08-18 17:48:19eric.araujocreate