Document the new ivy resolution behaviour #2297
Comments
Eric-Arellano
pushed a commit
that referenced
this issue
Aug 16, 2020
https://github.com/pypa/setuptools/releases/tag/v49.6.0 https://github.com/pypa/setuptools/blob/master/CHANGES.rst * #2129: In pkg_resources, no longer detect any pathname ending in .egg as a Python egg. Now the path must be an unpacked egg or a zip file. * #2306: When running as a PEP 517 backend, setuptools does not try to install ``setup_requires`` itself. They are reported as build requirements for the frontend to install. * #2310: Updated vendored packaging version to 20.4. * #2300: Improve the ``safe_version`` function documentation * #2297: Once again, in stubs prefer exec_module to the deprecated load_module. * #2316: Removed warning when ``distutils`` is imported before ``setuptools`` when ``distutils`` replacement is not enabled. * #2259: Setuptools now provides a .pth file (except for editable installs of setuptools) to the target environment to ensure that when enabled, the setuptools-provided distutils is preferred before setuptools has been imported (and even if setuptools is never imported). Honors the SETUPTOOLS_USE_DISTUTILS environment variable. pypa/setuptools#2257: Fixed two flaws in distutils._msvccompiler.MSVCCompiler.spawn. instead of #10561 [ci skip-build-wheels]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The new ivy resolution behaviour has some excellent-but-occasionally surprising effects on behaviour and correctness.
Having explained the new behaviour to a few folks, it would be good to get that same explanation in the documentation.
The text was updated successfully, but these errors were encountered: