I think that the idea is to keep using "mkdocs 1.0.4' for the moment due to 
some Theme issue.

According to the website https://www.mkdocs.org/about/release-notes/  the 
current release is mkdocs 1.4.0 which is not tested/required for OpenIndiana 
documentation.

However the good news is that the release-notes state that mkdocs 1.0 supported 
python 3.7

It states "Officially support Python 3.7." for release 1.0

The version that is required is the one from 2018 : 

https://www.mkdocs.org/about/release-notes/#version-104-2018-09-07

My understanding that this version is required could be wrong, but it is due to 
the discussion about Themes.

Also there was a PR (pull request) that was rejected in the past from somebody 
who tried to update mkdocs to version 1.2.3.

But I think that there is actually no reason to use Python 2.7 for mkdocs 1.0.4.

In fact the requirement for the "futures" package may be due to the fact that 
it can run on python 2.7 but requires the help from "futures" to do so ?

Regards
David Stes

----- Op 30 sep 2022 om 20:29 schreef Bob Friesenhahn 
bfrie...@simple.dallas.tx.us:

> On Fri, 30 Sep 2022, s...@pandora.be wrote:
> 
>> 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" package is intended to allow Python 2.7 code to be
> "soft" ported to Python 3.  It is a bridge to Python 3.  As such, it
> is important for any Python code yet to be ported to Python 3, or
> might execute with either version.
> 
> Bob
> --
> Bob Friesenhahn
> bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
> Public Key,     http://www.simplesystems.org/users/bfriesen/public-key.txt
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev

_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Reply via email to