install_requires vs requires
Hi, I am working on a new packaging solution, and I want to convert existing setup.py. I noticed that the install_requires as used by setuptools is not put into PKG-INFO as requires. Is this expected ? What is the difference between requires and require_install ? What happens when both have different values ? cheers, David
On Tue, Dec 15, 2009 at 8:28 AM, David Cournapeau <cournape@gmail.com> wrote:
Hi,
I am working on a new packaging solution, and I want to convert existing setup.py. I noticed that the install_requires as used by setuptools is not put into PKG-INFO as requires. Is this expected ?
Yes because it is not part of the standard, so setuptools is putting this in "requires.txt" which could be considered as an extension to the metadata. PEP 345 will include a new field that can replace requires.txt.
What is the difference between requires and require_install ? What happens when both have different values ?
What are those names ? See http://packages.python.org/distribute/setuptools.html#new-and-changed-setup-... for the list of new keywords introduced by Setuptools (+ a few more by Distribute)
cheers,
David _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Tarek Ziadé | http://ziade.org
On Tue, Dec 15, 2009 at 2:40 PM, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
On Tue, Dec 15, 2009 at 8:28 AM, David Cournapeau <cournape@gmail.com> wrote:
Hi,
I am working on a new packaging solution, and I want to convert existing setup.py. I noticed that the install_requires as used by setuptools is not put into PKG-INFO as requires. Is this expected ?
Yes because it is not part of the standard, so setuptools is putting this in "requires.txt" which could be considered as an extension to the metadata.
Ok, that makes sense.
PEP 345 will include a new field that can replace requires.txt.
What is the difference between requires and require_install ? What happens when both have different values ?
What are those names ?
I mostly use the distutils sources as reference, and the DistributionMetadata class generates provides metadata as documented in the corresponding PEP if the requires attribute is not empty. Does it make sense to generate PKG-INFO with the requires field which value would be taken from the install_requires ? I am using sphinx as my main test for the conversion now, and I noticed that setuptools does not generate a PKG-INFO with those data (v1.0 instead of v1.1 as I would have expected).
See http://packages.python.org/distribute/setuptools.html#new-and-changed-setup-... for the list of new keywords introduced by Setuptools (+ a few more by Distribute)
Will those arguments be added to distutils as well ? Or should I consider those arguments only when I detect distribute/setuptools-based setup.py ? cheers, David
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Cournapeau wrote:
On Tue, Dec 15, 2009 at 2:40 PM, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
Hi,
I am working on a new packaging solution, and I want to convert existing setup.py. I noticed that the install_requires as used by setuptools is not put into PKG-INFO as requires. Is this expected ? Yes because it is not part of the standard, so setuptools is putting
On Tue, Dec 15, 2009 at 8:28 AM, David Cournapeau <cournape@gmail.com> wrote: this in "requires.txt" which could be considered as an extension to the metadata.
Ok, that makes sense.
PEP 345 will include a new field that can replace requires.txt.
What is the difference between requires and require_install ? What happens when both have different values ? What are those names ?
I mostly use the distutils sources as reference, and the DistributionMetadata class generates provides metadata as documented in the corresponding PEP if the requires attribute is not empty.
Does it make sense to generate PKG-INFO with the requires field which value would be taken from the install_requires ? I am using sphinx as my main test for the conversion now, and I noticed that setuptools does not generate a PKG-INFO with those data (v1.0 instead of v1.1 as I would have expected).
See http://packages.python.org/distribute/setuptools.html#new-and-changed-setup-... for the list of new keywords introduced by Setuptools (+ a few more by Distribute)
Will those arguments be added to distutils as well ? Or should I consider those arguments only when I detect distribute/setuptools-based setup.py ?
The intent is to add the PEP 345 fields to PKG-INFO as generated by distutils. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkspj90ACgkQ+gerLs4ltQ7FowCgjauOk5CmewnCljm5W2qKdaBm YYoAnim9DoaUQ61Y+nJKAB+zalXfhoeW =ndG9 -----END PGP SIGNATURE-----
participants (4)
-
David Cournapeau -
David Lyon -
Tarek Ziadé -
Tres Seaver