Skip to content

Change the python/ directory related warnings to errors#1830

Merged
edmorley merged 1 commit into
mainfrom
checks-python-dir-error
Jul 10, 2025
Merged

Change the python/ directory related warnings to errors#1830
edmorley merged 1 commit into
mainfrom
checks-python-dir-error

Conversation

@edmorley

Copy link
Copy Markdown
Member

Builds will now error if either:

  • The Python buildpack has been run multiple times in the same build.
  • An existing .heroku/python/ directory is found in the app source for any other reason (e.g. accidentally committed to Git)

This upgrades the warnings added in #1724 in December 2024 to errors.

No feedback/concerns were raised in the GitHub issue linked from the warning:
#1704

And Honeycomb data shows:

  • the number of apps hitting the warnings was minimal
  • in most cases, the builds hitting the warnings were failing already (eg due to broken python/ directories having been committed to Git, and so turning the warning into an error will actually give them a better error message than before).

Closes #1704.
GUS-W-17309720.

@edmorley edmorley self-assigned this Jul 10, 2025
@edmorley edmorley marked this pull request as ready for review July 10, 2025 13:50
@edmorley edmorley requested a review from a team as a code owner July 10, 2025 13:50
@edmorley edmorley enabled auto-merge (squash) July 10, 2025 13:50
@edmorley edmorley disabled auto-merge July 10, 2025 13:54
Builds will now error if either:
- The Python buildpack has been run multiple times in the same build.
- An existing `.heroku/python/` directory is found in the app source
  for any other reason (e.g. accidentally committed to Git)

This upgrades the warnings added in #1724 in December 2024
to errors.

No feedback/concerns were raised in the GitHub issue
linked from the warning:
#1704

And Honeycomb data shows:
- the number of apps hitting the warnings was minimal
- in most cases, the builds hitting the warnings were failing
  already (eg due to broken `python/` directories having been
  committed to Git, and so turning the warning into an error
  will actually give them a better error message than before).

Closes #1704.
GUS-W-17309720.
@edmorley edmorley force-pushed the checks-python-dir-error branch from 7ca77c3 to 45053f5 Compare July 10, 2025 13:54
@edmorley edmorley enabled auto-merge (squash) July 10, 2025 13:54
@edmorley edmorley merged commit d124912 into main Jul 10, 2025
6 checks passed
@edmorley edmorley deleted the checks-python-dir-error branch July 10, 2025 14:11
@heroku-linguist heroku-linguist Bot mentioned this pull request Jul 10, 2025
edmorley added a commit that referenced this pull request Jul 14, 2025
These are not set/used since #1830.
edmorley added a commit that referenced this pull request Jul 15, 2025
These are not set/used since #1830.
edmorley added a commit that referenced this pull request Jul 18, 2025
After #1830, the two `checks::warn_if_*` functions now error
rather than warn, so the function names have been renamed
to match the behaviour.
edmorley added a commit that referenced this pull request Jul 18, 2025
After #1830, the two `checks::warn_if_*` functions now error
rather than warn, so the function names have been renamed
so they don't mislead about their behaviour.
edmorley added a commit that referenced this pull request Jul 18, 2025
After #1830, the two `checks::warn_if_*` functions now error
rather than warn, so the function names have been renamed
so they don't mislead about their behaviour.
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.

Error if the Python buildpack has been run multiple times during the same build

2 participants