[SUGGEST] Support various package manager as well as uv for "common openstack users"

[choieastsea]

Although we adopt package manager as uv, we need to provide multiple ways for common Openstack users .

1. Give requirements.txt(which automatically sync with uv.lock) for "pip users".

2. Add some guides with or without uv or uvx.

[S0okJu]

I agree with them.

I have a question.
Is there an extra process needed to keep requirements.txt synced with uv.lock?
Such as, setting up the pyproject.toml.

[paikend]

Agree!

almost openstack users may be use pip

[paikend]

I agree with them.

I have a question. Is there an extra process needed to keep requirements.txt synced with uv.lock? Such as, setting up the pyproject.toml.

My opinion, I agree with providing both requirements.txt and requirements-dev.txt.

However, I suggest we auto-generate these files rather than manually maintaining them.
We manage only uv+pyproject.toml

For example) Auto-generate requirements files:

uv export --no-hashes --no-dev > requirements.txt
uv export --no-hashes > requirements-dev.txt

[S0okJu]

However, I suggest we auto-generate these files rather than manually maintaining them. We manage only uv+pyproject.toml

Does manually maintaining mean we change requirements.txt and requirements-dev.txt separately?