From cb0d89887079b4c40cef128293f5c8efed7a1958 Mon Sep 17 00:00:00 2001
From: Adhitya Mohan <admohan@amd.com>
Date: Fri, 8 May 2026 17:21:06 -0600
Subject: [PATCH] ryzers: add pyproject.toml so editable installs survive
 uninstall/reinstall

After PR #76 (b36f6e5) `pip install -e .` works in a fresh venv. But when
the venv has previously held a non-editable install of ryzers
(`pip install .`) and is then switched to editable
(`pip uninstall ryzers && pip install -e .`), `ryzers build <pkg>` dies
with:

  File ".../ryzers/configs.py", line 9, in <module>
      from . import RYZERS_DEFAULT_RUN_FLAGS
  ImportError: cannot import name 'RYZERS_DEFAULT_RUN_FLAGS' from
  'ryzers' (unknown location)

Root cause: modern setuptools (>=68) auto-discovery sees the top-level
`packages/` directory (Dockerfiles, no __init__.py) as a namespace
candidate and falls through to "strict" PEP 660 editable mode, which
installs a custom finder. The finder's name->path mapping shadows the
real source-tree __init__.py, and Python reports the package as a
namespace package at "(unknown location)".

Pinning `[tool.setuptools] packages = ["ryzers"]` in a pyproject.toml
keeps setuptools out of auto-discovery so the editable wheel is built in
compat mode (a plain .pth pointer) and the regular __init__.py loads
cleanly in both fresh and reused venvs.

Signed-off-by: Adhitya Mohan <admohan@amd.com>
---
 pyproject.toml | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 pyproject.toml

diff --git a/pyproject.toml b/pyproject.toml
new file mode 100644
index 00000000..0d8c8439
--- /dev/null
+++ b/pyproject.toml
@@ -0,0 +1,36 @@
+# Copyright(C) 2025 Advanced Micro Devices, Inc. All rights reserved.
+# SPDX-License-Identifier: MIT
+#
+# Explicit setuptools metadata so editable installs work deterministically
+# regardless of setuptools version and previous install state in the venv.
+#
+# Without this, modern setuptools (>=68) auto-discovery sees the top-level
+# `packages/` directory (Dockerfiles, no __init__.py) as a namespace
+# candidate and falls through to "strict" PEP 660 editable mode, which
+# creates a custom finder. If the venv previously had ryzers installed
+# non-editable (`pip install .`) and is then switched to editable
+# (`pip uninstall ryzers && pip install -e .`), the strict finder shadows
+# the source-tree __init__.py and `from . import RYZERS_DEFAULT_RUN_FLAGS`
+# fails with `ImportError: cannot import name 'RYZERS_DEFAULT_RUN_FLAGS'
+# from 'ryzers' (unknown location)`.
+#
+# Pinning `[tool.setuptools] packages = ["ryzers"]` keeps setuptools out of
+# auto-discovery so the editable wheel is built in compat mode and the
+# regular source-tree __init__.py loads in both fresh and reused venvs.
+
+[build-system]
+requires = ["setuptools>=64"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "ryzers"
+version = "1.0"
+description = "A tool to Manage and Build Dockerfiles for Ryzen AI Applications."
+requires-python = ">=3.8"
+dependencies = ["pyyaml"]
+
+[project.scripts]
+ryzers = "ryzers.entrypoint:main"
+
+[tool.setuptools]
+packages = ["ryzers"]