| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
Under PEP-517, installing build dependencies is up to the frontend.
Closes gh-2303
|
|
|
|
|
| |
As setuptools is now python 3.5+, this compatibility shim is no longer
necessary.
|
| |
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
`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
|
|
|
|
|
| |
Since pkg_resources is imported elsewhere anyway, we don't get much
value out of porting the requirement parser locally.
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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 build_meta (PEP 517), always built gztar
|
| |
| |
| |
| | |
that a zip sdist should be generated. Fixes #1623.
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
| |
the wheel package is not required to build a source distribution
Resolves #1474.
|
| |
|
|
|
|
|
|
| |
This code is a bit ugly, but it's also been tested with the pip test suite
It's not the best solution long term (the best solution is to get the egg_info
directory directly from egg_info), but it works for now and avoids
technical risk.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
In some cases (specifically when pip imports this module in a virtualenv),
pkg_resources can already be imported, causing setuptools to load
entry_points from an older version. Here, we re-initialize the master
working set to fix the case where the entry points from an older
setuptools are loaded.
|
|
|