On Fri, Sep 30, 2022 at 07:16:18PM +0200, s...@pandora.be wrote: > > Part of the problem is, I think, that there is no maintainer any longer, as > far as I know, for the mkdocs component in oi-userland. > > If someone knows how to build mkdocs with python 3 (which is perhaps > possible, I don't know, I have no experience with building python components) > then this would solve most of the problem, I think ... > > Thanks for your work on this, because as I confirmed, there are indeed really > issues with the mkdocs python2.7. > > Several people related to the oi-docs are aware that we have a Python 2.7 > problem, but we are unsure how to fix it, I think. > > For example in my Vagrantfile I have a comment about a missing 2.7 'futures' > component: > > https://github.com/OpenIndiana/vagrantfiles/blob/main/oi-docs/Vagrantfile > > # there used to be a futures package in the repo ... > # library/python/futures seems to have a problem now > pfexec pkg install -v \ > git lynx links\ > library/python/futures \ > library/python/mkdocs \ > developer/documentation-tool/mdl > # as of 21/9/2021 futures IPS is missing so install by pip > pfexec pip install futures > > Because such "pip install" actions print a clear warning by Python that we > are using an unsupported Python 2.7, it is clear that something must be done.
The futures python package was obsoleted in May 2021 in OpenIndiana. The reason is, apparently, this - see https://pypi.org/project/futures/: It does not work on Python 3 due to Python 2 syntax being used in the codebase. Python 3 users should not attempt to install it, since the package is already included in the standard library. Regards. -- +-------------------------------------------+ | Marcel Telka e-mail: mar...@telka.sk | | homepage: http://telka.sk/ | +-------------------------------------------+ _______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev