no-python

To enforce a no-Python policy, apply explicit policy checks and automated validations that prevent Python dependencies, scripts, and tooling from entering repositories and CI pipelines. This ensures consistent tooling and guides teams to prefer Kotlin or Bash environments.

A no-Python workspace policy is an absolute prohibition on suggesting, using, or adding Python as a dependency, scripting language, or tool. It ensures consistent tooling and reduces risk from unsupported Python environments across all projects and pipelines.

Yes, you can use Bash and POSIX utilities instead of Python for CI pipeline automation. The no-Python policy guides teams to prefer Kotlin/JVM, Kotlin/Native, and Bash, or Node.js only when explicitly justified for new automation tasks.

To prevent Python artifacts from entering your repository, implement automated validations within your CI pipelines and document the no-Python constraint in your onboarding guide. This enforces strict policy checks against Python dependencies and scripts.

A development team should adopt a Kotlin-first workflow to ensure consistent tooling and reduce risk from unsupported Python environments. Enforcing a strict no-Python policy across dependencies and scripts keeps the tech stack aligned with Kotlin/Java or shell tooling.