delta/python-setuptools-git.git/setuptools/command, branch v60.0.2 github.com: pypa/setuptools.git Select 'posix_user' for the scheme unless falling back to stdlib, then use 'unix_user'. Fixes #2938. 2021-12-20T21:43:46+00:00 Jason R. Coombs jaraco@jaraco.com 2021-12-20T21:43:07+00:00 edf116b1cc4a72075b9af06748df3b177d55d4dc 






Add fallback support for distutils in stdlib.
2021-12-20T17:01:37+00:00

Jason R. Coombs
jaraco@jaraco.com

2021-12-20T17:01:37+00:00

60b78468341d52bc033f0ad77e890a656ccb9a72












In easy_install, re-use scheme selection from distutils if available.
2021-12-20T16:50:50+00:00

Jason R. Coombs
jaraco@jaraco.com

2021-12-20T16:50:50+00:00

76c9ab9efc3f13e5ef8681614bebbe437bf51012












Update setuptools.readthedocs.io to setuptools.pypa.io
2021-11-16T11:05:23+00:00

Hugo van Kemenade
hugovk@users.noreply.github.com

2021-11-16T11:05:23+00:00

a65c4326c788cd9f6a81eb1754029751500f7721












Use warning instead of log for distutils command
2021-11-05T14:14:29+00:00

Anderson Bravalheri
andersonbravalheri@gmail.com

2021-11-05T14:14:29+00:00

e2220331136c3a60b8d70a6b4eaad05816c9b637

As discussed in #2855, using an actual warning instead of the logger
allow users to control what gets displayed via warning filters.





As discussed in #2855, using an actual warning instead of the logger
allow users to control what gets displayed via warning filters.







Handle custom build_py inheriting from distutils
2021-11-04T13:08:16+00:00

Anderson Bravalheri
andersonbravalheri@gmail.com

2021-11-04T12:30:37+00:00

08235e88d10179c89ed80a4dd9bf2d18c76b478d

According to #2849, some projects, including important data-science
packages rely on `distutils` when creating custom commands, instead of
extending the ones provided by setuptools.

This change should accomodate this use case, while also warning the
users to migrate.





According to #2849, some projects, including important data-science
packages rely on `distutils` when creating custom commands, instead of
extending the ones provided by setuptools.

This change should accomodate this use case, while also warning the
users to migrate.







Remove data_files avoidance code.
2021-11-03T01:39:32+00:00

Jason R. Coombs
jaraco@jaraco.com

2021-11-03T01:08:01+00:00

b8ad7d2ca1abc59e42e63ecf484036d021a2e19c












Reformat docstring and rewrite in imperative voice.
2021-11-03T01:39:32+00:00

Jason R. Coombs
jaraco@jaraco.com

2021-11-03T00:54:51+00:00

2d38be3259311220d069996b3a906f171dfddafc












Fix 1461: Better loop breaker for `manifest_maker`
2021-11-01T20:50:58+00:00

Anderson Bravalheri
andersonbravalheri@gmail.com

2021-11-01T19:47:33+00:00

2e66eb7147ae1e8a799b2276c7340f48f63a7220

The inconsistency for the `package_data` configuration in sdists
when `include_package_data=True` in #1461 have been causing some
problems for the community for a while, as also shown in #2835.

As pointed out by
[@jaraco](https://github.com/pypa/setuptools/issues/1461#issuecomment-749092366),
this was being caused by a mechanism to break the recursion between the
`egg_info` and `sdist` commands.

In summary the loop is caused by the following behaviour:

- the `egg_info` command uses a subclass of `sdist` (`manifest_maker`)
  to calculate the MANIFEST,
- the `sdist` class needs to know the MANIFEST to calculate the data files when
  `include_package_data=True`

Previously, the mechanism to break this loop was to simply ignore
the data files in `sdist` when `include_package_data=True`.

The approach implemented in this change was to replace this mechanism,
by allowing `manifest_maker` to override the `_safe_data_files` method
from `sdist`.

---

Please notice [an extensive experiment]
(https://github.com/abravalheri/experiment-setuptools-package-data)
was carried out to investigate the previous confusing behaviour.

There is also [a simplified theoretical analysis]
(https://github.com/pyscaffold/pyscaffold/pull/535#issuecomment-956296407)
comparing the observed behavior in the experiment and the expected
one. This analysis point out to the same offender indicated by
[@jaraco](https://github.com/pypa/setuptools/issues/1461#issuecomment-749092366)
(which is being replaced in this change).





The inconsistency for the `package_data` configuration in sdists
when `include_package_data=True` in #1461 have been causing some
problems for the community for a while, as also shown in #2835.

As pointed out by
[@jaraco](https://github.com/pypa/setuptools/issues/1461#issuecomment-749092366),
this was being caused by a mechanism to break the recursion between the
`egg_info` and `sdist` commands.

In summary the loop is caused by the following behaviour:

- the `egg_info` command uses a subclass of `sdist` (`manifest_maker`)
  to calculate the MANIFEST,
- the `sdist` class needs to know the MANIFEST to calculate the data files when
  `include_package_data=True`

Previously, the mechanism to break this loop was to simply ignore
the data files in `sdist` when `include_package_data=True`.

The approach implemented in this change was to replace this mechanism,
by allowing `manifest_maker` to override the `_safe_data_files` method
from `sdist`.

---

Please notice [an extensive experiment]
(https://github.com/abravalheri/experiment-setuptools-package-data)
was carried out to investigate the previous confusing behaviour.

There is also [a simplified theoretical analysis]
(https://github.com/pyscaffold/pyscaffold/pull/535#issuecomment-956296407)
comparing the observed behavior in the experiment and the expected
one. This analysis point out to the same offender indicated by
[@jaraco](https://github.com/pypa/setuptools/issues/1461#issuecomment-749092366)
(which is being replaced in this change).







Deprecate setup.py install and easy_install. Ref #917.
2021-10-22T19:27:51+00:00

Jason R. Coombs
jaraco@jaraco.com

2021-10-22T19:27:51+00:00

fc5c3083908170e1cbfd1dec91f87a3e2707e3fa