Jump to content

Recommended Posts

Posted

I have been successfully running Python 3.3 on a school laptop. I can run IDLE and up comes the shell. Open a new edit window and save my code etc. F5 and run the code, no problem.

 

Until yesterday that is. Yesterday opening an editing/script window caused the program to shut-down.

 

So, what could be causing this? My network manager has no idea what is causing it and cannot help me.

 

The best I can come up with is the SRP in the GPO.

 

Any ideas what could be stopping this from running?

  • 2 weeks later...
Posted
Is this after students have worked on a file? What we found is if that file is renamed it allows you to open a new window again. But then once they work on a new file it's the same error. Open a new file and the wind
Posted
Is this after students have worked on a file? What we found is if that file is renamed it allows you to open a new window again. But then once they work on a new file it's the same error. Open a new file and the wind

@Latham which file is it that needs renaming?

Posted
Is this after students have worked on a file? What we found is if that file is renamed it allows you to open a new window again. But then once they work on a new file it's the same error. Open a new file and the wind

Not after a new file.

 

However, I have solved the problem by uninstalling the Python version I was running and installing 3.41 (AFAICR).

 

Which is the version being run in our VM.

 

I can only think 'white list issue'.

 

Thanks for your replies.

 

Then there is the VM protocol error but that is another thread.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...