On 26 Dec 2008, at 23:30, Benjamin Peterson wrote:

On Fri, Dec 26, 2008 at 2:55 AM, Mark Summerfield wrote:

...

Hi,

Just wondered if/when there'd be a Mac installer for Python 3?

I think there should be one eventually. Unfortunately, the 3.x build process is not ironed out. If somebody wants to make a patch which makes the build script in Mac/BuildScript/ work, I'd be very happy. :)

Since I've been building 3.0 for a while now I looked at the script. build-install.py seems to have been half converted to py 3.0. Going full 3.0 was not hard but then there is the problem of the imports. Python 3.0 does not have MacOS or Carbon modules. Seems that there are two ways to go. Put back the Carbon and MacOS modules into 3.0. Use Python 2 to build the python 3 package. Barry

On 30 Dec 2008, at 13:45, Barry Scott wrote: ...

Since I've been building 3.0 for a while now I looked at the script.

build-install.py seems to have been half converted to py 3.0. Going full 3.0 was not hard but then there is the problem of the imports.

Python 3.0 does not have MacOS or Carbon modules.

Seems that there are two ways to go.

Put back the Carbon and MacOS modules into 3.0. Use Python 2 to build the python 3 package.

As far as I can tell the Carbon and MacOS modules are _only_ used in the setIcon() function, which is used to give pretty icon to the python folder. Perhaps it might be better to have a fully Python 3 build system and loose the prettiness for the time being. Nicko

Nicko van Someren wrote:

On 30 Dec 2008, at 13:45, Barry Scott wrote: ...

...

Since I've been building 3.0 for a while now I looked at the script.

build-install.py seems to have been half converted to py 3.0. Going full 3.0 was not hard but then there is the problem of the imports.

Python 3.0 does not have MacOS or Carbon modules.

Seems that there are two ways to go.

Put back the Carbon and MacOS modules into 3.0. Use Python 2 to build the python 3 package.

As far as I can tell the Carbon and MacOS modules are _only_ used in the setIcon() function, which is used to give pretty icon to the python folder. Perhaps it might be better to have a fully Python 3 build system and loose the prettiness for the time being.

+1 Bill

On 2 Jan, 2009, at 20:51, Bill Janssen wrote:

Nicko van Someren wrote:

...

On 30 Dec 2008, at 13:45, Barry Scott wrote: ...

...

Since I've been building 3.0 for a while now I looked at the script.

build-install.py seems to have been half converted to py 3.0. Going full 3.0 was not hard but then there is the problem of the imports.

Python 3.0 does not have MacOS or Carbon modules.

Seems that there are two ways to go.

Put back the Carbon and MacOS modules into 3.0. Use Python 2 to build the python 3 package.

As far as I can tell the Carbon and MacOS modules are _only_ used in the setIcon() function, which is used to give pretty icon to the python folder. Perhaps it might be better to have a fully Python 3 build system and loose the prettiness for the time being.

+1

-1. The script exists to make it as easy as possible to build the installer. Converting it to python 3 makes that task harder. BTW. Until a couple of days ago the script had no chance of working at all because the Mac-specific Makefiles were broken. Ronald

Martin v. Löwis wrote:

...

...

As far as I can tell the Carbon and MacOS modules are _only_ used in the setIcon() function, which is used to give pretty icon to the python folder. Perhaps it might be better to have a fully Python 3 build system and loose the prettiness for the time being.

+1

-1. I think it is a good choice that build-install.py is written in Python 2.x, and only relies on the system Python. For that matter, it could have been a shell script. That way, you don't have to build Python first in order to build it.

Can't argue with that. But dropping the "setIcon" function and its associated use of Carbon and MacOS modules from that build script seems to me a good idea. Prepare for the future with *very* limited loss of functionality. Bill