toxgen: Make it clearer which suites can be migrated (#4196)

sentrivana · web-flow · commit 6f49bfb9fe4f · 2025-03-26T10:26:14.000Z
...also, `cohere` was in the `IGNORE` list twice, apparently.
diff --git a/scripts/populate_tox/populate_tox.py b/scripts/populate_tox/populate_tox.py
@@ -49,22 +49,26 @@
     # suites over to this script. Some entries will probably stay forever
     # as they don't fit the mold (e.g. common, asgi, which don't have a 3rd party
     # pypi package to install in different versions).
+    #
+    # Test suites that will have to remain hardcoded since they don't fit the
+    # toxgen usecase
+    "asgi",
+    "aws_lambda",
+    "cloud_resource_context",
     "common",
     "gevent",
     "opentelemetry",
     "potel",
+    # Integrations that can be migrated -- we should eventually remove all
+    # of these from the IGNORE list
     "aiohttp",
     "anthropic",
     "arq",
-    "asgi",
     "asyncpg",
-    "aws_lambda",
     "beam",
     "boto3",
     "chalice",
     "cohere",
-    "cloud_resource_context",
-    "cohere",
     "django",
     "fastapi",
     "gcp",
