Bump setuptools from 1.0.0 to 49.2.1

[dependabot-preview]

Bumps setuptools from 1.0.0 to 49.2.1.

Changelog

Sourced from setuptools's changelog.

v49.2.1

• #2257: Fixed two flaws in distutils._msvccompiler.MSVCCompiler.spawn.

v49.2.0

• #2230: Now warn the user when setuptools is imported after distutils modules have been loaded (exempting PyPy for 3.6), directing the users of packages to import setuptools first.

v49.1.3

• #2212: (Distutils) Allow spawn to accept environment. Avoid monkey-patching global state.
• #2249: Fix extension loading technique in stubs.

v49.1.2

• #2232: In preparation for re-enabling a local copy of distutils, Setuptools now honors an environment variable, SETUPTOOLS_USE_DISTUTILS. If set to 'stdlib' (current default), distutils will be used from the standard library. If set to 'local' (default in a imminent backward-incompatible release), the local copy of distutils will be used.

v49.1.1

• #2094: Removed pkg_resources.py2_warn module, which is no longer reachable.

v49.0.1

• #2228: Applied fix for command.build_ext raises FileNotFoundError pypa/distutils#3, restoring expectation that spawn will raise a DistutilsExecError when attempting to execute a missing file.

v49.1.0

• #2228: Disabled distutils adoption for now while emergent issues are addressed.

v49.0.0

• #2165: Setuptools no longer installs a site.py file during easy_install or develop installs. As a result, .eggs on PYTHONPATH will no longer take precedence over other packages on sys.path. If this issue affects your production environment, please reach out to the maintainers at #2165.
• #2137: Removed (private) pkg_resources.RequirementParseError, now replaced by packaging.requirements.InvalidRequirement. Kept the name for compatibility, but users should catch InvalidRequirement instead.
• #2180: Update vendored packaging in pkg_resources to 19.2.
• #2199: Fix exception causes all over the codebase by using raise new_exception from old_exception

v48.0.0

• #2143: Setuptools adopts distutils from the Python 3.9 standard library and no longer depends on distutils in the standard library. When importing setuptools or setuptools.distutils_patch, Setuptools will expose its bundled version as a top-level distutils package (and unload any previously-imported top-level distutils package), retaining the expectation that distutils' objects are actually Setuptools objects. To avoid getting any legacy behavior from the standard library, projects are advised to always "import setuptools" prior to importing anything from distutils. This behavior happens by default when using pip install or pep517.build. Workflows that rely on setup.py (anything) will need to first ensure setuptools is imported. One way to achieve this behavior without modifying code is to invoke Python thus: python -c "import setuptools; exec(open('setup.py').read())" (anything).

v47.3.2

Commits

• d3e754f Bump version: 49.2.0 → 49.2.1
• a83d96e Add changelog. Ref #2257.
• c2fcb01 Merge branch 'clean' of https://github.com/pypa/distutils into master
• 51b75e9 Merge pull request #8 from pypa/bugfix/tests-for-msvc-spawn
• 616e129 In _msvccompiler.MSVCCompiler.spawn, use correct capitalization for PATH envi...
• 0bb6c6b In CCompiler, allow keyword arguments to be passed to spawn calls. Ref pypa/s...
• 39b30e1 In TestSpawn.test_concurrent_safe, use CheckThread to ensure that the spawn c...
• 7f23397 Add a unit test for testing spawn. Ref pypa/distutils#5.
• 1215561 Suppress ImportError for winreg as the module is only available on some platf...
• 5578b44 Merge pull request #2291 from hugovk/patch-1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #504.