python doesn't include Tkinter though building with USE=tcltk Version is python-2.3.5 Tkinter is needed by several other programs and just assumed to exist when python exists at all. Of course I installed tk and all related software. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Did you enable 'X' in your USE flags?
Python herd, is there some reason we need the X USE flag? It seems redundant, since the only thing it does is allow the tcltk, but if you don't specify X, you get no tcltk. Is there some other purpose for the X flag I'm missing?
i would prefer the X flag over tcltk flag if we were to reduce it to one, mainly because there is not other toolkit that python bundles itself with. of course, some ppl who have X and gtk might not want to compile with tcltk support, so that is probably why there are two.
If you want to leave it as is instead of remove one, we could just add a check in pkg_setup to make sure they have X in addition to tcltk and die if not.
Anyway I included the 'X' flag in my global use flags. I even tried all 'IUSE' flags from 'python.*.ebuild' and re-emerged 'blt' as found in the forums. But nothing helps, lib-tk still isn't built. The complete USE log is: "x86 X Xaw3d acpi alsa berkdb bonobo bootstrap build bzlib cdparanoia ctype divx4linux doc dvb fftw ftp gcj gd gdbm gtkhtml icq ipv6 java jikes joystick kde kdeenablefinal kerberos lprng maildir mime moznocompose moznoirc mozp3p mozsvg mozxmlterm ncurses ooo-kde oss php posix readline satellite smime soap sockets ssl svg tcltk ucs2 usb vim-with-x xalan xmlrpc linguas_de linguas_tr linguas_en_GB userland_GNU kernel_linux elibc_glibc" May be there are some out of dates here, I don't check them too often.
You have 'build' in your USE flags, which disables tcltk,
(In reply to comment #6) Absolutely true, the python ebuild know really compiles with tcltk and tkinter module. The build and bootstrap flag managed to find their way through the IUSE setting of the python.*.ebuild file, which I simply copied to set all USE flags that modify behaviour. Maybe the tk ebuild should enable an automatic use flag tcltk, which won't produce too much overhead IMHO. I think this bug can be closed.
