Python toolbox library updated

Those of you who attended the WROCC talk will be aware that the toolbox library for python has undergone a bit of an overhaul.

The reults of this are now available, and can be installed with pip in the usual way. You might need to tell pip you want to upgrade if you’ve been using 0.2.0.

A word of warning, things build for 0.2 will need a bit of fettling to use 1.0.1.

The Hyper example is on github (https://github.com/c-jo/riscos-toolbox) which should give you a good idea how to do stuff, given the lack of docs and howtos. Which are on the list of things to do!

Hi Chris
Thanks for doing this. Are you going to update PIP on PackMan. It is currently showing:- Version 20.0.2-4

Meanwhile I used PIP to upgrade itself but am a bit puzzled by the warning.

*python3 -m pip install pip -U
Collecting pip
  Downloading pip-23.1.2-py3-none-any.whl (2.1 MB)

Installing collected packages: pip

Successfully installed pip-23-1-2

WARNING: You are using pip version 23-1-2; however, version 23.1.2 is available.

You should consider upgrading via the

‘SCSI::SSD….!Python3.Bin.python38 -m pip install —upgrade pip’

command.

Replicating the above I decided to verify the upgrade had happened.

*python3 -m pip --version
Traceback (most recent call last):
....
  File "ADFS::Titan4.$.Progm.Progm2.Python.!Python3.python38.lib.importlib.resources", line 61, in _normalize_path
    raise ValueError('{!r} must be only a file name'.format(path))
ValueError: 'cacert.pem' must be only a file name

I remembered this.

A bit of digging found instances of cacert.pem in !PythonSite.Python38.Site-Packages.pip._vendor.certifi.core/py which are not present in the previous version of that file in pip 20.0.2 .

A speculative search and replace of all 7 .pem‘s with /pem’s helped.

**python3 -m pip --version
pip 23.1.2 from ... !PythonSite.Python38.Site-Packages.pip (python 3.8)
*

Perhaps PackMan versions are better for RISC OS??

A bit later Reverted to pip 20.0.2 from PackMan.

Excellent timing, just grabbed it for the project I’m working on, can’t wait to give it a shot.

All occurrences of ‘.’ used as an extension separator should be replaced with

os.path.extsep

All occurrences of ‘.’ used as an extension separator should be replaced with os.path.extsep then the code will work on all platforms. The change then needs to be push back upstream.