external_python_setuptools/setuptools, branch feature/deterministic-provides-extras-2 Python setuptools Retain order when parsing values from config 2019-02-20T13:37:12+00:00 Jason R. Coombs jaraco@jaraco.com 2019-02-20T02:12:22+00:00 8cf5eb6b498b4d7954d539b1c832ca492da29ec5 






Prefer dict comprehension
2019-02-20T13:37:06+00:00

Jason R. Coombs
jaraco@jaraco.com

2019-02-20T02:08:48+00:00

c52a0abf7d752aab2faab10fe8221a3dc68104cb












On Python 3.5 and earlier, sort extras_require to support repeatable builds based on metadata generated from extras on those older Pythons.
2019-02-20T01:56:17+00:00

Jason R. Coombs
jaraco@jaraco.com

2019-02-19T22:56:42+00:00

0fc0f58fdb0dcb21cf3d2029d3ae4b735f39b1fd












Store 'provides_extras' as an ordered list to retain order.
2019-02-19T22:52:15+00:00

Jason R. Coombs
jaraco@jaraco.com

2019-02-19T22:52:15+00:00

2063cffefaa644e5948f50eddd524a0df23c8eb0












Expand tests to capture legacy behavior (sorted keys on older Pythons) and new behavior (honor author's order on Python 3.6)
2019-02-19T22:27:16+00:00

Jason R. Coombs
jaraco@jaraco.com

2019-02-19T22:24:49+00:00

78996f70807b9e0e50bc68c7579b339fedb7cade












Add test capturing expectation that provides_extras are ordered.
2019-02-17T22:08:13+00:00

Jason R. Coombs
jaraco@jaraco.com

2019-02-17T20:42:23+00:00

4a6b8ba7ced6bb841000a59bdef7f9879fb6578d












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.







Use absolute path in build_meta_legacy
2019-02-03T17:25:06+00:00

Paul Ganssle
paul@ganssle.io

2019-01-28T14:25:03+00:00

db590baf81ebcb23605da54118905437412228ce

Using the absolute path to the directory of the setup script better
mimics the semantics of a direct invocation of python setup.py.





Using the absolute path to the directory of the setup script better
mimics the semantics of a direct invocation of python setup.py.