| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
Handle the case where a missing transitive build dependency is
required by an extra for an already installed build dependency.
|
| |/ |
|
| | |
|
| |\
| | |
| | | |
Revert "drop easy_install script and associated documentation"
|
| | |
| | |
| | |
| | | |
This reverts commit 6e1838a9fb5feb000ba9b6a3c37c8b39d7e872b3.
|
| |\ \
| | |/
| |/| |
wheel: switch to `packaging.tags` for checking PEP 425 tags
|
| | | |
|
| |\ \
| | | |
| | | | |
Add support for `license_files` option in metadata
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
benoit-pierre/fix_empty_namespace_package_wheel_install
Fix empty namespace package wheel install
|
| | | |/
| | |/| |
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
The upload and register commands were deprecated over a year ago, in
July 2018 (PR GH-1410, discussed in issue GH-1381). It is time to
actively remove them in favor of twine.
|
| |\ \
| | | |
| | | | |
Fixes for python3.10
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The test command has not called sys.exit since commit
2c4fd43277fc477d85b50e15c37b176136676270.
|
| |\ \ \
| | | | |
| | | | | |
Change coding cookie to use utf-8 (lowercase)
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
While perfectly valid, the encoding 'UTF-8' (uppercase) is not
recognized by the Emacs MULE system. As such, it displays the following
warning when opening a file with it used as an encoding cookie:
Warning (mule): Invalid coding system ‘UTF-8’ is specified
for the current buffer/file by the :coding tag.
It is highly recommended to fix it before writing to a file.
Some discussion of this can be found at:
https://stackoverflow.com/questions/14031724/how-to-make-emacs-accept-utf-8-uppercase-encoding
While the post does offer a workaround for Emacs users, rather than ask
all to implement it, use the more typical utf-8 (lowercase).
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Provide a warning to users. Suggest using tox as an alternative generic
entry point.
Refs #1684
|
| |\ \
| | | |
| | | | |
Crash when invalid python_requires indicated in setup.cfg
|
| | | | |
|
| | |/ |
|
| | |
| | |
| | |
| | | |
packaging. Fixes #1858.
|
| |\ \
| | |/ |
|
| | |
| | |
| | |
| | | |
Do not test pip's master on 3.4, as support for it has been dropped.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Ensure the dictionary values are lists/tuples of strings.
Fix #1459.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
* 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
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
characters.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|