Skip to content
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

update how WAKEPY_FAKE_SUCCESS works - only affects Modes #261

Merged
merged 18 commits into from
Apr 21, 2024

Conversation

fohrloop
Copy link
Owner

@fohrloop fohrloop commented Apr 21, 2024

  • Checking WAKEPY_FAKE_SUCCESS env variable is only done in Mode._activate. If that is set to truthy value, insert the
    WakepyFakeSuccess method to the start of the methods list. This means that any Mode is quaranteed to be succesful with
    WAKEPY_FAKE_SUCCESS, but there's no guarantee for any particular Method (using Methods separately is not part of the public API of wakepy, so this does not matter)
  • WakepyFakeSuccess Method now always succeeds
  • Always prioritize WAKEPY_FAKE_SUCCESS method to be the first, if it is used.
  • Add 'N', 'F' and the empty string to the list of falsy values. (previously just '0', 'False', and 'no')
  • Update WAKEPY_FAKE_SUCCESS docs.

@fohrloop fohrloop merged commit 65bdc1f into dev Apr 21, 2024
12 checks passed
@fohrloop fohrloop changed the title Wakepy fake success update update how WAKEPY_FAKE_SUCCESS works - only affects Modes Apr 21, 2024
@fohrloop fohrloop deleted the wakepy-fake-success-update branch April 21, 2024 12:51
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.

1 participant