You need a 64-bit version of python when you work with the 64-bit version of 
PyScripter.  Is your python 64-bit?  You can tell from the message that is 
printed when you start the python command line.  

I also have the same issue but I don't know how to start the python command 
line. Can you post step by step instructions on how to do it?

Have you installed a python distribution from www.python.org?  If yes your 
Windows Start menu contains an Python folder containing an item "Python 
x.y(Command Line).  If you select that, you get the Python prompt with a 
message such as this:
=============================
Python 3.3.0a1 (default, Mar  4 2012, 17:27:59) [MSC v.1500 32 bit (Intel)] on w
in32
Type "help", "copyright", "credits" or "license" for more information.
>>>
==============================

Notice that is says whether it is 32 bit (or 64 bit).

Issue 652 has been merged into this issue.

I'm running 64 bit python 3.2
> python
Python 3.2.3 (default, Apr 11 2012, 07:12:16) [MSC v.1500 64 bit (AMD64)] on 
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> ^Z

And V 2.5.3.0 of PyScripter.

I get same error when I invoke it via:
> "c:\Program Files\PyScripter\PyScripter.exe" -python32 -pythonpathdll 
"c:\Python32\DLLs"

python32.dll is typically located in c:\windows\system32 for "All User" 
installations or in the root python directory for single user or unregistered 
installations.  So, in the above you try omitting the pythondllpath (and not 
pythonpathdll) commandline option, or else try 
"c:\Program Files\PyScripter\PyScripter.exe" --python32 --pythondllpathdll 
"c:\Python32"  

(two dashes and not one).

Sorry, I meant try either

"c:\Program Files\PyScripter\PyScripter.exe" --python32

or

"c:\Program Files\PyScripter\PyScripter.exe" --python32 --pythondllpath 
"c:\Python32" 

Nope, still broke.  Same error.  Is there any way to get more verbose tracing 
to debug this situation?  I cannot find the error string "Python could not be 
properly initialized. We must quit." *anywhere* in the sources.

 ======== c:\BobHy\projects
> where python*.*
C:\Windows\System32\python32.dll
C:\Windows\System32\pythoncom32.dll
C:\Windows\System32\pythoncomloader32.dll
c:\Python32\python.exe
c:\Python32\python3.2.exe
c:\Python32\python3.exe
c:\Python32\pythonw.exe
c:\Python32\pythonw3.2.exe
c:\Python32\pythonw3.exe

 ======== c:\BobHy\projects
> "c:\Program Files\PyScripter\PyScripter.exe" --python32

((same error))

 ======== c:\BobHy\projects
> "c:\Program Files\PyScripter\PyScripter.exe" --python32 --pythondllpath 
"c:\python32"

((error 'could not find python32.dll', which is as expected for my config.))

 ======== c:\BobHy\projects
> "c:\Program Files\PyScripter\PyScripter.exe" --python32 --pythondllpath 
"c:\windows\system32"

((error 'could not be properly initialized'))

Which Python distribution are using?  Is it the standard python distribution 
from www.python.org?

Are you sure that you have the 64bit version of PyScripter 2.5.3 to match your 
64-bit version of python?

Try the following from the command prompt:

SET PYTHONHOME=c:\Python32
and then
"c:\Program Files\PyScripter\PyScripter.exe" --python32

Aha!
I was using ActiveState distribution (64 bit).
Simply overwriting it with distribution from python.org fixed my problems and 
PyScripter is now working.

It looks like there is some difference in name of python dll between these 
distributions, one is \python32\dlls\python3.dll, the other is 
\windows\system32\python32.dll, but I'm not sure which was which.

Thanks for your help debugging.  Any chance we could add a somewhat more 
informative error message?  

\windows\system32\python32.dll is from python.org.  It appears that ActiveState 
changed the name and the location of the python dll, thus breaking 
compatibility with PyScripter.

Such as what?  It tells you that Python could not be properly initialized.  
PyScripter has no way of knowing why this is the case.

Regarding ActiveState distro, renaming the dll and moving it to the root python 
directory would probably work.  Can anyone try this?

I do not know why they changed the long standing tradition of naming the python 
dll.  The minor version should definitely be included.