This is awkward... I may be biased, but I prefer my #307 PR, which also includes the migrations but with dynamic version (based on cpplint.py) and dependencies (based on the dependency listing files). (I also read in pytest docs that they prefer storing settings in .pytest.ini so that's what I did.)

My PR would also automatically use the newest Python. (I also don't see reason to drop EOL Python versions for no reason; I think we should only drop it when something becomes an issue. And by "issue" I mean things like the EOL 3.7 not having the walrus operator.)

I also don't see reason to drop EOL.

Sorry about that, I've realized the issue now: newer versions of Pylint you need don't support 3.9. So I support bumping minimum to 3.9 now.

I believe we should all push projects to not build on foundations that no longer receive security updates.

Please cherry pick anything that is interesting here and put it in #307 and we can land that and close this.

I may be biased, but I prefer my #307 PR

You create pull requests under one username and review pull requests on the same repository under a different username? Seems duplicitous.

You create pull requests under one username and review pull requests on the same repository under a different username? Seems duplicitous.

I accidentally merged a PR that broke everything once; I started a PR to fix that. As @jayvdb (the only other active maintainer) is not active and the PR sat for weeks, I started doing that and jayvdb doesn't seem to mind.

I accidentally merged a PR that broke everything once

This is not something that happened just once. I find a repeated duplicitous and dangerous pattern of eight pull requests created by @norab0130 and approved and merged by @aaronliu0130 when the same person controls both accounts.

• Fix protobuf clitest #270
• Update documentation about PRs (& upd changelog) #274
• Add support for [[likely]], misc brace bugfixes, and drop support for Python 3.8 #277
• Update silly-sample + gitignore vscode (#253) #285
• Fix reading from stdin #289
• Disable "too-many-positional-arguments" #290
• Cache cppvar to improve performance #291
• Fix false positive for indented parameters in namespaces #304

This repeated pattern intentionally circumvents the supply chain security policy of this repo that a maintainer who is not the author reviews and approves every pull request before it is merged. This policy is standard for Google and most other widely installed software tools. If anyone thinks this is not a problem, they are not paying enough attention to software supply chain security issues.

The code in this repo is not owned by one person but is instead the work of many that needs to be treated safely and with respect. If a maintainer is not paying enough attention to review pull requests on widely deployed production code, then one or more new maintainers must be added to the project.

Actions: I have the commit-bit for my previous work on this repo.

1. I will close the three open PRs created by @norab0130. I ask that this user not create any new pull requests on this repo. This is done out of an abundance of caution given the circumvention of the security policies of this repo. If @aaronliu0130 wants to recreate them under their username, then another maintainer (myself included) can review and merge them.
2. I ask @jayvdb @mattyclarkson @tkruse @theandrewdavis to review the eight pull requests above to ensure that nothing suspicious has already been merged into this broadly deployed codebase.
3. I ask that if this duplicitous and dangerous pattern is being repeated on other GitHub repos, it must be stopped immediately.

EDIT:
If this was deliberately deceptive @norab0130 would be called a "sock puppet account" in the OSSF Scorecard docs.

This is the only place where I've used that account for this purpose, as someone from a "pgrouting" repository started complaining about the errors on the development branch. No problem not using that account if there's other active maintainers around to use that account. I'm happy for you, an active maintainer, to review my pull requests from now on!