This repository has been archived by the owner on Jun 2, 2023. It is now read-only.
Update dependency setuptools to v65 [SECURITY] #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==59.4.0
->==65.5.1
GitHub Vulnerability Alerts
CVE-2022-40897
Python Packaging Authority (PyPA)'s setuptools is a library designed to facilitate packaging Python projects. Setuptools version 65.5.0 and earlier could allow remote attackers to cause a denial of service by fetching malicious HTML from a PyPI package or custom PackageIndex page due to a vulnerable Regular Expression in
package_index
. This has been patched in version 65.5.1.Release Notes
pypa/setuptools
v65.5.1
Compare Source
Misc
^^^^
mock
package, always use :external+python:py:mod:unittest.mock
-- by :user:hroncok
v65.5.0
Compare Source
Changes
^^^^^^^
src
-layout projects.Documentation changes
^^^^^^^^^^^^^^^^^^^^^
Misc
^^^^
and editable install (in documentation and as an informational warning).
validate_pyproject
.v65.4.1
Compare Source
Misc
^^^^
expand.StaticModule
when system default encoding doesn't match expectations for source files.6852b20
including fix for pypa/distutils#181.v65.4.0
Compare Source
Changes
^^^^^^^
d82d926
including support for DIST_EXTRA_CONFIG in pypa/distutils#177.v65.3.0
Compare Source
Changes
^^^^^^^
ConfigDiscovery.analyse_name
from splatting theDistribution.name
attribute -- by :user:jeamland
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
Dependency management section of the Quickstart guide <userguide/quickstart>
-- by :user:mfbutner
Misc
^^^^
v65.2.0
Compare Source
Changes
^^^^^^^
22b9bcf
, including fixed cross-compiling support and removing deprecation warning per pypa/distutils#169.v65.1.1
Compare Source
Misc
^^^^
missing module has the same name as its parent.
v65.1.0
Compare Source
Changes
^^^^^^^
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
legacy-editable
mode.v65.0.2
Compare Source
Misc
^^^^
c802880
).v65.0.1
Compare Source
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
/userguide/quickstart
about supportto
setup.py
.Misc
^^^^
build_ext
commands inheriting directly from
distutils
.buid_meta.prepare_metadata_for_build_wheel
whengiven
metadata_directory
is"."
.v65.0.0
Compare Source
Breaking Changes
^^^^^^^^^^^^^^^^
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
keywords
documentation regarding editable installationsto specify which
setuptools
version require a minimalsetup.py
file or not.v64.0.3
Compare Source
Misc
^^^^
optional extensions.
editable_wheel
to ensure other commands are finalized before usingthem. This should prevent errors with plugins trying to use different commands
or reinitializing them.
considered
package_data
ordata_files
.v64.0.2
Compare Source
Misc
^^^^
build_py
implementations when running editableinstalls in favor of a warning indicating what is the most appropriate
migration path.
This is a transitional measure. Errors might be raised in future versions of
setuptools
.accidentally/purposefully via discovery configuration during editable installs.
This should emulate the behaviour of a non-editable installation.
v64.0.1
Compare Source
Misc
^^^^
#3497: Fixed
editable_wheel
for legacy namespaces.#3502: Fixed issue with editable install and single module distributions.
#3503: Added filter to ignore external
.egg-info
files in manifest.Some plugins might rely on the fact that the
.egg-info
directory isproduced inside the project dir, which may not be the case in editable installs
(the
.egg-info
directory is produced inside the metadata directory given bythe build frontend via PEP 660 hooks).
v64.0.0
Compare Source
Deprecations
^^^^^^^^^^^^
#3380: Passing some types of parameters via
--global-option
to setuptools PEP 517/PEP 660 backendis now considered deprecated. The user can pass the same arbitrary parameter
via
--build-option
(--global-option
is now reserved for flags like--verbose
or--quiet
).Both
--build-option
and--global-option
are supported as a transitional effort (a.k.a. "escape hatch").In the future a proper list of allowed
config_settings
may be created.Breaking Changes
^^^^^^^^^^^^^^^^
#3265: Added implementation for editable install hooks (PEP 660).
By default the users will experience a lenient behavior which prioritises
the ability of the users of changing the distributed packages (e.g. adding new
files or removing old ones).
But they can also opt into a strict mode, which will try to replicate as much
as possible the behavior of the package as if it would be normally installed by
end users. The strict editable installation is not able to detect if files
are added or removed from the project (a new installation is required).
This implementation might also affect plugins and customizations that assume
certain
build
subcommands don't run during editable installs or that theyalways copy files to the temporary build directory.
.. important::
The editable aspect of the editable install supported this implementation
is restricted to the Python modules contained in the distributed package.
Changes in binary extensions (e.g. C/C++), entry-point definitions,
dependencies, metadata, datafiles, etc may require a new installation.
Changes
^^^^^^^
#3380: Improved the handling of the
config_settings
parameter in both PEP 517 andPEP 660 interfaces:
It is possible now to pass both
--global-option
and--build-option
.As discussed in #1928, arbitrary arguments passed via
--global-option
should be placed before the name of the setuptools' internal command, while
--build-option
should come after.Users can pass
editable-mode=strict
to select a strict behaviour for theeditable installation.
#3392: Exposed
get_output_mapping()
frombuild_py
andbuild_ext
subcommands. This interface is reserved for the use of
setuptools
Extensions and third part packages are explicitly disallowed to calling it.
However, any implementation overwriting
build_py
orbuild_ext
arerequired to honour this interface.
#3412: Added ability of collecting source files from custom build sub-commands to
sdist
. This allows plugins and customization scripts to automaticallyadd required source files in the source distribution.
#3414: Users can temporarily specify an environment variable
SETUPTOOLS_ENABLE_FEATURES=legacy-editable
as a escape hatch for the:pep:
660
behavior. This setting is transitional and may be removed in thefuture.
#3484: Added transient
compat
mode to editable installs.This more will be temporarily available (to facilitate the transition period)
for those that want to emulate the behavior of the
develop
command(in terms of what is added to
sys.path
).This mode is provided "as is", with limited support, and will be removed in
future versions of
setuptools
.Documentation changes
^^^^^^^^^^^^^^^^^^^^^
Development Mode </userguide/development_mode>
to reflect on theimplementation of :pep:
660
.v63.4.3
Compare Source
Misc
^^^^
b65aa40
including more robust support for library/include dir handling in msvccompiler (pypa/distutils#153) and test suite improvements.v63.4.2
Compare Source
Misc
^^^^
pyparsing
to 3.0.9.install_requires
andextras_require
misconfiguration in
setup.cfg
pyproject.toml
validation exception handling tomake relevant debugging information easier to spot.
v63.4.1
Compare Source
Misc
^^^^
274758f
, restoring compatibility shim in bdist.format_commands.v63.4.0
Compare Source
Changes
^^^^^^^
upload_docs
command is deprecated once again.Documentation changes
^^^^^^^^^^^^^^^^^^^^^
sphinx-hoverxref
extension to show tooltips on internal an external references.-- by :user:
humitos
sphinx-notfound-page
extension to generate nice 404 pages.-- by :user:
humitos
Misc
^^^^
c397f4c
v63.3.0
Compare Source
Changes
^^^^^^^
129480b
, including substantial delinting and cleanup, some refactoring around compiler logic, better messaging in cygwincompiler (pypa/distutils#161).v63.2.0
Compare Source
Changes
^^^^^^^
setuptools.build_meta
no longer triesto :func:
compile
the setup script code before :func:exec
-ing it.Misc
^^^^
v63.1.0
Compare Source
Changes
^^^^^^^
152c13d
including pypa/distutils#155 (improved compatibility for editable installs on homebrew Python 3.9), pypa/distutils#150 (better handling of runtime_library_dirs on cygwin), and pypa/distutils#151 (remove warnings for namespace packages).v63.0.0
Compare Source
Breaking Changes
^^^^^^^^^^^^^^^^
fetch_build_eggs
).Documentation changes
^^^^^^^^^^^^^^^^^^^^^
jacalata
file_finders
hook so thatthe logging recommendation aligns with the suggestion to not use
distutils
directly.keywords
to point to the Core Metadata Specificationinstead of PEP 314 (the live standard is kept always up-to-date and
consolidates several PEPs together in a single document).
codeandfire
v62.6.0
Compare Source
Changes
^^^^^^^
file:
for requirements in setup.cfg -- by :user:akx
(this feature is currently considered to be in beta stage).
file:
for dependencies and optional-dependencies in pyproject.toml -- by :user:akx
(this feature is currently considered to be in beta stage).
attr:
to also extract simple constants with type annotations -- by :user:karlotness
v62.5.0
Compare Source
Changes
^^^^^^^
pyproject.toml
configuration:now
[project]
is a fully supported configuration interface, but the[tool.setuptools]
tableand sub-tables are still considered to be in beta stage.
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
#3368: Added documentation page about extension modules -- by :user:
mkoeppe
#3371: Moved documentation from
/userguide/commands
to/depracted/commands
.This change was motived by the fact that running
python setup.py
directly isconsidered a deprecated practice.
#3372: Consolidated sections about
sdist
contents andMANIFEST.in
into a single page.Added a simple
MANIFEST.in
example.#3373: Moved remarks about using :pypi:
Cython
to the newly created page forextension modules.
#3374: Added clarification that using
python setup.py egg_info
commands tomanage project versions is only supported in a transitional basis, and
that eventually
egg_info
will be deprecated.Reorganized sections with tips for managing versions.
#3378: Updated
Quickstart
docs to make it easier to follow for beginners.Misc
^^^^
pyproject.toml
files areintended for internal use only and that not part of the public API.
v62.4.0
Compare Source
Changes
^^^^^^^
isuruf
75ed79d
including reformat using black, fix for Cygwin support (pypa/distutils#139), and improved support for cross compiling (pypa/distutils#144 and pypa/distutils#145).Documentation changes
^^^^^^^^^^^^^^^^^^^^^
#3355: Changes to the User Guide's Entry Points page -- by :user:
codeandfire
#3361: Further minor corrections to the Entry Points page -- by :user:
codeandfire
#3363: Rework some documentation pages to de-emphasize
distutils
and the historyof packaging in the Python ecosystem. The focus of these changes is to make the
documentation easier to read for new users.
#3364: Update documentation about dependency management, removing mention to
the deprecated
dependency_links
and adding some small improvements.#3367: Extracted text about automatic resource extraction and the zip-safe flag
from
userguide/miscellaneous
todeprecated/resource_extraction
anddeprecated/zip_safe
.Extracted text about additional metadata files from
userguide/miscellaneous
into the existinguserguide/extension
document.
Updated
userguide/extension
to better reflect the status of thesetuptools project.
Removed
userguide/functionalities_rewrite
(a virtually empty part of thedocs).
v62.3.4
Compare Source
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
codeandfire
package_data
glob pattern matching for dotfiles -- by :user:comabrewer
package_dir
configuration.Misc
^^^^
v62.3.3
Compare Source
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
CHANGES.rst
-- by :user:codeandfire
codeandfire
codeandfire
Misc
^^^^
test_setup_install_includes_dependencies
to work with customPYTHONPATH
–- by :user:hroncok
v62.3.2
Compare Source
Misc
^^^^
v62.3.1
Compare Source
Misc
^^^^
namespace_packages
to raise an error instead ofwarning.
v62.3.0
Compare Source
Deprecations
^^^^^^^^^^^^
#3262: Formally added deprecation messages for
namespace_packages
.The methodology that uses
pkg_resources
andnamespace_packages
forcreating namespaces was already discouraged by the :doc:
setuptools docs </userguide/package_discovery>
and the:doc:
Python Packaging User Guide <PyPUG:guides/packaging-namespace-packages>
,therefore this change just make the deprecation more official.
Users can consider migrating to native/implicit namespaces (as introduced in
:pep:
420
).#3308: Relying on
include_package_data
to ensure sub-packages are automaticallyadded to the build wheel distribution (as "data") is now considered a
deprecated practice.
This behaviour was controversial and caused inconsistencies (#3260).
Instead, projects are encouraged to properly configure
packages
or usediscovery tools. General information can be found in :doc:
userguide/package_discovery
.Changes
^^^^^^^
**
) inpackage_data
. -- by :user:nullableVoidPtr
install_requires
(insetup.py
) anddependencies
(inpyproject.toml
) are specified.The configuration in
pyproject.toml
will take precedence oversetup.py
(in accordance with PEP 621). A warning was added to inform users.
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
#3307: Added introduction to references/keywords.
Added deprecation tags to test kwargs.
Moved userguide/keywords to deprecated section.
Clarified in deprecated doc what keywords came from distutils and which were added or changed by setuptools.
Misc
^^^^
pyparsing
to 3.0.8 to avoid problems withupcoming deprecation in Python 3.11.
importlib-metadata
.v62.2.0
Compare Source
Changes
^^^^^^^
a7cfb56
per pypa/distutils#138.Misc
^^^^
setup.cfg
examples used when testingsetuptools.config
.v62.1.0
Compare Source
Changes
^^^^^^^
5229dad
.Misc
^^^^
package_dir
obtained via auto-discovery.v62.0.0
Compare Source
Breaking Changes
^^^^^^^^^^^^^^^^
setup.py develop --user
install to the user site packages directory even if it is disabled in the current interpreter.Changes
^^^^^^^
ldaniluk
install_as_egg
-- by :user:delijati
Misc
^^^^
dist-info
command.readme
specified as dynamic inpyproject.toml
from being dynamically specified in
setup.py
.v61.3.1
Compare Source
Misc
^^^^
setupcfg_examples.txt
insdist
.setupcfg_examples.txt
prior torunning tests. By caching these files it should be possible to run the test suite
offline.
v61.3.0
Compare Source
Changes
^^^^^^^
trove-classifiers
to facilitate reproducibility.Misc
^^^^
pyproject.toml
validation viavalidate-pyproject
v0.7.1.the validation of
pyproject.toml
.This tool can be executed via
tox -e generate-validation-code
.v61.2.0
Compare Source
Changes
^^^^^^^
#3215: Ignored a subgroup of invalid
pyproject.toml
files that use the[project]
table to specify only
requires-python
(transitional)... warning::
Please note that future releases of setuptools will halt the build process
if a
pyproject.toml
file that does not match doc:the PyPA Specification <PyPUG:specifications/declaring-project-metadata>
is given.#3215: Updated
pyproject.toml
validation, as generated byvalidate-pyproject==0.6.1
.#3218: Prevented builds from erroring if the project specifies metadata via
pyproject.toml
, but uses other files (e.g.setup.py
) to complement it,without setting
dynamic
properly... important::
This is a transitional behaviour.
Future releases of
setuptools
may simply ignore externally set metadatanot backed by
dynamic
or even halt the build with an error.#3224: Merge changes from pypa/distutils@
e1d5c9b
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
pyproject.toml
example in Quickstart -- by :user:pablo-cardenas
.Misc
^^^^
optional-dependencies
is set inpyproject.toml
.v61.1.1
Compare Source
Misc
^^^^
setup.py install
.Note that calling
setup.py install
directly is still deprecated andwill be removed in future versions of
setuptools
.Please check the release notes for :ref:
setup_install_deprecation_note
.v61.1.0
Compare Source
Deprecations
^^^^^^^^^^^^
setuptools.convert_path
to an internal function that is not exposedas part of setuptools API.
Future releases of
setuptools
are likely to remove this function.Changes
^^^^^^^
#3202: Changed behaviour of auto-discovery to not explicitly expand
package_dir
for flat-layouts and to not use relative paths starting with
./
.#3203: Prevented
pyproject.toml
parsing from overwritingdist.include_package_data
explicitly set insetup.py
with defaultvalue.
#3208: Added a warning for non existing files listed with the
file
directive insetup.cfg
andpyproject.toml
.#3208: Added a default value for dynamic
classifiers
inpyproject.toml
whenfiles are missing and errors being ignored.
#3211: Disabled auto-discovery when distribution class has a
configuration
attribute (e.g. when the
setup.py
script containssetup(..., configuration=...)
). This is done to ensure extension-only packages createdwith
numpy.distutils.misc_util.Configuration
are not broken by the safeguard
behaviour to avoid accidental multiple top-level packages in a flat-layout.
.. note::
Users that don't set
packages
,py_modules
, orconfiguration
arestill likely to observe the auto-discovery behavior, which may halt the
build if the project contains multiple directories and/or multiple Python
files directly under the project root.
To disable auto-discovery please explicitly set either
packages
orpy_modules
. Alternatively you can also configure :ref:custom-discovery
.v61.0.0
Compare Source
Deprecations
^^^^^^^^^^^^
#3068: Deprecated
setuptools.config.read_configuration
,setuptools.config.parse_configuration
and other functions or classesfrom
setuptools.config
.Users that still need to parse and process configuration from
setup.cfg
canimport a direct replacement from
setuptools.config.setupcfg
, however thismodule is transitional and might be removed in the future
(the
setup.cfg
configuration format itself is likely to be deprecated in the future).Breaking Changes
^^^^^^^^^^^^^^^^
#2894: If you purposefully want to create an "empty distribution", please be aware
that some Python files (or general folders) might be automatically detected and
included.
Projects that currently don't specify both
packages
andpy_modules
in theirconfiguration and contain extra folders or Python files (not meant for distribution),
might see these files being included in the wheel archive or even experience
the build to fail.
You can check details about the automatic discovery (and how to configure a
different behaviour) in :doc:
/userguide/package_discovery
.#3067: If the file
pyproject.toml
exists and it includes projectmetadata/config (via
[project]
table or[tool.setuptools]
),a series of new behaviors that are not backward compatible may take place:
include_package_data
will be considered to beTrue
.pyproject.toml
file accordingto PEP 621 specification.
pyproject.toml
will take precedence over thosespecified in
setup.cfg
orsetup.py
.Changes
^^^^^^^
#2887: [EXPERIMENTAL] Added automatic discovery for
py_modules
andpackages
-- by :user:
abravalheri
.Setuptools will try to find these values assuming that the package uses either
the src-layout (a
src
directory containing all the packages or modules),the flat-layout (package directories directly under the project root),
or the single-module approach (an isolated Python file, directly under
the project root).
The automatic discovery will also respect layouts that are explicitly
configured using the
package_dir
option.For backward-compatibility, this behavior will be observed only if both
py_modules
andpackages
are not set.(Note: specifying
ext_modules
might also prevent auto-discover fromtaking place)
If setuptools detects modules or packages that are not supposed to be in the
distribution, please manually set
py_modules
andpackages
in yoursetup.cfg
orsetup.py
file.If you are using a flat-layout, you can also consider switching to
src-layout.
#2887: [EXPERIMENTAL] Added automatic configuration for the
name
metadata-- by :user:
abravalheri
.Setuptools will adopt the name of the top-level package (or module in the case
of single-module distributions), only when
name
is not explicitlyprovided.
Please note that it is not possible to automatically derive a single name when
the distribution consists of multiple top-level packages or modules.
#3066: Added vendored dependencies for :pypi:
tomli
, :pypi:validate-pyproject
.These dependencies are used to read
pyproject.toml
files and validate them.#3067: [EXPERIMENTAL] When using
pyproject.toml
metadata,the default value of
include_package_data
is changed toTrue
.#3068: [EXPERIMENTAL] Add support for
pyproject.toml
configuration(as introduced by :pep:
621
). Configuration parameters not covered bystandards are handled in the
[tool.setuptools]
sub-table.In the future, existing
setup.cfg
configurationmay be automatically converted into the
pyproject.toml
equivalent before taking effect(as proposed in #1688). Meanwhile users can use automated tools like
:pypi:
ini2toml
to help in the transition.Please note that the legacy backend is not guaranteed to work with
pyproject.toml
configuration.-- by :user:
abravalheri
#3125: Implicit namespaces (as introduced in :pep:
420
) are now considered by defaultduring :doc:
package discovery </userguide/package_discovery>
, whensetuptools
configuration and project metadata are added to thepyproject.toml
file.To disable this behaviour, use
namespaces = False
when explicitly settingthe
[tool.setuptools.packages.find]
section inpyproject.toml
.This change is backwards compatible and does not affect the behaviour of
configuration done in
setup.cfg
orsetup.py
.#3152: [EXPERIMENTAL] Added support for
attr:
andcmdclass
configurationsin
setup.cfg
andpyproject.toml
whenpackage_dir
is implicitlyfound via auto-discovery.
#3178: Postponed importing
ctypes
when hiding files on Windows.This helps to prevent errors in systems that might not have
libffi
installed.#3179: Merge with pypa/distutils@
267dbd2
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
setuptools
viapyproject.toml
(using standard project metadata).
Misc
^^^^
setuptools.config
by separating configuration parsing (specificto the configuration file format, e.g.
setup.cfg
) and post-processing(which includes directives such as
file:
that can be used across differentconfiguration formats).
v60.10.0
Compare Source
Changes
^^^^^^^
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
xhlulu
MANIFEST.in
, that include links to PyPUG docsand more prominent mentions to using a revision control system plugin as an
alternative.
pkg_resources
as the recommended way of accessing datafiles, in favour of importlib.resources.
Additionally more emphasis was put on the fact that package data files reside
inside the package directory (and therefore should be read-only).
Misc
^^^^
These tests now are marked with
XFAIL <https://docs.pytest.org/en/stable/how-to/skipping.html>
_, instead of erroringout directly.
rst-linker
(extension used to build thechangelog).
befeleme
setuptools
wheel or sdist for beingused during tests with virtual environments.
Paths for these pre-built distribution files can now be set via the environment
variables:
PRE_BUILT_SETUPTOOLS_SDIST
andPRE_BUILT_SETUPTOOLS_WHEEL
.v60.9.3
Compare Source
Misc
^^^^
v60.9.2
Compare Source
Misc
^^^^
__name__
to ensure consistent importing from inside and out.v60.9.1
Compare Source
Misc
^^^^
v60.9.0
Compare Source
Changes
^^^^^^^
pkg_resources
for entry point handling... warning:: Users trying to install the unmaintained :pypi:
pathlib
backportfrom PyPI/
sdist
/source code may find problems when usingsetuptools >= 60.9.0
.This happens because during the installation, the unmaintained
implementation of
pathlib
is loaded and may cause compatibility problems(it does not expose the same public API defined in the Python standard library).
Whenever possible users should avoid declaring
pathlib
as a dependency.An alternative is to pre-build a wheel for
pathlib
using a separatedvirtual environment with an older version of setuptools and install the
library directly from the pre-built wheel.
v60.8.2
Compare Source
Misc
^^^^
concurrent.futures
import lazy in vendoredmore_itertools
package to a avoid importing threading as a side effect (which caused
gevent/gevent#​1865 <https://github.com/gevent/gevent/issues/1865>
__).-- by :user:
maciejp-ro
v60.8.1
Compare Source
Misc
^^^^
v60.8.0
Compare Source
Changes
^^^^^^^
v60.7.1
Compare Source
Misc
^^^^
v60.7.0
Compare Source
Changes
^^^^^^^
Misc
^^^^
v60.6.0
Compare Source
Changes
^^^^^^^
bb018f1
including consolidated behavior in sysconfig.get_platform (pypa/distutils#104).Home-page
in metadata if nourl
is specified. -- by :user:cdce8p
b53a824
including improved support for lib directories on non-x64 Windows builds.Documentation changes
^^^^^^^^^^^^^^^^^^^^^
setuptools.build_meta
in a in-treecustom backend. This is a :pep:
517
-compliant way of dynamically specifyingbuild dependencies (e.g. when platform, OS and other markers are not enough).
-- by :user:
abravalheri
to GitHub Discussions.
-- by :user:
ashemedai
wheel
to:pep:
517
requirements -- by :user:webknjaz
Misc
^^^^
super().__init__()
-- by :user:imba-tjd
v60.5.0
Compare Source
Changes
^^^^^^^
.origin
attribute of thedistutils
module to the module's__file__
.v60.4.0
Compare Source
Changes
^^^^^^^
requires
sorting when installing wheels as an egg dir.costly modules in
_distutils_hack
-- by :user:tiran
Documentation changes
^^^^^^^^^^^^^^^^^^^^^
sphinx-favicon
.scour
package.
Misc
^^^^
#2862: Added integration tests that focus on building and installing some packages in
the Python ecosystem via
pip
-- by :user:abravalheri
#2952: Modified "vendoring" logic to keep license files.
#2968: Improved isolation for some tests that where inadvertently using the project
root for builds, and therefore creating directories (e.g.
build
,dist
,*.egg-info
) that could interfere with the outcome of other tests-- by :user:
abravalheri
.#2968: Introduced new test fixtures
venv
,venv_without_setuptools
,bare_venv
that rely on thejaraco.envs
package.These new test fixtures were also used to remove the (currently problematic)
dependency on the
pytest_virtualenv
plugin.#2968: Removed
tmp_src
test fixture. Previously this fixture was copying all thefiles and folders under the project root, including the
.git
directory,which is error prone and increases testing time.
Since
tmp_src
was used to populate virtual environments (installing theversion of
setuptools
under test via the source tree), it was replaced bythe new
setuptools_sdist
andsetuptools_wheel
fixtures (that are buildonly once per session testing and can be shared between all the workers for
read-only usage).
v60.3.1
Compare Source
Misc
^^^^
v60.3.0
Compare Source
Changes
^^^^^^^
Misc
^^^^
788cc15
. Includes fix for config vars missing from sysconfig.v60.2.0
Compare Source
Changes
^^^^^^^
distutils.log.*
, uselogging.getLogger(name).*
.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.