Skip to content

[Python] Clarify approach for namespacing #3518

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kanterov wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[Python] Clarify approach for namespacing #3518

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cde27f0
[Python] Clarify approach for namespacing
kanterov Aug 29, 2025
d48babc
Merge branch 'main' into python-clarify-namespacing
pietern Oct 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion experimental/python/codegen/codegen/packages.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,14 @@
import re
from typing import Optional

# All supported resource types and their namespace
# All supported resource types and their namespace.
#
# We put each resource type into own package and don't do cross-package imports,
# each package is self-contained. If two resources share the same datatype, it's
# duplicated to allow independent evolution.
#
# The convention is that each resource type uses a plural name as package name,
# e.g., "resources.Job" -> "jobs", "resources.Pipeline" -> "pipelines".
RESOURCE_NAMESPACE = {
"resources.Job": "jobs",
"resources.Pipeline": "pipelines",
Expand Down
Loading