Remove support for auto-brightness #6734
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #5476 by removing
auto_brightness
and related support completely.@deshipu @tannewt My understanding of the comments in #5476, particularly the later ones, is that auto-brightness never worked, and we may as well just remove it, which is what I proposed in that issue. If this is not correct, then I'll close or change this.
This PR explicitly removes the
.auto_brightness
attribute onDisplay
andFrameBufferDisplay
. It does not just render it inoperable in 8.0.0, to be removed in 9.0.0. I could do such a staged removal if you think it advisable.I found about five boilerplate references to
.auto_brightness
in the Learn Guide repo, and about three in the libraries, all of which could easily be handled.@deshipu There are also a couple of mentions of
.auto_brightness
incircuitpython-stage
. Before this PR is merged, those would need to be removed and I would update the frozen submodule.