On Oct 10, 2009, at 11:44 AM, Jack Howarth wrote:
Frank, I also noticed that we don't have a py26-tkinter stub package for python26. Why is that? Also, why do we build python26 and install it as a framework? Was there a specific reason for that change compared to how the python25 package is built?
The tkinter module is built into python25 and python26. It used to be the case that it was a separate port for python25, but later versions of the python25 port have it built in so we turned py25-tkinter into a stub package for those that had it installed. I think that when the python26 port was made, tkinter was already built in, hence there was no need to make an empty stub package for it.
The framework issue is a little more complex and someone will hopefully correct me if I'm wrong. The original python25 port was not a framework build. It was determined that a framework build was more desirable. I cannot remember the exact reasoning right now. There are a few tickets about this such as [1] and [2]. python25 was eventually made partially a framework build and we had to fix a few ports to work around that. When python26 (and above) was made, we decided to make it a framework build from the beginning.
[1] <https://trac.macports.org/ticket/16111> [2] <https://trac.macports.org/ticket/16334> Cheers! Frank _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
