Closed devyntk closed 1 month ago
Hello @devyntk
I think the question should be asked why this is a problem to begin with. These shebangs have existed in the code base for years and it's never been a problem. By way of example, all these tests pass github CICD and yet they don't pass centos9 package build process?
However, let's just assume for the moment that there is something new in centos9 that somehow trips over them in the package build process. You have choices:
tests/
foldercd tests && pytest .
instead of whatever you're doing now.Thoughts?
This PR has automatically been marked stale due to inactivity. It will automatically close unless further action is taken. Please understand that the CiscoConfParse team is not obligated to comment on (or approve) every Pull Request. For more detailed information, please refer to CONTRIBUTING guidance -> https://github.com/mpenning/ciscoconfparse/blob/main/.github/CONTRIBUTING.md
This PR has been automatically closed due to lack of activity. For more detailed information, please refer to our CONTRIBUTING guidance -> https://github.com/mpenning/ciscoconfparse/blob/main/.github/CONTRIBUTING.md
these cause an issue when packaging on centos9, as they do not specify python2 or python3, and thus panic during building.