Skip to content

Conversation

@Soares
Copy link
Contributor

@Soares Soares commented Apr 24, 2017

I think I followed the backporting instructions at https://docs.python.org/devguide/committing.html?highlight=backport correctly, but this is my first time, so please let me know if I erred, as is fairly likely.

Nate added 2 commits April 24, 2017 16:29
…#527)

Many metaclasses in the standard library don't play nice with
__init_subclass__. This bug makes ABCMeta in particular with
__init_subclass__, which is an 80/20 solution for me personally.
AFAICT, a general solution to this problem requires updating all
metaclasses in the standard library to make sure they pass **kwargs to
type.__new__, whereas this PR only fixes ABCMeta. For context, see
https://bugs.python.org/issue29581.

* added a test combining ABCMeta and __init_subclass__
* Added NEWS item

(cherry picked from commit bd583ef)
…ythonGH-527)

Many metaclasses in the standard library don't play nice with
__init_subclass__. This bug makes ABCMeta in particular with
__init_subclass__, which is an 80/20 solution for me personally.
AFAICT, a general solution to this problem requires updating all
metaclasses in the standard library to make sure they pass **kwargs to
type.__new__, whereas this PR only fixes ABCMeta. For context, see
https://bugs.python.org/issue29581.

* added a test combining ABCMeta and __init_subclass__
* Added NEWS item.
(cherry picked from commit bd583ef)
@Soares
Copy link
Contributor Author

Soares commented Apr 24, 2017

I'm also planning to backport PR #678, which depends on this backport (of PR #527). I assume that I shouldn't begin that backport until this one is accepted, but let me know if I can begin the backport of #678 now.

@vstinner
Copy link
Member

There is an issue on the Misc/NEWS merge :-/

@Soares
Copy link
Contributor Author

Soares commented Apr 25, 2017

Oops. I don't see an easy way to fix this using the cherry_picker tool, so I'm going to abandon this PR and make a new one (merging correctly) this time, unless you object.

Also, I note that there's a "No issue number in the title or "trivial" label" problem listed in 'checks'. Do you want me to add the issue label of the original issue (for which this is a backport), or stick with the auto-generated backport PR name?

@ncoghlan ncoghlan closed this Apr 25, 2017
@ncoghlan
Copy link
Contributor

@Soares The preferred format for backport PR titles is "[X.Y] bpo-NNNNN: ...", where X.Y is the target branch and NNNNN is the bugs.python.org issue number

@serhiy-storchaka serhiy-storchaka added type-bug An unexpected behavior, bug, or error cherry-pick for 3.6 labels Apr 25, 2017
@Soares Soares deleted the backport-bd583ef-3.6 branch April 25, 2017 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type-bug An unexpected behavior, bug, or error

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants