| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | | |
This both prevents the warning from surfacing during the tests and
ensures that no regressions occur.
|
| | | |
|
| |\ \
| | | |
| | | | |
added unittest for _download_git
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Prior to this patch, if the author or author_email were omitted from
`setup`, a malformed `PKG-INFO` would be created.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This comment is not used anywhere and `platform.dist()` is deprecated.
See CPython PR #10414: https://github.com/python/cpython/pull/10414
and bpo-35186: https://bugs.python.org/issue35186
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The `upload.show_response` feature was not added until Python 3. Rather
than backport it, it is now enabled only if supported.
This also adds a "smoke test" for the feature.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes uploads when bdist_rpm or bdist_dumb are the command, both of
which insert a comment about what platform they are built for.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes an issue where `distutils.spawn.spawn` was not available in
the ported upload_file, which is only used when signing the data.
This also adds a test that the gpg signature command is invoked and
included in the uploaded data.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
`test_upload_metadata` was written before the fixture, so this updates
the test to use the fixture.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a fixture to create an upload command with a patched version of
urlopen so that no HTTP queries are sent.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rather than writing to a file in a temporary directory, we can write to
and read from an in-memory buffer, now that the encoding functionality
in write_pkg_file is fixed.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously this value was hard-coded to '1.0', which was inaccurate for
many packages.
Fixes #1381
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
Add futures and backport to Python 2.7 test requirements
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
`setuptools.tests.test_build_meta` relies on the Python 3 feature
`concurrent.futures` to run, and as a result has been silently skipped
in Python 2.7. This adds the `futures` backport to the 2.7 test
requirements and turns the `pytest.importorskip` invocations in test_build_meta
into standard import statements.
|
| | | | | |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
This tests that `setup.py` is included by default in the distribution
with the egg_info command and when an sdist is built with
build_meta.build_sdist
|
| |\ \ \
| | | | |
| | | | | |
Deprecate the requires keyword
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
For runtime dependencies, install_requires should be used. For build
dependencies, a PEP 518-compliant `pyproject.toml` should be used.
Other dependencies can use extra requirements.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These are tests to ensure that the specified deprecation warnings are
raised when the functions are called.
Co-authored-by: Junhan Huang <robin.j.huang@gmail.com>
Co-authored-by: Marton Pono <marci93@gmail.com>
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Also reuse pre-defined py2_only and py3_only decorators where
appropriate.
|
| | | |
|
| | | |
|
| | | |
|
|/ /
| |
| |
| | |
Co-Authored-By: Poyzan Nur Taneli <31743851+ptaneli@users.noreply.github.com>
|
| |
| |
| |
| |
| |
| | |
In the test case, dist.data_files needs to be sorted because the
current implementation loads the configuration files as a dictionary
with arbitrary order on Python < 3.6.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
daa/pkg-resources-always-handle-namespace-package-path
Improved handling of module __path__ attribute for namespace packages, fixes #1321
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Touch 'egg-info' directory
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'tox' determines whether a package should be rebuilt by comparing the
timestamp of the package's 'egg-info' directory and its 'setup.py' or
'setup.cfg' files [1][2]. Unfortunately this checks the 'egg-info'
directory itself, which is not updated, unlike the contents of that
directory. This means that 'tox' will always rebuild the package once
one of the two setup files has been updated.
While this is clearly a bug in 'tox' that should be fixed separately,
there is merit in using this as a heuristic so enable it.
[1] https://github.com/tox-dev/tox/blob/3.1.0/src/tox/venv.py#L253-L257
[2] https://github.com/tox-dev/tox/blob/3.1.0/src/tox/venv.py#L221-L244
Signed-off-by: Stephen Finucane <stephen@that.guru>
|
|\ \ \ \
| | | | |
| | | | | |
build_meta.get_requires_for_build_sdist does not include wheel
|