New submission from Tres Seaver tsea...@palladion.com:
A bare distutils install of a package with 'headers' passed to 'setup()'
dispatches to 'install_headers', which copies the exported header files
into the system include path.
'easy_install' bypasses the distutils 'install()' when doing a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/09/2012 11:13 AM, Tres Seaver wrote:
New submission from Tres Seaver tsea...@palladion.com:
A bare distutils install of a package with 'headers' passed to
'setup()' dispatches to 'install_headers', which copies the exported
header files
On Fri, Jul 6, 2012 at 11:20 AM, Daniel Holth dho...@gmail.com wrote:
It is exactly the same as setuptools' extras feature, and I didn't
quote the entire edit on-list. Also, there is a reference
implementation at https://bitbucket.org/dholth/distribute/ in the
DistInfoDistribution class.
The
Though in the interest of not having too many different ways to do a
similar thing, could this not also be used for tests/docs? Perhaps
even Provides-Extra: tests, and Provides-Extra: docs should be
reserved names as you suggested. I envision something like:
...
Provides-Extra: setup
On Mon, Jul 9, 2012 at 1:27 PM, Daniel Holth dho...@gmail.com wrote:
Though in the interest of not having too many different ways to do a
similar thing, could this not also be used for tests/docs? Perhaps
even Provides-Extra: tests, and Provides-Extra: docs should be
reserved names as you
I expect to see a lot of bugs in packages that require some of their
build-time dependencies at run time.
Maybe, but wouldn't that be the developer's problem? setup_requires
has the same issue--it does not install the setup requirements into
site-packages. Instead it just does an egg
On Mon, Jul 9, 2012 at 4:37 PM, Daniel Holth dho...@gmail.com wrote:
I expect to see a lot of bugs in packages that require some of their
build-time dependencies at run time.
Maybe, but wouldn't that be the developer's problem? setup_requires
has the same issue--it does not install the setup
Under a scheme like this one would have to list that dependency under
Requires-Dist twice: with and without the 'extra' marker. I might
still prefer extending the metadata format to add a
Setup-Requires-Dist or the like.
The difference is that setup/build dependencies generally should be
New draft up at https://bitbucket.org/dholth/python-peps/changeset/537e83bd4068
Adds Provides-Extra: (with longer explanation), Setup-Requires-Dist:
(full text below)
Setup-Requires-Dist lives because it makes sense to list packages only
needed for setup.py to run before install is possible.
