Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
problem solved :_ I upgraded to 3.5.1 just released, and it works fine! (except pillow and pygame installs still dont work, but that's not your problem) Enjoy the holidays On 25 December 2015 at 14:12, Nicky Mac wrote: > thanks again for continuing to address my problem. > all those files are present as required. > This is a hard slog. > Maybe I should give up and fallback to my now working win 7 system > until a resolution crops up via an update/upgrade. > Have a happy and peaceful Christmas > > > On 24 December 2015 at 22:17, eryk sun wrote: > >> On Thu, Dec 24, 2015 at 3:29 PM, Nicky Mac wrote: >> > >> > C:\Users\Nick>python -m idlelib >> > ** IDLE can't import Tkinter. >> > Your Python may not be configured for Tk. ** >> >> In the 3.5 installation directory, ensure that tkinter is installed in >> Lib/tkinter. There should be an "__init__.py" and several other files >> such as "filedialog.py". Also ensure that the DLLs directory has the >> extension module "_tkinter.pyd" and dependent DLLs "tcl86t.dll" and >> "tk86t.dll". >> > > > > -- > Nick "Mac" McElwaine > -- Nick "Mac" McElwaine -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
thanks again for continuing to address my problem. all those files are present as required. This is a hard slog. Maybe I should give up and fallback to my now working win 7 system until a resolution crops up via an update/upgrade. Have a happy and peaceful Christmas On 24 December 2015 at 22:17, eryk sun wrote: > On Thu, Dec 24, 2015 at 3:29 PM, Nicky Mac wrote: > > > > C:\Users\Nick>python -m idlelib > > ** IDLE can't import Tkinter. > > Your Python may not be configured for Tk. ** > > In the 3.5 installation directory, ensure that tkinter is installed in > Lib/tkinter. There should be an "__init__.py" and several other files > such as "filedialog.py". Also ensure that the DLLs directory has the > extension module "_tkinter.pyd" and dependent DLLs "tcl86t.dll" and > "tk86t.dll". > -- Nick "Mac" McElwaine -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On Thu, Dec 24, 2015 at 4:45 PM, Terry Reedy wrote: > >> This file should not exist. Python 3 stores .pyc files in a >> __pycache__ subdirectory. It won't even run "idlelib\__init__.pyc" if >> "idlelib\__init__.py" exists, so your installation is incomplete and >> damaged. I suggest that you uninstall Python 3.5 and then completely >> remove "C:\Python\Python35" before reinstalling. > > 'python -m xyz', where xyz is a package name (directory on disk), runs > xyx/__main__.py (or the xyz/__pycache__/__main__...34.py compiled version). Running "-m idlelib" still imports idlelib, which executes __init__.py(c). For example, I modified __init__.py to print a message: C:\>py -3 -m idlelib Here I am. Specifically, runpy._run_module_as_main('idlelib', 1) calls runpy._get_module_details, which recurs to get the details for "idlelib.__main__". but first it executes __import__("idlelib") to "avoid catching initialization errors". It returns the module spec and the code object. Then _run_module_as_main calls runpy._run_code to exec the code in the namespace of __main__. That said, Python 3's import system should ignore a .pyc beside a .py file, because it looks for .pyc files in the __pycache__ subdirectory. It only executes "idlelib\__init__.pyc" if the corresponding .py file is missing. That's why I said Nicky's installation was both incomplete (missing "__init__.py") and damaged (somehow containing a Python 2.7 "__init__.pyc"), so I suggested a completely fresh install. Apparently that didn't help, so I presume for some reason it's not actually installing the _tkinter extension module and its dependencies. -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On Thu, Dec 24, 2015 at 4:33 PM, Terry Reedy wrote: >> somehow the new py3.5 has been added to the end, not the beginning. >> guess this path is what you meant by "my profile". > > Bizarre. I just installed 3.5.1 on top of 3.5.1rc1, on Win10 with the 64bit > .exe installer, and the 3.5 dirs are at the front, where I expect them. Are > you using a different version of installer? (The web version?) If you install just for the current user, the installer modifies only the user's "HKCU\Environment" key in the registry. When you log on, or when Explorer reloads its environment, the value of PATH is formed by concatenating the user value to the end of the system value. -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On 12/24/2015 9:59 AM, eryk sun wrote: On Thu, Dec 24, 2015 at 5:06 AM, Nicky Mac wrote: not sure what you mean by "my profile". following your suggestion, looks normal: I meant your profile directory, "C:\Users\Nick". But printing the package path showed the problem is in your Python 3 installation itself. C:\Users\Nick> python -c "import importlib; print(importlib.find_loader('idlelib').path)" C:\Python\Python35\lib\idlelib\__init__.pyc This file should not exist. Python 3 stores .pyc files in a __pycache__ subdirectory. It won't even run "idlelib\__init__.pyc" if "idlelib\__init__.py" exists, so your installation is incomplete and damaged. I suggest that you uninstall Python 3.5 and then completely remove "C:\Python\Python35" before reinstalling. 'python -m xyz', where xyz is a package name (directory on disk), runs xyx/__main__.py (or the xyz/__pycache__/__main__...34.py compiled version). This file currently contains the following implementation, subject to change. """ IDLE main entry point Run IDLE as python -m idlelib """ import idlelib.PyShell idlelib.PyShell.main() # This file does not work for 2.7; See issue 24212. The errant __init__.pyc should not directly be a problem, but does indicate something wrong, such as 2.7 files mixed into your 3.5 install (__cache__ is *not* used in 2.7). Based on my experience with this happening, you might try running chkdsk, from an elevated Command Prompt. 'python -m idlelib.idle' runs idlelib/idle.py (or the cached version) to mostly the same effect. The alternate entry has adjustments so it works in an uninstalled development repository, while still working in an installation. From a python program, 'import idlelib.idle' needed as 'import idlelib' would run idlelib/__init__.py, which is empty. -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On 12/24/2015 8:59 AM, Nicky Mac wrote: Dear python Team I think I've been wasting your time: C:\Users\Nick>path PATH=C:\Python27\;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Broadcom\Broadcom 802.11 Network Adapter;;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Python\Python35\Scripts\;C:\Python\Python35\ somehow the new py3.5 has been added to the end, not the beginning. guess this path is what you meant by "my profile". Bizarre. I just installed 3.5.1 on top of 3.5.1rc1, on Win10 with the 64bit .exe installer, and the 3.5 dirs are at the front, where I expect them. Are you using a different version of installer? (The web version?) -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On Thu, Dec 24, 2015 at 3:29 PM, Nicky Mac wrote: > > C:\Users\Nick>python -m idlelib > ** IDLE can't import Tkinter. > Your Python may not be configured for Tk. ** In the 3.5 installation directory, ensure that tkinter is installed in Lib/tkinter. There should be an "__init__.py" and several other files such as "filedialog.py". Also ensure that the DLLs directory has the extension module "_tkinter.pyd" and dependent DLLs "tcl86t.dll" and "tk86t.dll". -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
wow - a very comprehensive answer. However it seems I have now got it correctly reinstalled with the correct environment and path (as below) So I'm back to my original problem: C:\Users\Nick>python -m idlelib ** IDLE can't import Tkinter. Your Python may not be configured for Tk. ** On doing a repair or modify to install tcl/Tk again, the same result. C:\Users\Nick>python -c "import sys; print(*sys.path, sep='\n')" gives C:\Python\Python35\python35.zip C:\Python\Python35\DLLs C:\Python\Python35\lib C:\Python\Python35 C:\Python\Python35\lib\site-packages This looks OK, Python35 directory contains Lib and tcl as it does on my now working Win7 system, and Lib contains tkinter C:\Users\Nick>path PATH=C:\Python\Python35\Scripts\;C:\Python\Python35\;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Broadcom\Broadcom 802.11 Network Adapter;;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static; -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On 24/12/2015 14:52, Nicky Mac wrote: what a horrible environment windows is to support anything! (I was a UNIX professional). seems the user profile PATH is a registry entry, and was not updated when I deinstalled Python2.7 still haven't figured out how to change it - I will NOT attempy a regedit. I don't have a problem, but then I don't top post on lists that greatly prefer bottom posting or interspersed answers. -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On Thu, Dec 24, 2015 at 8:52 AM, Nicky Mac wrote: > seems the user profile PATH is a registry entry, and was not updated when I > deinstalled Python2.7 > still haven't figured out how to change it - I will NOT attempy a regedit. As to PATH on Windows, it's split into system and user components, which get concatenated (system followed by user) when a profile is loaded at logon. Persisted user environment variables are defined in the user's "Environment" key. This is where PATH should be defined. HKEY_CURRENT_USER\Environment There's also the "Volatile Environment" key where the system stores variables that are defined at logon such as USERNAME, USERPROFILE, and a per-session subkey (e.g. "1" for session 1) that has values such as SESSIONNAME. HKEY_CURRENT_USER\Volatile Environment HKEY_CURRENT_USER (HKCU) references the current user's hive, which is loaded in HKEY_USERS. The entries in HKEY_USERS are named by user SIDs (see "whoami /user"). The user's registry hive is loaded when logged on interactively or otherwise by LoadUserProfile. The hive is physically stored in the user profile directory in the hidden file "%USERPROFILE%\NTUSER.DAT". The system environment is first loaded by the session manager (smss.exe) during boot, so it's a subkey of the session manager's configuration. HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Control\Session Manager\Environment The HKLM\SYSTEM hive is located on the system volume at "%SystemRoot%\System32\config\SYSTEM". Don't use regedit to modify the environment unless you plan to reboot the system. Tools that modify the environment know to broadcast a WM_SETTINGCHANGE message to all top-level windows, which makes Explorer reload its environment from the registry. Subsequent processes started by Explorer inherit the updated environment. >From the command line, use "set" to modify the current environment. If you also want the change to be permanent, and for Explorer to be notified, then use setx.exe. In this case you still need cmd's internal "set" in order to modify the current environment. For example, first modify the current PATH. C:\>set MYPATH=C:\Spam;C:\Eggs C:\>set PATH=%PATH%;%MYPATH% Next, inspect the user's PATH in the registry. C:\>reg query HKCU\Environment /v PATH HKEY_CURRENT_USER\Environment PATHREG_EXPAND_SZ%USERPROFILE%\.dnx\bin Run setx.exe to extend this value. Note that "^" is cmd's escape character. C:\>setx MYPATH %MYPATH% SUCCESS: Specified value was saved. C:\>setx PATH ^%USERPROFILE^%\.dnx\bin;^%MYPATH^% SUCCESS: Specified value was saved. Verify that it was set correctly. C:\>reg query HKCU\Environment HKEY_CURRENT_USER\Environment DNX_HOMEREG_SZ%USERPROFILE%\.dnx PATHREG_EXPAND_SZ%USERPROFILE%\.dnx\bin;%MYPATH% TEMPREG_EXPAND_SZ%USERPROFILE%\AppData\Local\Temp TMPREG_EXPAND_SZ%USERPROFILE%\AppData\Local\Temp MYPATHREG_SZC:\Spam;C:\Eggs setx.exe sets the value's type as REG_EXPAND_SZ if it contains at least two "%" characters. It's only well-defined for REG_EXPAND_SZ values to depend on REG_SZ variables (or any system variable in a user variable, since the system environment is loaded first). A registry key is enumerated in arbitrary order (not alphabetic), but the system enumerates the key in two passes, with REG_SZ variables loaded in the first pass. Note that Visual Studio mistakenly set DNX_HOME as a REG_SZ. Thus I have the following useless environment variable: C:\>echo %DNX_HOME% should have been set as REG_EXPAND_SZ. %USERPROFILE%\.dnx should have been set as REG_EXPAND_SZ. -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
sorry to be such a darned nuisance - fixed the PATH to eliminate Py2.7 references but get same result: C:\Users\Nick>path PATH=C:\Python\Python35\Scripts\;C:\Python\Python35\;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Broadcom\Broadcom 802.11 Network Adapter;;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static; C:\Users\Nick>python -m idlelib C:\Python\Python35\python.exe: Error while finding spec for 'idlelib.__main__' (: bad magic number in 'idlelib': b'\x03\xf3\r\n'); 'idlelib' is a package and cannot be directly executed On 24 December 2015 at 14:52, Nicky Mac wrote: > what a horrible environment windows is to support anything! > (I was a UNIX professional). > seems the user profile PATH is a registry entry, and was not updated when > I deinstalled Python2.7 > still haven't figured out how to change it - I will NOT attempy a regedit. > > season's greetings > > On 24 December 2015 at 13:59, Nicky Mac wrote: > >> Dear python Team >> I think I've been wasting your time: >> >> C:\Users\Nick>path >> PATH=C:\Python27\;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\Program >> Files\Broadcom\Broadcom 802.11 Network >> Adapter;;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program >> Files (x86)\ATI >> Technologies\ATI.ACE\Core-Static;C:\Python\Python35\Scripts\;C:\Python\Python35\ >> >> somehow the new py3.5 has been added to the end, not the beginning. >> guess this path is what you meant by "my profile". >> I'll set about fixing it. >> Meery christmas to you all >> Nick >> >> On 24 December 2015 at 11:06, Nicky Mac wrote: >> >>> Hello again.] >>> not sure what you mean by "my profile". >>> following your suggestion, looks normal: >>> >>> C:\Users\Nick> python -c "import importlib; >>> print(importlib.find_loader('idlelib').path)" >>> C:\Python\Python35\lib\idlelib\__init__.pyc >>> >>> A search for idlelib shows this one plus one deep inside OpenOffice and >>> a Game. >>> >>> On 23 December 2015 at 21:20, eryk sun wrote: >>> On Wed, Dec 23, 2015 at 1:51 PM, Nicky Mac wrote: > > no sign of old Py2.7 anywhere :- > > C:\Users\Nick>python -c "import sys; print(*sys.path, sep='\n')" > > C:\Python\Python35\python35.zip > C:\Python\Python35\DLLs > C:\Python\Python35\lib > C:\Python\Python35 > C:\Python\Python35\lib\site-packages The first blank entry is for the current directory. Do you maybe have an old "idlelib" directory in your profile? Print what it's attempting to load: python -c "import importlib; print(importlib.find_loader('idlelib').path)" >>> >>> >>> >>> -- >>> Nick "Mac" McElwaine >>> >> >> >> >> -- >> Nick "Mac" McElwaine >> > > > > -- > Nick "Mac" McElwaine > -- Nick "Mac" McElwaine -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
what a horrible environment windows is to support anything! (I was a UNIX professional). seems the user profile PATH is a registry entry, and was not updated when I deinstalled Python2.7 still haven't figured out how to change it - I will NOT attempy a regedit. season's greetings On 24 December 2015 at 13:59, Nicky Mac wrote: > Dear python Team > I think I've been wasting your time: > > C:\Users\Nick>path > PATH=C:\Python27\;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\Program > Files\Broadcom\Broadcom 802.11 Network > Adapter;;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program > Files (x86)\ATI > Technologies\ATI.ACE\Core-Static;C:\Python\Python35\Scripts\;C:\Python\Python35\ > > somehow the new py3.5 has been added to the end, not the beginning. > guess this path is what you meant by "my profile". > I'll set about fixing it. > Meery christmas to you all > Nick > > On 24 December 2015 at 11:06, Nicky Mac wrote: > >> Hello again.] >> not sure what you mean by "my profile". >> following your suggestion, looks normal: >> >> C:\Users\Nick> python -c "import importlib; >> print(importlib.find_loader('idlelib').path)" >> C:\Python\Python35\lib\idlelib\__init__.pyc >> >> A search for idlelib shows this one plus one deep inside OpenOffice and a >> Game. >> >> On 23 December 2015 at 21:20, eryk sun wrote: >> >>> On Wed, Dec 23, 2015 at 1:51 PM, Nicky Mac wrote: >>> > >>> > no sign of old Py2.7 anywhere :- >>> > >>> > C:\Users\Nick>python -c "import sys; print(*sys.path, sep='\n')" >>> > >>> > C:\Python\Python35\python35.zip >>> > C:\Python\Python35\DLLs >>> > C:\Python\Python35\lib >>> > C:\Python\Python35 >>> > C:\Python\Python35\lib\site-packages >>> >>> The first blank entry is for the current directory. Do you maybe have >>> an old "idlelib" directory in your profile? >>> >>> Print what it's attempting to load: >>> >>> python -c "import importlib; >>> print(importlib.find_loader('idlelib').path)" >>> >> >> >> >> -- >> Nick "Mac" McElwaine >> > > > > -- > Nick "Mac" McElwaine > -- Nick "Mac" McElwaine -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On Thu, Dec 24, 2015 at 8:52 AM, Nicky Mac wrote: > seems the user profile PATH is a registry entry, and was not updated when I > deinstalled Python2.7 > still haven't figured out how to change it - I will NOT attempy a regedit. I don't use the option to add the installation and Scripts directories to PATH. It's a mess when installing multiple interpreters. I use the py launcher [1] and virtual environments [2], and manually add .PY to PATHEXT. [1]: https://docs.python.org/3/using/windows.html#python-launcher-for-windows [2]: https://docs.python.org/3/library/venv.html -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On Thu, Dec 24, 2015 at 5:06 AM, Nicky Mac wrote: > > not sure what you mean by "my profile". > following your suggestion, looks normal: I meant your profile directory, "C:\Users\Nick". But printing the package path showed the problem is in your Python 3 installation itself. > C:\Users\Nick> python -c "import importlib; > print(importlib.find_loader('idlelib').path)" > C:\Python\Python35\lib\idlelib\__init__.pyc This file should not exist. Python 3 stores .pyc files in a __pycache__ subdirectory. It won't even run "idlelib\__init__.pyc" if "idlelib\__init__.py" exists, so your installation is incomplete and damaged. I suggest that you uninstall Python 3.5 and then completely remove "C:\Python\Python35" before reinstalling. -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
Dear python Team I think I've been wasting your time: C:\Users\Nick>path PATH=C:\Python27\;C:\Python27\Scripts;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Broadcom\Broadcom 802.11 Network Adapter;;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Python\Python35\Scripts\;C:\Python\Python35\ somehow the new py3.5 has been added to the end, not the beginning. guess this path is what you meant by "my profile". I'll set about fixing it. Meery christmas to you all Nick On 24 December 2015 at 11:06, Nicky Mac wrote: > Hello again.] > not sure what you mean by "my profile". > following your suggestion, looks normal: > > C:\Users\Nick> python -c "import importlib; > print(importlib.find_loader('idlelib').path)" > C:\Python\Python35\lib\idlelib\__init__.pyc > > A search for idlelib shows this one plus one deep inside OpenOffice and a > Game. > > On 23 December 2015 at 21:20, eryk sun wrote: > >> On Wed, Dec 23, 2015 at 1:51 PM, Nicky Mac wrote: >> > >> > no sign of old Py2.7 anywhere :- >> > >> > C:\Users\Nick>python -c "import sys; print(*sys.path, sep='\n')" >> > >> > C:\Python\Python35\python35.zip >> > C:\Python\Python35\DLLs >> > C:\Python\Python35\lib >> > C:\Python\Python35 >> > C:\Python\Python35\lib\site-packages >> >> The first blank entry is for the current directory. Do you maybe have >> an old "idlelib" directory in your profile? >> >> Print what it's attempting to load: >> >> python -c "import importlib; >> print(importlib.find_loader('idlelib').path)" >> > > > > -- > Nick "Mac" McElwaine > -- Nick "Mac" McElwaine -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
Hello again.] not sure what you mean by "my profile". following your suggestion, looks normal: C:\Users\Nick> python -c "import importlib; print(importlib.find_loader('idlelib').path)" C:\Python\Python35\lib\idlelib\__init__.pyc A search for idlelib shows this one plus one deep inside OpenOffice and a Game. On 23 December 2015 at 21:20, eryk sun wrote: > On Wed, Dec 23, 2015 at 1:51 PM, Nicky Mac wrote: > > > > no sign of old Py2.7 anywhere :- > > > > C:\Users\Nick>python -c "import sys; print(*sys.path, sep='\n')" > > > > C:\Python\Python35\python35.zip > > C:\Python\Python35\DLLs > > C:\Python\Python35\lib > > C:\Python\Python35 > > C:\Python\Python35\lib\site-packages > > The first blank entry is for the current directory. Do you maybe have > an old "idlelib" directory in your profile? > > Print what it's attempting to load: > > python -c "import importlib; > print(importlib.find_loader('idlelib').path)" > -- Nick "Mac" McElwaine -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On Wed, Dec 23, 2015 at 1:51 PM, Nicky Mac wrote: > > no sign of old Py2.7 anywhere :- > > C:\Users\Nick>python -c "import sys; print(*sys.path, sep='\n')" > > C:\Python\Python35\python35.zip > C:\Python\Python35\DLLs > C:\Python\Python35\lib > C:\Python\Python35 > C:\Python\Python35\lib\site-packages The first blank entry is for the current directory. Do you maybe have an old "idlelib" directory in your profile? Print what it's attempting to load: python -c "import importlib; print(importlib.find_loader('idlelib').path)" -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
dear Python team thanks for your amazing support! no sign of old Py2.7 anywhere :- C:\Users\Nick>python -c "import sys; print(*sys.path, sep='\n')" C:\Python\Python35\python35.zip C:\Python\Python35\DLLs C:\Python\Python35\lib C:\Python\Python35 C:\Python\Python35\lib\site-packages On 23 December 2015 at 19:30, eryk sun wrote: > On Wed, Dec 23, 2015 at 8:38 AM, Nicky Mac wrote: > > > > I removed the old python2.7 entries in system Path, the PYTHON variables > you > > mentioned are not present. > > All I have is Python35 in the PATH. > > Maybe there's still a stale directory on sys.path for another reason. > Print sys.path from the command prompt: > > python -c "import sys; print(*sys.path, sep='\n')" > > P.S. Please reply to the list also this time. > -- Nick "Mac" McElwaine -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On Wed, Dec 23, 2015 at 8:38 AM, Nicky Mac wrote: > > I removed the old python2.7 entries in system Path, the PYTHON variables you > mentioned are not present. > All I have is Python35 in the PATH. Maybe there's still a stale directory on sys.path for another reason. Print sys.path from the command prompt: python -c "import sys; print(*sys.path, sep='\n')" P.S. Please reply to the list also this time. -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On Wed, Dec 23, 2015 at 7:16 AM, Nicky Mac wrote: > C:\Python\Python35\python.exe: Error while finding spec for > 'idlelib.__main__' (: bad magic number in 'idlelib': > b'\x03\xf3\r\n'); 'idlelib' is a package and cannot be directly executed 0xf303 (62211) is for Python 2.7. Make sure you don't have the environment variables PYTHONHOME or PYTHONPATH defined. -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
slight progress: i reinstalled ticking precompile options in the "Advanced features". Now I get this: icrosoft Windows [Version 10.0.10586] (c) 2015 Microsoft Corporation. All rights reserved. C:\Users\Nick>python -m idlelib C:\Python\Python35\python.exe: Error while finding spec for 'idlelib.__main__' (: bad magic number in 'idlelib': b'\x03\xf3\r\n'); 'idlelib' is a package and cannot be directly executed any help hugely appreciated! season's greetings Nick On 22 December 2015 at 20:27, Nicky Mac wrote: > I have run the install (and repair) which explicitly includes Tcl/Tk and l > have this problem: > > Microsoft Windows [Version 10.0.10586] (c) 2015 Microsoft Corporation. All > rights reserved. > > >C:\Python\Python35\python.exe -m idlelib > ** IDLE can't import Tkinter. > Your Python may not be configured for Tk. ** > > Please suggest how this can be fixed > any support greatly appreciated > > Nick McElwaine > -- Nick "Mac" McElwaine -- https://mail.python.org/mailman/listinfo/python-list
Re: unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
On 12/22/2015 3:27 PM, Nicky Mac wrote: I have run the install (and repair) which explicitly includes Tcl/Tk and l have this problem: First, I would download and install the final 3.5.1. I believe there was a change to the installer that might, possibly, make a difference. Write down exactly the install options you choose. C:\Python\Python35\python.exe -m idlelib ** IDLE can't import Tkinter. Your Python may not be configured for Tk. ** Then run python -m tkinter to remove IDLE from the issue. If problem persists, report again. Please suggest how this can be fixed any support greatly appreciated -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
unable to open IDLE for Python3.50rc1 on windows10 64bit AMD
I have run the install (and repair) which explicitly includes Tcl/Tk and l have this problem: Microsoft Windows [Version 10.0.10586] (c) 2015 Microsoft Corporation. All rights reserved. >C:\Python\Python35\python.exe -m idlelib ** IDLE can't import Tkinter. Your Python may not be configured for Tk. ** Please suggest how this can be fixed any support greatly appreciated Nick McElwaine -- https://mail.python.org/mailman/listinfo/python-list