On Dec 3, 10:54 am, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> On Dec 3, 2008, at 10:48 AM, David Joyner wrote:
>
> > But tcl/tk is not a python package. tkinter is the python interface to
> > it and it is included with every python distribution (including
> > Sage's).
> > The problem is that to import it, tkinter.py looks for tcl/tk using
> > some
> > magic I couldn't figure out.
>
> > Adrian's suggestion (or William's, and I think now Adam had the
> > right idea too)
> > worked: reinstall Sage's Python using sage -f.
>
> > Thanks to all of you for your help.
To reiterate: if you don't have the tcl/tk development libraries
installed the extension will fail to build. The system python had
working bindings since that python was build in the presence of those
dev libraries. Since those aren't needed at runtime for python they
are usually not installed as a dependency. "sage -f ..." only worked
because you installed the right dev packages in the meantime.
> Sometimes during Python compilation, it looks to see if a certain
> library is available,
Nope, no looking involved, python's build system just "does" :)
> and if it is it compiles the corresponding
> module, and otherwise simply doesn't. This is what it does, for
> instance, with OpenSSL, and sounds like the same thing with tkinter.
> This matches the behavior we're seeing at least.
Python attempts to build the extension and if it fails is just moves
on. On most systems at least some extensions are broken, so this is
business as usual.
> - Robert
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
