Move more packages to the new primer

[DanielNoord]

• Add yourself to CONTRIBUTORS if you are a new contributor.
• Write a good description on what the PR does.

Type of Changes

	Type
✓	🔨 Refactoring

Description

I'll remove the empty file when we can remove the old primer as removing now requires additional refactors.

[coveralls]

Pull Request Test Coverage Report for Build 2410153713

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 95.516%

---

Totals
Change from base Build 2409548505:	0.0%
Covered Lines:	16230
Relevant Lines:	16992

---

💛 - Coveralls

[DanielNoord]

@jacobtylerwalls This is running into CI time-outs. See main.

I don't really understand as this batch of packages passed on my local branch in CI and locally. Does this pass in reasonable time for you locally?

[jacobtylerwalls]

Make sure to try with bleeding-edge astroid, it has good nutrients :D

[DanielNoord]

Make sure to try with bleeding-edge astroid, it has good nutrients :D

Does bleeding-edge fail with these packages? 😢

[jacobtylerwalls]

Well, I'm waiting to find out. It takes a long time to lint home-assistant! How long does it take on your system?

[DanielNoord]

I got 21m in CI here:
https://github.com/DanielNoord/pylint/runs/6657709454?check_suite_focus=true
Note that that is with:
DanielNoord@e739427

I removed keras, Django and music21 for this PR as they all crashed due to the importlib issue.

[jacobtylerwalls]

@DanielNoord the other thing I can think of is the message dict might be huge. Could we write the message dict and flush it as each package is linted, rather than writing it out after all packages? This will also help with debugging.

[DanielNoord]

Now that I look at that workflow again I see that we never actually go beyond keras. So it was probably broken as well, but just failed prematurely. I didn't recognise that correctly... Sorry!

@DanielNoord the other thing I can think of is the message dict might be huge. Could we write the message dict and flush it as each package is linted, rather than writing it out after all packages? This will also help with debugging.

Yeah that should be do-able.
The only thing we need to take care of is writing { before the first package , after each package and } after the last package to make the final output a valid JSON dictionary.

I was actually planning on shutting down for the night. If you want feel free to take a stab at this or just revert this PR so main gets unblocked. I think I won't get to this before tomorrow evening (+24h from now).

[jacobtylerwalls]

Woo hoo! The issue with pandas is fixed at pylint-dev/astroid#1579.