Hi, Just wondered if/when there'd be a Mac installer for Python 3? Thanks! -- Mark Summerfield, Qtrac Ltd, www.qtrac.eu C++, Python, Qt, PyQt - training and consultancy "Programming in Python 3" - ISBN 0137129297
On Fri, Dec 26, 2008 at 2:55 AM, Mark Summerfield <list@qtrac.plus.com> 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. :)
Thanks!
-- Regards, Benjamin Peterson
On 26 Dec 2008, at 23:30, Benjamin Peterson wrote:
On Fri, Dec 26, 2008 at 2:55 AM, Mark Summerfield <list@qtrac.plus.com> 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 Tue, Dec 30, 2008 at 3:45 PM, Barry Scott <barry@barrys-emacs.org> wrote:
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.
Thanks for your help, but just today Ronald Oussoren, the Mac maintainer, spent some time making the installer work. As a result, we should be ready to go for 3.0.1!
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.
I've converted it back to 2.x for the time being. Eventually, I think some 3.x bindings should be released. -- Regards, Benjamin Peterson
On 30 Dec, 2008, at 22:59, Benjamin Peterson wrote:
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.
I've converted it back to 2.x for the time being. Eventually, I think some 3.x bindings should be released.
For the record: I was my intention that the build-installer.py script works with /usr/bin/python on OSX 10.4 or later. That makes it possible to create a usable installer without first having to build a bootstrap version of python. Ronald
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 <nicko@nicko.org> 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
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. Regards, Martin
Martin v. Löwis <martin@v.loewis.de> 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
Bill Janssen <janssen@parc.com> wrote:
Martin v. Löwis <martin@v.loewis.de> 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.
At the very least, we could move the imports of Carbon and MacOS into the setIcon() function, which is called only once, and wrap a try-except around that call. Bill
On 2 Jan, 2009, at 20:51, Bill Janssen wrote:
Nicko van Someren <nicko@nicko.org> 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
On Wed, Dec 31, 2008 at 4:34 PM, Nicko van Someren <nicko@nicko.org> 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 also There's little advantage having it be in Python 3 at the moment. -- Regards, Benjamin
participants (7)
-
"Martin v. Löwis" -
Barry Scott -
Benjamin Peterson -
Bill Janssen -
Mark Summerfield -
Nicko van Someren -
Ronald Oussoren