<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 29, 2022 at 2:25 PM Marcel Telka <<a href="mailto:marcel@telka.sk">marcel@telka.sk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
Currently we provide Python versions 2.7, 3.5, 3.7, and 3.9 for<br>
OpenIndiana, while version 3.9 is the default version.<br>
<br>
Both Python 2.7 and 3.5 are no longer supported for two or almost three<br>
years now respectively - see<br>
<a href="https://devguide.python.org/versions/#versions" rel="noreferrer" target="_blank">https://devguide.python.org/versions/#versions</a> for details, so we<br>
started to obsolete them. Since there are many related packages that<br>
needs to be rebuilt to get python 2.7 and 3.5 obsoleted, this transition<br>
is expected to take long time (probably weeks, maybe months).<br>
<br>
There are basically two sets of related packages:<br>
<br>
#1 software that uses python (e.g. gimp), and<br>
#2 packages that provide some enhancement to python; these are usually<br>
python modules, for example cherrypy.<br>
<br>
For #1 we just need to rebuild packages that require python 2.7 or 3.5<br>
so they start to require either python 3.7, or python 3.9. Volunteers<br>
are welcome!<br>
<br>
For #2 the situation is a bit more complex. The name of all packages in<br>
this set is starting with 'library/python'. There is usually a basic<br>
package (e.g. library/python/cherrypy) and few version specific packages<br>
(e.g. library/python/cherrypy-35, library/python/cherrypy-37,<br>
library/python/cherrypy-39). Another example is library/python/pycups<br>
and its library/python/pycups-27 and library/python/pycups-35.<br>
<br>
For such packages we will slowly obsolete their -27 and -35 variants.<br>
In a case there is neither -37 nor -39 variant already available, nor it<br>
is needed for some other package, we will end up with all package<br>
variants obsoleted. If this happens, then in addition to obsolete of<br>
both -27 and -35 we will obsolete the base package too.<br>
<br>
For example, cherrypy. There are already -35, -37, and -39 variants.<br>
We will obsolete the -35 variant and both -37 and -39 will be kept, so<br>
we will keep the basic library/python/cherrypy too.<br>
<br>
When looking at pycups, we will obsolete both -27 and -35 variants.<br>
Let's assume there is currently no other package that needs pycups, so<br>
we would end with orphaned library/python/pycups, so we will obsolete<br>
the library/python/pycups package too.<br>
<br>
Based on the rule above we already obsoleted following packages<br>
recently:<br>
<br>
library/python/augeas<br>
library/python/backports.shutil_get_terminal_size<br>
library/python/backports.tempfile<br>
library/python/cheetah<br>
library/python/click<br>
library/python/cssutils<br>
library/python/cython<br>
library/python/dulwich<br>
library/python/geoip<br>
library/python/elixir<br>
library/python/import-profiler<br>
library/python/kafka-python<br>
library/python/livereload<br>
library/python/m2crypto<br>
library/python/mkdocs-bootstrap<br>
library/python/mkdocs-bootswatch<br>
library/python/mkdocs<br>
library/python/netaddr<br>
library/python/netifaces<br>
library/python/numpy<br>
library/python/pygtksourceview<br>
library/python/pymongo<br>
library/python/pyorbit<br>
library/python/pyrex<br>
library/python/pyro<br>
library/python/python-ldap<br>
library/python/python-memcached<br>
library/python/python-mysql<br>
library/python/python-notify<br>
library/python/python-sexy<br>
library/python/pywbem<br>
library/python/scientific-py<br>
library/python/sqlalchemy<br>
library/python/typing<br>
library/python/unittest2<br>
<br>
Here is a list of packages that could get possibly obsoleted soon:<br>
<br>
library/python/backport_abc<br>
library/python/backports.functools_lru_cache<br>
library/python/backports.ssl_match_hostname<br>
library/python/colorama<br>
library/python/decorator<br>
library/python/enum<br>
library/python/flamegraph<br>
library/python/funcsigs<br>
library/python/ipaddress<br>
library/python/ipython<br>
library/python/ipython_genutils<br>
library/python/notify2<br>
library/python/pickleshare<br>
library/python/prompt-toolkit<br>
library/python/pyatspi2<br>
library/python/pycups<br>
library/python/pygobject<br>
library/python/pygtk2<br>
library/python/python-compizconfig<br>
library/python/python-xdg<br>
library/python/python-xlib<br>
library/python/rbtools<br>
library/python/simplegeneric<br>
library/python/traitlets<br>
<br>
If you need any package from these lists then please create a pull<br>
request (see <a href="https://github.com/OpenIndiana/oi-userland/pulls" rel="noreferrer" target="_blank">https://github.com/OpenIndiana/oi-userland/pulls</a>) to get<br>
the package back and built for python 3.7 and/or 3.9 (in a case it is on<br>
the first list of already obsoleted packages), or either let us know or<br>
create a pull request to rebuild the package for python 3.7 and/or 3.9<br>
(if it is on the second list of packages we could possibly obsolete).<br>
<br>
Any help with this task is very welcome (for example pull requests to<br>
get software in set #1 rebuilt).<br>
<br>
Please note that support for building python modules for python 2.7 and<br>
3.5 was already dropped from oi-userland.<br></blockquote><div><br></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default">I do not understand the need for obsoleting the entire package and removing all the files instead of updating on the go.</div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default">Could you explain the motivation?</div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default">To me this seems a bit of overhead, like removing the mkdocs, cython, numpy packages completely from the tree instead of updating them. </div></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default">We therefore lose track of what was in the tree and people may start from scratch all over again.</div></div><div><br></div><div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default">Maybe you intend to provide some level of automation later?</div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default">An earlier heads-up before starting to remove everything could have been nice to have a chance to update a few components in advance and avoid the mumbo-jumbo.</div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default"><br></div><div style="font-family:arial,helvetica,sans-serif;font-size:small" class="gmail_default">Thank you<br></div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
Thank you.<br>
<br>
-- <br>
+-------------------------------------------+<br>
| Marcel Telka e-mail: <a href="mailto:marcel@telka.sk" target="_blank">marcel@telka.sk</a> |<br>
| homepage: <a href="http://telka.sk/" rel="noreferrer" target="_blank">http://telka.sk/</a> |<br>
+-------------------------------------------+<br>
<br>
_______________________________________________<br>
oi-dev mailing list<br>
<a href="mailto:oi-dev@openindiana.org" target="_blank">oi-dev@openindiana.org</a><br>
<a href="https://openindiana.org/mailman/listinfo/oi-dev" rel="noreferrer" target="_blank">https://openindiana.org/mailman/listinfo/oi-dev</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><font style="font-family:courier new,monospace" size="1">---<br>Praise the Caffeine embeddings<br></font></div></div></div></div></div>