Skip to content

addini: allow for default=None, use notset sentinel#6118

Closed
blueyed wants to merge 1 commit intopytest-dev:featuresfrom
blueyed:upstream-addinit-default-unset
Closed

addini: allow for default=None, use notset sentinel#6118
blueyed wants to merge 1 commit intopytest-dev:featuresfrom
blueyed:upstream-addinit-default-unset

Conversation

@blueyed
Copy link
Contributor

@blueyed blueyed commented Nov 1, 2019

Fixes #6117.

@blueyed
Copy link
Contributor Author

blueyed commented Nov 2, 2019

As per #6117 this might change behavior, closing for now.

@blueyed blueyed closed this Nov 2, 2019
@blueyed blueyed deleted the upstream-addinit-default-unset branch November 2, 2019 07:38
@nicoddemus
Copy link
Member

TBH I think we should reopen and go for this in the next minor release... I don't think it will cause too much breakage, and the new behavior is much more sane and seems to me is fixing an annoying wart that was included as an oversight.

If people are really concerned, I still would like to see this in 6.0 at least, but I'm not sure how to properly warn on this given that the problem is the return value.

cc @RonnyPfannschmidt?

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.

2 participants