Koshy of CSY, Bangalore privately emailed me that Python/iX 1.5 is in
the works.  I have forwarded his comments below.

My comments:  Great, wonderful, outstanding!  An excellent example of
the proactive approach of HP3000'ers, both inside and outside of HP,
making a concerted effort to bring valuable software tools to MPE.

As for your question, for us a version for MPE/iX 5.5 is fine as all of
our systems are on that.  Given that 6.0 is just around the corner, I
would speculate that backporting to 5.0 is not necessary.

Rob Joseph
The NPD Group
[log in to unmask]

> >>>> "K Nagarajan" <[log in to unmask]> writes
>
> Hi Robert,
>
> I have Python1.5.1 with all the published fixes running on MPE/iX 5.5
> at the moment.
>
> I'm currently exploring a few final tweaks, like making libpython into
> an executable library, adding support for `dlopen()'ed modules so that
> Python can be easily embedded in Apache/iX and other products.
>
> Coming up next are a few interface modules that will allow Python
> code to seamlessly work with IMAGE and the native intrinsics.
>
> I hope to finish up the port in about a week or so after which I plan
> to put up both source and installable binaries on 'jazz'.  I am
> currently pursuing the necessary clearances for this.
>
> Pl. send me email if you'd like to see anything else in Python/iX.
> Porting Python to MPE/iX 5.0 is a bit tougher than 5.5.  Please let
> me know if you feel a 5.0 version is important.
>
> Koshy
> MPE/iX Kernelteam,  CSY, HPISO, Bangalore.
> <[log in to unmask]> My Personal Opinions Only.