Skip to content

Remove warning about packages not containing __init__.py files #151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 1, 2022

Conversation

abravalheri
Copy link
Contributor

Originally distutils implementation did not account for PEP 420 and included warns for package directories that did not contain __init__.py files.

After the acceptance of PEP 420, these warnings don't make more sense and sometimes can confuse users.
Recently this was pointed out in one of setuptools discussions: pypa/setuptools#3353 (reply in thread).

This PR removes the warning (and adds a test capturing the expectation).

Since the only change is a warning removal, this can be seen as a "progressive enhancement" over the versions of distutils existing in the standard library:

  • Users that run setuptools using SETUPTOOLS_USE_DISTUTILS=stdlib will still see the warning, but the build will not fail or change in terms of outcome
  • Users that run setuptools without the fallback will benefit from not seeing the outdated warning

@abravalheri abravalheri marked this pull request as ready for review June 10, 2022 21:07
@jaraco jaraco merged commit 763c440 into pypa:main Jul 1, 2022
@abravalheri abravalheri deleted the remove-warning branch July 4, 2022 12:19
netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this pull request Jul 6, 2022
v63.1.0

Changes

Merge with pypa/distutils@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

Breaking Changes

Drop setuptools' support for installing an entrypoint extra requirements at load time: - the functionality has been broken since v60.8.0. - the mechanism to do so is deprecated (fetch_build_eggs). - that use case (e.g. a custom command class entrypoint) is covered by making sure the necessary build requirements are declared.

Documentation changes

Updated the example pyproject.toml -- by :user:`jacalata`
This updates the documentation for the file_finders hook so that the logging recommendation aligns with the suggestion to not use distutils directly.
Fix reference for keywords to point to the Core Metadata Specification instead of PEP 314 (the live standard is kept always up-to-date and consolidates several PEPs together in a single document).
Reordered the User Guide's Table of Contents
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants