Python 3 issues

I have Python3 installed via PackMan

Firstly, the Python3 file type — AE5 — doesn’t seem to be associated with Python3. Should it be?

Secondly, is there any straightforward way of finding out which libraries are available on RISC OS Python 3? In particular, argparse, glob and (not very likely, I assume) Python-imaging.

I have a number of scripts written in Python on other OSs. They run from the command line, and by placing them in an appropriate directory I can run them anywhere. I’m aware that scripts can be put in !Boot.Library, but when I put my script in there and call it by name I get the message “An application that opens this type of file has not been seen by the filer” — hence first question. So what do I need to do to get this to work the way it does in every other OS?

Has python 3 been seen by the filer?
You may have to Boot look at

Firstly, the Python3 file type — AE5 — doesn’t seem to be associated with Python3. Should it be?

Filetype &AE5 is for Python2. Python3 uses &A73. See !Python3.!Boot.

Python 3 has been seen by the filer — I can run "python3” from a task window.

I’ll have to change the file type. AE5 is what StrongEd creates when I ask it to create a Python file. Anybody know if StrongEd has been updated to cater for Python 3?

This type of problem is unique to RISC OS. Unix-based systems use the “shebang” line, while on Windows only one version of Python can be associated with the .py extension.

Thanks for the help.

Anybody know if StrongEd has been updated to cater for Python 3?

There are some notes on use of StrongED with python in the “Work in Progress” section of this document:-
How to use Python on RISC OS

Anybody know if StrongEd has been updated to cater for Python 3?

There is a Python3 mode for StrongED. You’ll need to update the Python mode too, the new version only grabs Python2 files leaving the rest for Python3 mode.

Unix-based systems use the “shebang” line,

StrongED can be set up to use the “shebang” line by editing the ModeWhen file for Python3 mode. You can also place StrongED$Mode = Python3 somewhere in the first 1k of a file to force the mode to use.

Should Python3 be capable of running on 26-bit OSs? I get a “bad parameters” error when trying it on VRPC DL/RO 4.0.2.

I get a “bad parameters” error when trying it on VRPC DL/RO 4.0.2.

That is because RO4’s WimpSlot command cannot manage the M suffix. Change 8M to 8192K in !Python3.!Run and in !Python3.!Setup line 8, minslot$. Python3 lights up on RO4.02 RPCEmu here.