Jacob Walls

Hi @xi this dropped under the radar because the ticket still was flagged as _Needs documentation_. Now that 4.1 is released, it would be helpful if you could update the...

> do we have any update on review or merging of this PR. If this is ready for re-review, the ticket should be updated to remove the "Needs ..." flags...

From discussion on a recent astroid PR: > There's two issues left in 2.12, including this one that is mergeable, should we even release 2.11.7 ? @Pierre-Sassoulas fine with me...

Regarding PyCQA/astroid#1189 I reread Marc's review comment,and he refers to intending to do a "subsequent" review, so I'm wondering if we're better off releasing 2.12 right now and getting on...

> Fine with me if we don't find the time to review it. It introduces the concept of _explicit_instance_attrs which is something we should probably think carefully about. Yeah, let's...

@DanielNoord Up for a `2.12.1`?

Ring ring! What do you say, is it release time? :bell: I think we should bump everything (and I mean everything) that's not already got an approving review to the...

> Seems like the only MR that needed an astroid update in 2.15.0 is https://github.com/PyCQA/pylint/pull/7333 That makes sense, since we're just going from patch to patch.

Hi @vapier thanks for the inquiry. This predates my involvement by a lot, but the blame tells me this is intentional since at least #219.

Thanks, I was having trouble understanding what you meant by "registered as an importable module." Do you mean `import-self` should not be emitted? (And not that the entire file should...