The future of Python for OpenVMS

(LOGO.JPG) Python for OpenVMS

(go to: table of contents, index)

What is planned / needs to be done for/in a future version of Python for OpenVMS:


Currently, everything is running from the 'development directory tree' ([PYTHON...]). Access to the library is just 'hacked to make it work'. Multi-platform support (Alpha / VAX) is unclear.

What needs to be done is:

Some work has already been done by creating a special version of GETPATH.C in [.VMS]VMS__GETPATH.C.


Changes to the development environment so that users can make use of the building instructions without privileges. The 'development directory tree' ([PYTHON...]) should be able to live in a user's subdirectory.
Better navigation between web pages:
It should be possible to go directly from one page to the other (or the previous one) without returning to the table of contents.
26-DEC-1998 - Work has been started some time ago by using a single HTML page for each interface routine for the 'vms_lib' and 'vms_sys' modules.
A set of tests for OpenVMS specific extensions should be developed.

There are always enhancements / changes to already existing routines and data structures which can break old functions (and it happened).


Some implementations of gmtime() in the OpenVMS C run-time library return NULL (to indicate they do not support timezones) which Python (in [.MODULES]TIMEMODULE.C) cannot cope with. A workaround is in VMS__GMTIME.C which, however, returns just the local time.
(go to: table of contents, index)

07-APR-1999 ZE.