Bill Janssen <jans...@parc.com> wrote: > Martin v. Löwis <mar...@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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
