external_python_setuptools/setuptools/build_meta.py, branch docs/distutils-porting Python setuptools Remove pkg_resources.py31compat.makedirs() in favor of the stdlib 2020-02-16T17:33:32+00:00 Jon Dufresne jon.dufresne@gmail.com 2020-01-18T16:13:23+00:00 b3de7989665740cd4218d7d814e719d90e75de73 As setuptools is now python 3.5+, this compatibility shim is no longer necessary. 
As setuptools is now python 3.5+, this compatibility shim is no longer
necessary.
👹 Feed the hobgoblins (delint). 2020-01-19T17:46:30+00:00 Jason R. Coombs jaraco@jaraco.com 2020-01-19T17:46:30+00:00 3d4d8b9dde61b87271861b8c7ebeb168ac4fa72b 






Set sys.argv[0] in build scripts run by build_meta
2019-05-15T17:56:15+00:00

Emiel Wiedijk
me@aimileus.nl

2019-02-23T19:51:09+00:00

8f227af516c8c6b991c8e6c76f5bf4672f36c41e

Some setup.py scripts, use sys.argv[0] to locate the source directory of
a project. I added this to build_meta.__legacy__ since that is focused
on backwards compatibility with old scripts. However, @pganssle said
this behaviour should not be added to setuptools.build_meta. Fixes #1628





Some setup.py scripts, use sys.argv[0] to locate the source directory of
a project. I added this to build_meta.__legacy__ since that is focused
on backwards compatibility with old scripts. However, @pganssle said
this behaviour should not be added to setuptools.build_meta. Fixes #1628







build_meta: fix 2 issues with `build_wheel` / `build_sdist`
2019-04-22T21:02:33+00:00

Benoit Pierre
benoit.pierre@gmail.com

2019-04-22T20:18:50+00:00

5f88c42f3b4529956e4d02453ae571e32bc4692a

Fix the following cases:

* `build_sdist` is called with another sdist already present
  in the destination directory

* `build_wheel` is called with the destination directory not
  already created





Fix the following cases:

* `build_sdist` is called with another sdist already present
  in the destination directory

* `build_wheel` is called with the destination directory not
  already created







Fix error when wheels already exist in dist/
2019-04-22T14:19:28+00:00

Shashank Singh
shashanksingh28@gmail.com

2019-04-21T03:24:41+00:00

901f7cc2a036bfeb93bfbe480608e04c76c2c5ec

`build_meta.build_wheel` assumes that the only wheel in its output
directory is the one it builds, but prior to this, it also used the
`dist/` folder as its working output directory. This commit uses a
temporary directory instead, preventing an error that was triggered when
previously-generated wheel files were still sitting in `dist/`.

Fixes GH #1671





`build_meta.build_wheel` assumes that the only wheel in its output
directory is the one it builds, but prior to this, it also used the
`dist/` folder as its working output directory. This commit uses a
temporary directory instead, preventing an error that was triggered when
previously-generated wheel files were still sitting in `dist/`.

Fixes GH #1671







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.