Ned Deily added the comment:
As proposed above, the built-in Tcl/Tk support has been reverted from the OS X
installers for 3.3.3rc2 and for 2.7.6 final. Issue15663 will continue to track
changes for 3.4.0; the implementation there will have to change for 3.4.0b1.
I've also opened Issue19558
Benjamin Peterson added the comment:
Downgrading, since this is fixed in release branch.
--
priority: release blocker - normal
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19490
___
Ned Deily added the comment:
After further investigation and deliberation, I believe that we need to revert
the built-in Tcl/Tk from the OS X installers for 2.7.6 and 3.3.3. The
contributing factors:
1. As implemented, we now know that the built-in Tcl/Tk breaks source installs
and/or
Piet van Oostrum added the comment:
I think future versions of Python should add the relevant information about how
they are linked to Tcl/Tk in sysconfig. This would include the path of the
include files, the shared libraries and the tcl files. Or a framework location
on OS X if this is
Ned Deily added the comment:
Piet, yes, I've been thinking of how to do that. Unfortunately, it can only be
a hint since, in the case of an installer Python, there is no guarantee that
the header files on the build machine are available on the installed machine in
the same location or even
New submission from Ned Deily:
Piet van Oostrum (on python-dev and elsewhere) wrote:
I tried to install matplotlib 1.3.1 on the release candidates of Python 2.7.6
and 3.3.3.
I am on Mac OS X 10.6.8.
Although the installation gave no problems, there is a problem with Tcl/Tk.
The new Pythons
Ned Deily added the comment:
That's unfortunate. It looks like matplotlib on OS X (darwin) has cpp code
that interfaces directly with Tk and, hence, needs Tk headers. Further, for OS
X (darwin), its setup.py assumes that Tkinter is linked with Tcl and Tk
installed as frameworks in
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19490
___
