summaryrefslogtreecommitdiff
path: root/setuptools/tests/integration
Commit message (Collapse)AuthorAgeFilesLines
* Minor edits to integration tests.Jason R. Coombs2022-07-131-13/+13
|
* Just assume exactly one sdist is available.Jason R. Coombs2022-07-131-10/+2
|
* Add another conditional to resolve the release for version-specific ↵Jason R. Coombs2022-07-131-1/+1
| | | | packages. Fixes #3448.
* Fix `bellow` typo in docsMathieu Kniewallner2022-03-241-1/+1
|
* Automatic discovery of packages, py_modules and name (#2894)Anderson Bravalheri2022-03-071-0/+14
|\ | | | | | | | | | | | | | | | | | | It is desirable to have some configurations automatically derived. This is definitely possible for packages and py_modules, and (based on these two) also for name. This change adds a new class `setuptools.discovery.ConfigDiscovery` implementing the automatic discovery logic for packages, py_modules and name.
| * Reuse integration helperAnderson Bravalheri2022-03-051-0/+14
| |
* | Add a 'uses_network' marker to tests that require connectivityAnderson Bravalheri2022-03-051-0/+1
|/
* Remove `numpy` sdists from integration testsAnderson Bravalheri2022-01-071-2/+1
| | | | | | | | | | | | | | Numpy now uses a version cap for setuptools in their `pyproject.toml`, which defies a bit the value of including it in the integration tests. As revealed in a conversation with `numpy` maintainer, it seems that they not plan to remove this cap (maybe only update it from time to time, only if necessary). Moreover they are also studying other build backends. So I think that now the best thing to do would be stop trying to build numpy sdists with the current version of setuptools, otherwise we risk to break this test.
* Use setuptools wheel instead of source tree in integration testsAnderson Bravalheri2022-01-061-9/+3
|
* Separate some reusable integration helpersAnderson Bravalheri2021-12-212-60/+70
|
* Use shutil to find executableAnderson Bravalheri2021-12-211-2/+5
| | | | | This is more reliable then simply globing (and will also work in other operating systems)
* Simulate pip's isolation using virtualenvAnderson Bravalheri2021-12-211-51/+49
|
* Use separated "extras" for integration testsAnderson Bravalheri2021-12-211-1/+4
| | | | Instead of disabling pytest plugins, simply don't install them
* Add integration test based on feedback from #2849Anderson Bravalheri2021-12-212-0/+272
The selection of packages used in the integration test is arbitrary, and can be changed. The main criteria used was the time to build, and the number of "non-Python" dependencies. The only exception was numpy, due to its significance to the ecosystem.