| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
to 'import setuptools' during 'get-pip', and in that case, stub the import to signal the presence of setuptools. Ref #3022. Fixes #2993.
|
| |
|
| |
|
|\
| |
| | |
set origin= for distutils.__spec__
|
| |
| |
| |
| | |
set origin so spec finding reports the correct location -- https://docs.python.org/3/library/importlib.html#importlib.machinery.ModuleSpec
|
| | |
|
| | |
|
|\ \
| |/
|/| |
Speedup startup of Python by importing less
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
``_distutils_hack`` is imported by a ``.pth`` file at every start of a
Python interpreter. The import of costly modules like ``re`` and
``contextlib`` almost doubles the initial startup time of an
interpreter.
- replace ``contextlib`` with simple context manager and try/except
- replace ``re`` with simple string match
- move import of ``importlib`` into function body
- remove ``warnings.filterwarnings()``, which imports ``re``, too.
Fixes: #3006
Signed-off-by: Christian Heimes <christian@python.org>
|
|\
| |
| | |
Capture performance of interpreter startup.
|
|/ |
|
|\
| |
| | |
Fixed a bug that easy install incorrectly parsed Python 3.10 version string
|
| | |
|
| | |
|
|\ \
| |/
|/| |
docs/2674: packaging resources in quickstart guide
|
| |
| |
| | |
Co-authored-by: Anderson Bravalheri <andersonbravalheri+github@gmail.com>
|
| |
| |
| | |
for pull request for #2674 as per developer guide
|
|/
|
| |
Section `Resources on Python packaging` did not point to any resource. Added as discussed on #2674
|
|\
| |
| | |
Remove `numpy` sdists from integration tests
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \
| |/
|/| |
Fix misplaced news fragment
|
|/
|
|
|
| |
PR #2839 accidentally misplaced the news fragment file under root.
This commit fix that.
|
|\
| |
| | |
Maintain `requires` order in METADATA.
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
It seems that workflows that build -> install -> build would have the order of requires changed by these sorted() calls. From a brief attempt to trace through all the related interfaces, it seems this is the only code that changes the order of the requirements and so would be the only source of the observed inconsistency of Requires-Dist entries.
If this sorting is desirable, the other setuptools and wheel interfaces that interact with the requirements should also sort them. Otherwise, it's valuable to retain the order across all parts of the system.
|
|\ \ \
| | | |
| | | | |
Change vendoring script to preserve license files
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
I believe that only wheels install licenses in the *.dist-info.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As pointed out by #2950, it is probably a good idea to keep the license
files for the vendored dependencies.
This is done by changing the `pavement.py` tasks.
|
|\ \ \ \
| | | | |
| | | | | |
[CI] Remove the need for the `tmp_src` fixture
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It seems that the release action in the CI was running even when the
cygwin tests did not pass... It is likely we want it to pass first.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some tests are running the build process using setuptools own directory
as cwd. This impacts the build process and also leave behind artifacts
produced during tests (like .egg-info folders)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now that all tests use `jaraco.envs`, there is no need to depend on
`pytest_virtualenv`.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of re-building/installing setuptools from the source tree
every time, the tests now rely on the venv, wheel and sdist fixtures
(the venv fixture is populated from sdist/wheel).
Moreover migrate `test_virtualenv` to use `jaraco.envs`
(so it uses the same libraries ad `test_distutils_adoption`).
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
… and change it to install the pre-build setuptools wheel (fixture)
instead of installing from the source tree
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
They should be build once for each session and be able to be re-used in
parallel (assuming read-only) for all tests.
This is useful when dealing with virtual environments
|