| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Closes: #1557
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* ignore distutils' warning (`Unknown distribution option: 'python_requires'`)
* fix test on Windows
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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 with PEP 517 builds when wheel exists (GH #1761)
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
`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
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As a mitigation for #1730, this commit limits the number of workers in
the ProcessPoolExecutor to 1 (default is the number of CPUs). On PyPy,
having a higher number of available workers dramatically increases the
number of concurrent processes, leading to some resource exhaustion
issues.
This does not address the root issue, but should improve the situation
until the root issue is addressed.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently, this will fail because setuptools.build_meta.build_wheel
assumes that no wheels already exist in the `dist/` directory.
See GH #1671
|
| | | | |
| | | | |
| | | | | |
Checking for new implementation solving issue #1740
|
| | | | |
| | | | |
| | | | | |
Windows does not change the working directory for a process via `cd .. && <process>` (see e.g. this question: https://stackoverflow.com/q/55641332/8575607 ). This commit replaces the use of `cd .. &&` with arguments provided by `git` and `hg` respectively.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
uniquify paths in PYTHONPATH
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
duplicate entries.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When running in a complex environment with lots of installed
packages, PYTHONPATH gets way too long. Instead, just make sure
that paths_on_pythonpath doesn't contain duplicates
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
characters.
|
| | | | | | |
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Support requirement parsing in setuptools.build_meta
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Per GH #1682, with setuptools.build_meta we are not properly handling
the situation where setup_requires is actually a newline-delimited
string rather than a list, which is supported by setup.py interface.
This adds several failing (and some passing) tests for how
setup_requires is handled by setuptools.build_meta.
|
|/ / / / / / |
|
|/ / / / /
| | | | |
| | | | | |
Found by lgtm
|
| | | | | |
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
Parametrize the test to check different versions of pip
(including master) are correctly supported.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Using the absolute path to the directory of the setup script better
mimics the semantics of a direct invocation of python setup.py.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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 runs all build_meta tests, plus a test that it is possible to
import from the directory containing `setup.py` when using the
build_meta_legacy backend.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Failing test adapted from PR #1643
Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Bump version: 40.7.2 → 40.7.3
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
urllib.parse.urlparse is clumsy and causes problems as reported in #1663 and #1668. Alternative to #1499 and fixes #1668.
|
|\ \ \ \ \
| |/ / / /
| | | | | |
Ensure port is included in package-index
|
| | | | |
| | | | |
| | | | |
| | | | | |
the URL when auth is present. Fixes #1663.
|
|\ \ \ \ \
| |/ / / / |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| |/ / / / |
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
benoit-pierre/fix_889_and_non-ascii_in_setup.cfg_take_2
improve encoding handling for `setup.cfg`
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
ConfigParser.
|