-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
tools: frr-reload.py must use python2 #6434
Conversation
Use python2 explicitly in frr-reload.py. Signed-off-by: Mark Stapp <mjs@voltanet.io>
💚 Basic BGPD CI results: SUCCESS, 0 tests failedResults table
For details, please contact louberger |
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-12358/ This is a comment from an automated CI system. Warnings Generated during build:Debian 10 amd64 build: Successful with additional warningsDebian Package lintian failed for Debian 10 amd64 build:
|
What issues are you seeing with python 3? I would like to understand a bit better before throwing in the towel and putting in a hard dependancy on python2 especially since python2 is deprecated. |
I saw cli processing failures running a couple of the topotests that use frr-reload to make config changes; I'm using an ubuntu20 vm, where 'python' is now python3. I guess I saw this as a temporary way to avoid blocking everyone on newer environments, offering a window to resolve the issue.
|
This patch is a hard nack from me. frr-reload.py has code in it that attempts to bridge the gap between people using 2 or 3. If people are using 3 and it is failing then we should fix that not downgrade it to a version of python that is completely out of support. If there are specific test cases that are failing using frr-reload.py in topotests then I would like to understand what ones they are so it can be fixed appropriately. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
python2 is deprecated and I will not advocate intentionally turning backwards here. We must move forward by identifying and fixing issues seen in python3 running this script.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, let's either see what the bugs are and fix them specifically, or (my preference) go the reverse direction and force python 3.
I agree w/ Quentin I would prefer forcing python3 as the answer here as well. |
Fair enough |
Use python2 explicitly in frr-reload.py - on ubuntu 20 for example, "python" is now python3.