delta/python-setuptools-git.git/setuptools, branch di-patch-1 github.com: pypa/setuptools.git Fix typo in docstring 2019-03-13T18:54:46+00:00 Dustin Ingram di@users.noreply.github.com 2019-03-13T18:54:46+00:00 42002a7efeb2c267ded78b3b3569dc019748c6bc 






Remove duplicate import io (#1713)
2019-03-06T14:22:28+00:00

Frédéric Chapoton
fchapoton2@gmail.com

2019-03-06T14:22:28+00:00

16e452a42a3dbbb0ab3d3146ffa3b743cdca2539

Found by lgtm




Found by lgtm






Automatically skip tests that require network
2019-02-23T17:38:50+00:00

Paul Ganssle
paul@ganssle.io

2019-02-07T14:28:29+00:00

b224605a8c16b2a713120bf0d484fa12ce781f02












tests: improve `test_pip_upgrade_from_source`
2019-02-23T01:39:27+00:00

Benoit Pierre
benoit.pierre@gmail.com

2019-01-28T22:07:59+00:00

82db4c621974659513effae337d47a05e31fe7a5

Parametrize the test to check different versions of pip
(including master) are correctly supported.





Parametrize the test to check different versions of pip
(including master) are correctly supported.







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.







Set sys.path in try/finally block with comment
2019-02-03T17:25:06+00:00

Paul Ganssle
paul@ganssle.io

2019-01-28T14:22:49+00:00

49d17725a0ad02552babbdc79c737cfb27430f4f

Per Nick Coghlan's suggestion on PR #1652, a try/finally block ensures
that the path is restored even in the event of an error.





Per Nick Coghlan's suggestion on PR #1652, a try/finally block ensures
that the path is restored even in the event of an error.







Add build_meta_legacy backend
2019-02-03T17:25:06+00:00

Paul Ganssle
paul@ganssle.io

2019-01-27T17:31:28+00:00

fd3b06dae1a33b3131cf96ddb9d7938430b9d8b5

This is part of the solution to GH #1642, it is a
backwards-compatibility backend that can be used as a default PEP 517
backend for projects that use setuptools but haven't opted in to
build_meta.





This is part of the solution to GH #1642, it is a
backwards-compatibility backend that can be used as a default PEP 517
backend for projects that use setuptools but haven't opted in to
build_meta.