Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

The instruction says:

Trivial changes, like fixing a typo, do not need an issue.

I think this fix is obvious and trivial enough that an extra issue is overkill.

We need issues for actual bugs. They aren't needed for things like documentation changes.

I don't know what should be put in the issue body.

The original code is a bad design and may cause an issue if someone extends the _Extra class, but it does not cause an actual bug so far as _Extra is only used internally.

The original code is a bad design and may cause an issue if someone extends the _Extra class, but it does not cause an actual bug so far as _Extra is only used internally.

Not disagreeing, but in practice, people will just fix that on the fly. It's typically not worth it to prematurely fix internal APIs.

I'm going to leave this one up to @jaraco who wrote the code.

Closing, no issue has been created.

@jaraco Did you intend to write the code in this way? Is there any special reason?

It looks like a mistake, and if it really is, I can raise an issue and PR for it.