Skip to content
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

Jump to bottom

Review / Test / Implement best practices to make Meza Python 3 compatible #9

Open
freephile opened this issue Jan 25, 2024 · 1 comment
Open

Review / Test / Implement best practices to make Meza Python 3 compatible #9

freephile opened this issue Jan 25, 2024 · 1 comment
Labels
python Python programming
Milestone
Platform Upgrade

Comments

@freephile
Copy link
Owner

See best practices for Ansible and Python Python 2.x compatibility is not a concern. The concern it to ensure that Meza conforms to Python 3.x best practices.
@freephile freephile added the python Python programming label Feb 28, 2024
@freephile freephile added this to the Platform Upgrade milestone Apr 4, 2024
@freephile
Copy link
Owner Author

There should not be separate configuration variables that are OS and version dependent like 'package_python3_pip_rhel8' (compared to package_python3_pip) - that is explicitly handled by OS and version detection in your playbooks!

This was noted in my comment at #41 (comment)

@freephile freephile mentioned this issue Feb 8, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
python Python programming
Projects
None yet
Milestone
Platform Upgrade
Development

No branches or pull requests
1 participant
@freephile