external_python_setuptools/setuptools/build_meta.py, branch v41.0.0 Python setuptools Use pkg_resources.parse_requirements in build_meta 2019-03-16T19:10:55+00:00 Paul Ganssle paul@ganssle.io 2019-03-16T17:24:36+00:00 5efdf816fddcd8fbc9c3d1e6867a25848b1f9a06 Since pkg_resources is imported elsewhere anyway, we don't get much value out of porting the requirement parser locally. 
Since pkg_resources is imported elsewhere anyway, we don't get much
value out of porting the requirement parser locally.
Add requirement parsing in setuptools.build_meta 2019-03-16T16:58:29+00:00 Paul Ganssle paul@ganssle.io 2019-03-16T16:53:05+00:00 318f739d14a810042e6803fa3eb4c4e140f0ef88 This fixes GH #1682 by porting the pkg_resources requirement parsing logic into setuptools.build_meta, so that all valid requirement specifiers passed to setup_requires will be added to the get_requires_for_build_* function outputs. Fixes GH #1682 
This fixes GH #1682 by porting the pkg_resources requirement parsing
logic into setuptools.build_meta, so that all valid requirement
specifiers passed to setup_requires will be added to the
get_requires_for_build_* function outputs.

Fixes GH #1682
Add support for setup.cfg-only projects 2019-02-07T13:08:14+00:00 Paul Ganssle paul@ganssle.io 2019-01-31T13:29:36+00:00 179115b198387a21202433ea61cc53f2efd383fc Many projects can get away with an empty `setup.py` and use *only* the declarative `setup.cfg`. With the new PEP 517 backend, we can supply a default empty `setup.py` if one is not provided. 
Many projects can get away with an empty `setup.py` and use *only* the
declarative `setup.cfg`. With the new PEP 517 backend, we can supply a
default empty `setup.py` if one is not provided.
Rename build_meta:legacy to build_meta:__legacy__ 2019-02-05T13:42:36+00:00 Paul Ganssle paul@ganssle.io 2019-02-05T13:42:36+00:00 e04a41e3129fa9945e15b16fd6d65cc212c1d946 






Move build_meta_legacy to build_meta:legacy
2019-02-03T17:25:06+00:00

Paul Ganssle
paul@ganssle.io

2019-02-03T17:17:46+00:00

11fb3f38d23ff1e0d81e64ba3b68b3de2d2b990a

Rather than exposing a top-level module for the legacy backend, we will
move the legacy backend into the `setuptools.build_meta` module and
specify it using the module:object syntax.





Rather than exposing a top-level module for the legacy backend, we will
move the legacy backend into the `setuptools.build_meta` module and
specify it using the module:object syntax.







Add __all__ to setuptools.build_meta
2019-02-03T17:25:05+00:00

Paul Ganssle
paul@ganssle.io

2019-01-27T16:46:21+00:00

f40a47a776904b09747502a1f210af9fc92ec542












Wrap build_meta backend in a class
2019-02-03T17:25:05+00:00

Paul Ganssle
paul@ganssle.io

2019-01-27T16:45:10+00:00

74c323d1658f554b879ef6ac2867faf77776a2ac

In order to support both the `build_meta` and `build_meta_legacy`
backends, the core functionality is wrapped in a class with methods to
be overridden in build_meta_legacy. The class is an implementation
detail and should remain private.





In order to support both the `build_meta` and `build_meta_legacy`
backends, the core functionality is wrapped in a class with methods to
be overridden in build_meta_legacy. The class is an implementation
detail and should remain private.







Merge pull request #1625 from pypa/bugfix/1623-always-targz
2019-01-03T13:06:58+00:00

Jason R. Coombs
jaraco@jaraco.com

2019-01-03T13:06:58+00:00

572fb158a4077d779488cd3c81e6d47028322396

In build_meta (PEP 517), always built gztar




In build_meta (PEP 517), always built gztar






Extract common behavior into a function
2019-01-02T19:42:23+00:00

Jason R. Coombs
jaraco@jaraco.com

2019-01-02T19:42:23+00:00

2bb8225a6efa6f429d4522f47308b779a48cd07f












Avoid hanging indent
2019-01-02T19:39:37+00:00

Jason R. Coombs
jaraco@jaraco.com

2019-01-02T19:39:37+00:00

7378e6be2f8f8a0d96b748e256dfa6b53821c3f6