Message 220970 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	John.Malmberg
Recipients	John.Malmberg
Date	2014-06-19.13:05:14
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1403183114.72.0.0988291504524.issue21809@psf.upfronthosting.co.za>
In-reply-to

Content
With issue 16136 VMS support was removed for Python V3 A test build of the in-development branch using the UNIX instruction and the current GNV product with a few minor tweaks produced a Python.exe interpreter that is somewhat functional. Most of the issues that showed up in the build process were either bugs in the VMS C library, or that Python would prefer some additional libraries would be present. These issues are common to porting other software to VMS, and not something that the Python project should need to concern it self with. I have setup a repository on the Sourceforge VMS-PORTS project, and a VMS specific discussion thread for doing the port. https://sourceforge.net/p/vms-ports/discussion/portingprojects/thread/333ab40a/ This is not intended as a fork of the Python project, rather it is a project to provide the build and runtime environment that Python 3 will need on VMS. Description on how to use this repository on VMS: https://sourceforge.net/p/vms-ports/cpython/ci/default/tree/readme The plan is to keep the current status in this file. https://sourceforge.net/p/vms-ports/cpython/ci/default/tree/vms_source/cpython/vms/aaa_readme.txt

With issue 16136 VMS support was removed for Python V3

A test build of the in-development branch using the UNIX instruction and the current GNV product with a few minor tweaks produced a Python.exe interpreter that is somewhat functional.

Most of the issues that showed up in the build process were either bugs in the VMS C library, or that Python would prefer some additional libraries would be present.  These issues are common to porting other software to VMS, and not something that the Python project should need to concern it self with.

I have setup a repository on the Sourceforge VMS-PORTS project, and a
VMS specific discussion thread for doing the port.

https://sourceforge.net/p/vms-ports/discussion/portingprojects/thread/333ab40a/

This is not intended as a fork of the Python project, rather it is a project to provide the build and runtime environment that Python 3 will need on VMS.

Description on how to use this repository on VMS:

https://sourceforge.net/p/vms-ports/cpython/ci/default/tree/readme

The plan is to keep the current status in this file.

https://sourceforge.net/p/vms-ports/cpython/ci/default/tree/vms_source/cpython/vms/aaa_readme.txt

History
Date	User	Action	Args
2014-06-19 13:05:14	John.Malmberg	set	recipients: + John.Malmberg
2014-06-19 13:05:14	John.Malmberg	set	messageid: <1403183114.72.0.0988291504524.issue21809@psf.upfronthosting.co.za>
2014-06-19 13:05:14	John.Malmberg	link	issue21809 messages
2014-06-19 13:05:14	John.Malmberg	create