-
Notifications
You must be signed in to change notification settings - Fork 138
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
Move to embed and update more dependencies #2424
Comments
Re: current system package: python-dbus-pythonIn our Leap 15.3 we had:
So it was a meta-package for, in our case: python2-dbus-python | 1.2.16-6.3.1 There is on PyPi.org: dbus Python Bindings1.2.18 (2021-07-20)
1.3.0 (2022-09-06)
New dev dependencyNew development system requirement for building the PyPi dbus-python v1.2.18
zypper in dbus-1-devel Also requires glib2-devel |
distro from PyPifrom: https://pypi.org/project/distro/1.6.0/ 1.7.0 Feb 15, 2022
N.B. it looks like we were also depending on an old and considered buggy behaviour noted in 1.7.0 changelog:
1.6.0 - Jul 30, 2021https://github.com/python-distro/distro/blob/master/CHANGELOG.md#160-2021730
With our Leap 15.3 system package installs as follows:
|
Six from PyPihttps://pypi.org/project/six/ six 1.16.0Looks good and is what we were running via 15.3 packages anyway:
No equivalent found in Leap 15.4 as of yet!
Which is a little confusing. We may just want to build our own here. |
PyZMQ from PyPihttps://pypi.org/project/pyzmq/#history But the requires tag in PyPi only states 2.7 on 19.0.2 (Jul 31, 2020) at the latest. Also from the homepage changelog: https://pyzmq.readthedocs.io/en/latest/changelog.html#id20 20.0 (Nov 13, 2020)
And on a development Leap 15.3 we have:
Their docs we have that it builds against the system included.
So we may want to specify a binary wheel variant here. |
Python requestsWe already package bundle 2.25.1 (2020-12-16)
Previous version was 2.27.1 (2022-01-05) so last to support Python 2 Newer versions in Python 3 variant no longer use chardet by default. |
Update setup.py and our django-hack.py to accommodate embedding and updating: - pytz to latest version. - six to latest version. - distro to latest version with prior expected behaviour. The following were all moved to the last Python 2 compatible versions, prior to our move to Python 3: - pyzmq - requests - dbus-python
Remove legacy 'distribute' dependency as it's setuptools install clashes/breaks 15.4 build due to conflict with system devel_languages_python setuptools version. Our varying build systems 15.3/15.4 also now produce varying egg paths. Accommodate by overloading.
Now that we are embedding more dependencies we need to pin and add them to our django-hack.py. At least until we replace our build system.
We are initially sourcing our currently required python2-setuptools via the devel_languages_python OBS repo. |
Update setup.py and our django-hack.py to accommodate embedding and updating: - pytz to latest version. - six to latest version. - distro to latest version with prior expected behaviour. The following were all moved to the last Python 2 compatible versions, prior to our move to Python 3: - pyzmq - requests - dbus-python Remove legacy 'distribute' dependency as it's setuptools install clashes/breaks 15.4 build due to conflict with system devel_languages_python setuptools version. Our varying build systems 15.3/15.4 also now produce varying egg paths. Accommodate by overloading. Pin modules required by our embedded Python2 Requests Now that we are embedding more dependencies we need to pin and add them to our django-hack.py. At least until we replace our build system.
…_more_dependencies Embed and update more dependencies #2424
close by #2431 |
During the development involved in moving us from our v3 (CentOS base) to our v4 "Built on openSUSE" we partly transitioned to using some OS system python libraries. It is now required that we transition back to including as many dependencies as is practical.
Three reasons for this proposed direction/requirement:
Current package (rpm) defined dependencies directly related to Python; in the context of the above referenced issues:
The text was updated successfully, but these errors were encountered: