search

adem0x / pyscripter

Automatically exported from code.google.com/p/pyscripter
0 stars 0 forks source link

Pyscriptor gives error 'could not be properly initialized' when run against python 3.4.1 #773

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Install 3.4.1 - set path to c:\python34 then run pyscriptor
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
windows 7 - home basic: pyscriptor v2.5.3-x64 

Please provide any additional information below.
Idle runs quite happily.
Switching to python 3.3.5 x64 and pyscriptor works again.
Pyscriptor and Python are wonderful products

Original issue reported on code.google.com by rosswg2...@gmail.com on 28 Jun 2014 at 7:35

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
OK, I can uninstall 3.4.1, and install 3.3.5 instead.  My 3.4.1 is 32 bits.  Is 
3.3.5 64 bits?

I do not use my gmail account.  I would much appreciate if you email me at:
mohamedsaba@hotmail.com

Many thanks.

Original comment by msaba...@gmail.com on 6 Jul 2014 at 11:56

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/pyscripter/issues/detail?id=773
Ticket #773 "Pyscriptor gives error 'could not be properly initialized' when 
run against python 3.4.1"

http://code.google.com/p/pyscripter/issues/detail?id=775
Ticket #775 "Python could not be properly installed. We must quit"

http://code.google.com/p/pyscripter/issues/detail?id=776
Ticket #776 "Pyscripter 2.5.3 does not run on Python 3.4.1 - Suggestion: Please 
provide an updated version with Python 3.4 support"

describe the same bug.

Sincerely
Rolf

Original comment by rolf.hem...@gmail.com on 20 Jul 2014 at 8:59

GoogleCodeExporter commented 9 years ago 
Yes got it to work as follows:
installed 3.3.5 - path set to python33
then installed 3.4.1 path left at python33
then changed path to python34 - this worked.
.......................
Later had the same problem with psycopg - 
so installed psycopg for 3.5 path set at python33
then installed psycopg for 3.4.1 path still set at python33
then changed path to python34.
this is now working.

Original comment by rosswg2...@gmail.com on 9 Aug 2014 at 8:53

GoogleCodeExporter commented 9 years ago

Original comment by pyscripter on 20 Mar 2015 at 4:30