Fixes issue #1427

[redruin1]

Summary

Values given to __init__ should now always be propagated to __attrs_pre_init__, regardless of default configuration. Resolves #1427.

Pull Request Check List

• Do not open pull requests from your main branch – use a separate branch!
• Added tests for changed code.
• New features have been added to our Hypothesis testing strategy.
• Changes or additions to public APIs are reflected in our type stubs (files ending in .pyi).
  • ...and used in the stub test file tests/typing_example.py.
  • If they've been added to attr/__init__.pyi, they've also been re-imported in attrs/__init__.pyi.
• Updated documentation for changed code.
  • New functions/classes have to be added to docs/api.rst by hand.
  • Changes to the signatures of @attr.s() and @attrs.define() have to be added by hand too.
  • Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.
    The next version is the second number in the current release + 1.
    The first number represents the current year.
    So if the current version on PyPI is 22.2.0, the next version is gonna be 22.3.0.
    If the next version is the first in the new year, it'll be 23.1.0.
    • If something changed that affects both attrs.define() and attr.s(), you have to add version directives to both.
• Documentation in .rst and .md files is written using semantic newlines.
• Changes (and possible deprecations) have news fragments in changelog.d.
• Consider granting push permissions to the PR branch, so maintainers can fix minor issues themselves without pestering you.

[redruin1]

@hynek Is there anything more I need to do on this PR, or is this not considered a bug?

[hynek]

hey @redruin1 sorry for letting you hang; I've currently too many fires everywhere and am procrastinating to attack the whole pile within attrs. I swear I feel bad and will get around to it!

[hynek]

Thanks, that was indeed straight-forward! 🙈