classification
Title: Unable to run IDLE without write-access to config directory
Type: behavior Stage: needs patch
Components: IDLE Versions: Python 3.3, Python 3.2, Python 2.7, Python 2.6
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: brian.curtin, cane, serwy
Priority: normal Keywords:

Created on 2010-03-25 15:39 by cane, last changed 2011-12-17 19:37 by serwy.

Files
File name Uploaded Description Edit
error.png cane, 2010-03-25 15:39 Error message
Messages (2)
msg101708 - (view) Author: (cane) Date: 2010-03-25 15:39
When trying to run Python 2.6.5 & 3.1 IDLE GUI on Windows 7, I receive the following error that the "IDLE's subprocess didnt make connection. Either IDLE can't start a subprocess or personal firewall software is blocking the connection."

I've researched this error and tried following the steps to troubleshoot this error without any success.  I do not have any firewall software installed or have the Microsoft firewall enabled.  When following issue 8099 and tring to set the TCL and TK library to the idle.py I get the error that I need to check the path and permissions. (see attached screenshot)

These workstations are setup in active directory enviroment where each username that logs into the workstation is a local administrator and the referenced "M:\" drive is a home directory that is mapped for them.

When the local administrator account logs into the workstation the user can execute the IDLE GUI without any issues.

I found reference in one article that the os.py creates a directory called ".idlerc". 

I'm wondering if there is a way to hardcode a reference path that doesnt point to my "M:\" drive for this directory or is there something else that I can try to fix this issue?

Thanks,
Bryan
msg101716 - (view) Author: Brian Curtin (brian.curtin) * (Python committer) Date: 2010-03-25 16:13
I just reproduced this by removing write access from my user for my home directory.

It seems odd that you wouldn't have write access to your home directory in the first place, but that's tangent to the issue. I'll see if there are other acceptable locations to attempt to place the config directory.
History
Date User Action Args
2011-12-17 19:37:47serwysetnosy: + serwy

components: + IDLE, - Library (Lib), Windows
versions: + Python 2.7, Python 3.2, Python 3.3, - Python 3.1
2010-03-25 16:13:26brian.curtinset
nosy: + brian.curtin
title: Subprocess Startup Error - unable to create user config directory -> Unable to run IDLE without write-access to config directory
messages: + msg101716
priority: normal
components: + Library (Lib)
type: crash -> behavior
stage: needs patch
2010-03-25 15:39:28canecreate