RFC: Python actors already run on Crawlee Cloud — help us make it official

[aminembarki]

Here's a fact that surprises most people: Python actors already run on Crawlee Cloud today. The runner is Docker-image-based and doesn't care what's inside the container — if your actor ships a Dockerfile, it runs. crc init already offers Apify's official Python templates, and crc dev already detects requirements.txt and runs your actor with python3 -m src locally.

What's missing is everything around that: the docs say TypeScript-only (the comparison pages literally say "TypeScript scrapers" — that's on me and will be corrected as part of this work), there's no curated Python template set, and nobody has systematically verified which parts of the Apify Python SDK / crawlee-python behave identically against a self-hosted instance.

Before I turn "accidentally works" into "officially supported", I want input from people who'd actually use it:

1. Which templates matter most to you? crawlee-python, the Apify Python SDK directly, plain requests/httpx scripts, Scrapy — what would you reach for first?
2. What compat guarantees do you need documented? The README has a Supported Apify SDK Features table for JS/TS. I'm planning to add a Python column — which SDK surfaces (datasets, KV stores, request queues, proxy config, webhooks) do you rely on and want verified?
3. Early testers wanted. If you have a Python actor (or want to write one), I'll personally help you get it running on your instance and turn whatever breaks into test cases.

Ground rules, same as always:

• The roadmap's non-goals still apply — this is and stays a self-hosted platform.
• "I need X because Y happened to me" beats "it would be cool if X". Real friction wins.

This is on the roadmap as Proposed — RFC open: no version commitment until this discussion converges. What would make Python support actually useful for your deployment?