-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [removed the bazaar list from the recipients] On Jul 21, 2007, at 1:02 AM, Phillip J. Eby wrote:
At 11:24 PM 7/20/2007 -0400, Barry Warsaw wrote:
Great for testing, thanks. But um, how /do/ normal users tell setup.py to install those extra packages?
Normally, people use install_requires, and the packages get installed automatically if you're using setuptools or easy_install.
Meanwhile, if you want to install a package's extras, you just use "easy_install foo[bar,baz]" to install package foo with extras bar and baz. "setup.py install" can't and won't ever handle extras.
Please keep in mind, though, that extras are for *optional* features. Your package won't work without bzrlib, so that's not really an "extra" and probably shouldn't be defined as such.
Agreed that in this particular example, extras aren't appropriate. But I have another use case where I definitely want to declare an optional dependency (e.g. munepy's optional dependence on the nose package for tests). So I'm wondering, why do you say setup.py can't and won't every support this? Is there a technical or philosophical limitation? I would think there should be a user friendlier way for a developer sitting there at the setup.py file to request that the optional packages get installed. I don't count using a different command as "user friendlier". Cheers, - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRqIbq3EjvBPtnXfVAQKKBwP+NIOV6bW6Pj55E2X76h3OYs1NT+OSP/ej pP8n6Vwmaq35fAfuwonYdQ6NErnf5SQqIrXLLmR8EgVQwoiGrzt4w/cd2AXEtn6I mZE87+P6wd4a96ts7ypUoh7keRdm8u/uX0knb2WBaZzT8AV67/kGknL08MlMWlRM NxXqn7qu9Mw= =r6Xh -----END PGP SIGNATURE-----