Date
1 - 4 of 4
CSIT jobs breaking on python2 trouble
|
JamO Luhrsen
Example:
https://jenkins.opendaylight.org/releng/job/netconf-csit-1node-userfeatures-all-magnesium/283/console We still have some pip install (which is python2) going on in our shell scripts to run our robot jobs. Some package somewhere is probably recently upgraded that is no longer going to allow python2. I have not looked very deep yet, just fyi for now. JamO |
|
|
|
JamO Luhrsen
https://jira.opendaylight.org/browse/INTTEST-103 On 6/18/20 6:57 PM, JamO Luhrsen via
lists.opendaylight.org wrote:
Example: |
|
|
|
JamO Luhrsen
ugly hack: https://git.opendaylight.org/gerrit/c/releng/builder/+/90504
On 6/18/20 7:01 PM, JamO Luhrsen via
lists.opendaylight.org wrote:
|
|
|
|
Thanh ha <zxiiro@...>
I think its probably time for us to default to Python 3 considering Python 2 is EOL at this point. More and more packages will become Python 3 supported only so we'll likely to continue hitting issues in the future if we keep on Python 2. Another patch I started looking into is consolidating all the Python requirements into a single requirements file (https://git.opendaylight.org/gerrit/c/releng/builder/+/90435). One of the problems I find with Python dependencies is that when you run "pip install" for packages separately, Python's dependency manager does not take into account previously installed packages so later pip installs could pull in incompatible versions of similar dependencies thus breaking previous pip installed packages. Having all of the packages in a single requirements file and pip installing all of them together in 1 command will resolve this kind of issue. I'm happy to help with a Python 3 migration but would need assistance from integration team to test such an effort. Regards, Thanh On Fri, Jun 19, 2020 at 3:16 AM JamO Luhrsen <jluhrsen@...> wrote:
|
|
|