Skip to content

Conversation

@okurz
Copy link
Member

@okurz okurz commented Dec 12, 2025

After

One main open point is where we should place the Python files. It would be good to have them in a sub-directory and a usual Python practice is to use a properly named package derived from the directory name so "src/os_autoinst_scripts/" sounds correct but is also rather long and also means for testing we need to adjust the Python import path. How about just "oas/" for (Os-Autoinst-Scripts) and ditch the "src/"?

@okurz okurz marked this pull request as draft December 12, 2025 15:44
@okurz okurz force-pushed the feature/bash_to_python4 branch from 4289b5f to 4629b34 Compare January 7, 2026 10:36
@os-autoinst os-autoinst deleted a comment from mergify bot Jan 7, 2026
@okurz okurz force-pushed the feature/bash_to_python4 branch from 4629b34 to 513f245 Compare January 7, 2026 10:41
@kalikiana
Copy link
Member

It would be good to have them in a sub-directory and a usual Python practice is to use a properly named package derived from the directory name so "src/os_autoinst_scripts/" sounds correct but is also rather long and also means for testing we need to adjust the Python import path. How about just "oas/" for (Os-Autoinst-Scripts) and ditch the "src/"?

I would prefer one or multiple more descriptive namespaces, rather than making it even more cryptic.

@okurz
Copy link
Member Author

okurz commented Jan 7, 2026

It would be good to have them in a sub-directory and a usual Python practice is to use a properly named package derived from the directory name so "src/os_autoinst_scripts/" sounds correct but is also rather long and also means for testing we need to adjust the Python import path. How about just "oas/" for (Os-Autoinst-Scripts) and ditch the "src/"?

I would prefer one or multiple more descriptive namespaces, rather than making it even more cryptic.

meaning what, to keep "src/os_autoinst_scripts/"?

@okurz okurz changed the title PART 2: Rewrite bash scripts to python - After #498 PART 2: Rewrite bash scripts to python - After #498+#505 Jan 8, 2026
Copy link
Contributor

@Martchus Martchus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks generally good so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants