Pierre Sassoulas

The thing I had in mind was to make ``astroid.nodes`` (or astroid) the entrypoint to import everything and to make ``node_classes`` and ``scoped_nodes`` private. What your suggesting is to use...

Thank you for creating the issue :)

@cdce8p do you think you'll have time to review this ? I see you self requested a review two months ago. I'm trying to release astroid 2.10 :)

Thank you for opening the issue, I agree with everything you said. I would add that making astroid performance better would save gigawatt of electricity. What I'm saying it that...

I'm clearing the milestone so we can release astroid 2.10, this is not strictly necessary.

Yeah, the new release don't need to be perfect, only better than the old one (often it's slower because we added checks). We have a blocker on pylint right now...

Don't panic, there's enough issues for everyone 😄

@ewerybody seeing how in-depth you looked into the problem (thank you!) I'm confident you're one of the most qualified to handle it now. In particular [the piece of code that...

I think you can start by fixing the parsing in astroid by creating a test checking the result of ``astroid.parse(code)``. You will need a new version of astroid released in...

I think we should introduce aliases to match what the ``ast`` does (without changing the API we have, only adding aliases), what do you think @hippo91 ?