Closed GoogleCodeExporter closed 9 years ago
It seems that most of this (but not sure all of it) is caused by the PYTHONPATH
variable having directories on drives that are disconnected (unplugged). This
is very annoying problem because even trying to kill the Pyscripter process
when it is stuck does not work.
Original comment by john.non...@gmail.com
on 6 Feb 2012 at 3:40
Here is what I get here.
On my laptop I set a mapped drive corresponding to a drive on the desktop.
a) I start PyScripter and open a file from the mapped drive.
b) I close PyScripter.
c) I shut down the desktop.
d) I start PyScripter. There is a long delay about 40-60 seconds and then
PyScripter starts normally.
However I get the same issue with Windows explorer.
i.e. if I try to show the contents of the mapped drive after disconnecting the
desktop there is a long delay about 40-60 seconds before Windows Explorer comes
with an error message and marks the drive as unavailable. In fact if I try to
access the mapped drive in Windows Explorer before step d above and then try to
start PyScripter then PyScripter starts immediately. So the delay comes from
Windows trying to determine the availability of the mapped drive the first time
it is accessed after becoming unavailable. I am not sure what I can do about
it, so I am changing the status to Won't do.
If you have any suggestions about how to handle this I am all ears.
Original comment by pyscripter
on 24 Feb 2012 at 12:44
I believe my 2nd comment is the real cause. Please try to include a mapped
drive in the PYTHONPATH. You will find PyScripter NEVER restarts unless you
reconnect to the mapped drive that is in the PYTHONPATH.
Original comment by john.non...@sbcglobal.net
on 27 Feb 2012 at 3:41
OK. I did some more testing.
a) Set the PYTHONPATH environment variable to some mapped drive pointing to my
desktop.
b) Started PyScriper. It starts fine and includes the mapped drive in the path.
c) Closed PyScripter and shut down the desktop.
d) Restarted PyScripter. After a delay of around 40-50 seconds PyScripter
started OK.
e) Closed PyScripter and started again. PyScripter started fast this time.
I repeated the above steps but this time working with the standard python
shell. The behavior was similar. It appears that the delay comes from loading
python.
In your case does the standard Python shell (same version as the one used by
PyScripter) start as expected?
Original comment by pyscripter
on 29 Feb 2012 at 12:10
Original issue reported on code.google.com by
john.non...@gmail.com
on 19 Jan 2012 at 5:30