These tools are easily installed via pip (they are "any" and not require any patching).
Instead of maintaning packages for them, let users install the version they need, for
the Python version they want.
After removal, only one recipe (youtube_dl) mentions, in a comment, flake8.
None of these recipes should actually ever be needed as BUILD_REQUIERES either, as they
are linter/code-formatting tools.
If tests "require" them, as the youtube_dl seems to imply, those test should be disabled.
A required package (sip) already dropped 3.9 support in its last recipe update (6.8.6).
Also, all users of `pyqt_builder` already require only the `_python310` version.
----
Build tested on beta5 32 bits.
Nothing currently uses it on-tree.
Only known user, "unknown-horizons", is broken on-tree, upstream is
porting the game to Godot, and considers current engine "dead".
Only use in-tree of this is from calibre, and that's 3.10 only.
Use beautifulsoup4 for tests instead of the older "beautifulsoup" that isn't there anymore.
This is the newest of the 1.3.x series. As this is a requirement for gertty,
and that package hasn't seen development in years, better stick to an older
version of sqlalchemy (1.4 *might* work? 2.x surely will not).
Not used by anything on-tree. This version is pretty outdated, but updating
it requires bring up 7 packages more as dependencies.
Drop it, and let users install it via pip if needed.
Not used by anything on-tree. Newer versions are installable via pip, same with
alternatives that have zero dependencies (eg https://pypi.org/project/segno/).
Nothing on tree uses anything provided by twisted, and the rest of recipes
are for dependencies only twisted required.
All packages are "any" and without any patches. If someone needs these modules,
they can install them via pip.
While this module could be "any" in theory, doing so means the "x86_gcc2" version
of "pkg-config" gets called (that causes problems when packages that use this module
to build stuff, get the wrong info on 32 bits, no sane python package would be asking
for, or expecting, GCC2 stuff).
Cleaned up a bit the recipe while at it, and droped 3.9, as the only user on-tree
of this module is Python 3.10 only already (borgbackup).
