Doesn't initialize on Python 3.4.0

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Pyscripter doesn't initialize with Python 3.4.0, but it works fine with 3.3.4.
2.
3.

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

What version of the product are you using? On what operating system?
2.5.3.0 x86 on XP

Please provide any additional information below.

Original issue reported on code.google.com by doug.tha...@gmail.com on 18 Mar 2014 at 4:04

[GoogleCodeExporter]

I have experienced the same problem on Windows 8.1 64 bit ("Python could not be 
properly initialized. We must quit.")

I tried to uninstall and reinstall Python and then Pyscripter 2.5.3, both in 32 
bit versions. It did not solve the problem.

The same attempt with 64 bit versions of the two products failed as well.

Best regards
Jesper

Original comment by b17032...@gmail.com on 20 Mar 2014 at 8:34

[GoogleCodeExporter]

Pyscripter 2.5.3 was running fine on my computer with Pythom 3.3.4. When I
removed 3.3.4 and installed 3.4.0, Pyscripter locked. I then uninstalled
3.4.0 and re-installed 3.3.4. Pyscripter was fine.

I only install 32-bit software.

Are any other people experiencing problems with 3.4.0?

Original comment by doug.tha...@gmail.com on 21 Mar 2014 at 12:39

[GoogleCodeExporter]

I am also experiencing the same issue.
- Windows 8.1 x64
- Python 3.4 x64
- PyScripter 2.5.3 x64
I have not used PyScripter previously, so I cannot comment on previous, working 
scenarios.

Original comment by Steve.Jo...@gmail.com on 24 Mar 2014 at 12:30

[GoogleCodeExporter]

Same Issue with Windows 7 64 bit and Python 3.4.0.
After Installing Python 3.3.5 Pyscripter started.

Original comment by marian.v...@gmail.com on 25 Mar 2014 at 2:18

[GoogleCodeExporter]

I've looked at the version history of Pyscripter versions 
(https://code.google.com/p/pyscripter/wiki/History), and can see, that every 
major version of Python required new versions of Pyscripter. For example added 
Pyscripter 2.5 support to Python 3.3 and Pyscripter 2.1.1 to Python 3.2.

Therefore, I believe the same is required to make Pyscripter able to work with 
Python 3.4.

And no, I'm not capable of doing it, I'm sorry.

/Jesper

Original comment by b17032...@gmail.com on 26 Mar 2014 at 10:10

[GoogleCodeExporter]

Same issue here. I am using both Pythons 3.3.5 and 3.4 and set Pyscripter for 
3.3.5. I guess Pyscripter needs a new version.

Original comment by echagas....@gmail.com on 20 Apr 2014 at 12:46

[GoogleCodeExporter]

still no support for python-3.4.0? I am getting an error "pyscripter could not 
be initialized. Help needed.

Original comment by addawith...@gmail.com on 25 Apr 2014 at 9:30

[GoogleCodeExporter]

I can't use pyscripter until this is fixed - so I have to put up with 
FlashDevelop instead.

Original comment by starbeam...@gmail.com on 25 Apr 2014 at 2:42

[GoogleCodeExporter]

I'm experiencing the same problem. It seems, that pyscripter only "knows" 
python up to 3.3 and doesn't know how to handle future versions. You would 
probbly only need to add two lines of code in 
https://pyscripter.googlecode.com/svn/trunk/frmPythonII.pas somewhere after 
line 1890.

Original comment by ca201...@gmail.com on 27 Apr 2014 at 3:15

[GoogleCodeExporter]

@#9 If I knew how to use svn, I would send the svn equivalent of git's pull
requests to fix the problem if it worked.

Original comment by starbeam...@gmail.com on 27 Apr 2014 at 4:26

[GoogleCodeExporter]

i guess it's the same prob every1 is facing....python 3.4 pyscripter 2.7 
comes up wit an error msg"Python could not be initialised properly. we must 
quit".
Can any1 cum up wit any advice other than opting for lower versions of python

Original comment by pushka...@gmail.com on 12 May 2014 at 12:17

[GoogleCodeExporter]

@#11

I can think of two options:

1. Use a different editor (not preferred)
2. Submit the svn equivalent of a pull request fixing the issue

Unfortunately, I have to use option 1 because I don't know anything about
a) SVN and b) The language that Pyscripter is written in :(

Original comment by starbeam...@gmail.com on 12 May 2014 at 3:41

[GoogleCodeExporter]

Is this problem solved? I mean in other way..? I still have this problem

Original comment by av9...@gmail.com on 30 Aug 2014 at 7:04

[GoogleCodeExporter]

No, the problem is not solved.
The last time the source was modified was Aug 17, 2012.

I'm afraid the project is not maintained anymore.

Original comment by sebastie...@gmail.com on 16 Sep 2014 at 8:44

[GoogleCodeExporter]

@#14 Pyscripter was so good!

Why would anyone decide to throw it away?

Original comment by starbeam...@gmail.com on 17 Sep 2014 at 6:33

[GoogleCodeExporter]

It was good indeed. But now that I am using 3.4 regularly, I moved to Pycharm 
for my Python IDE. Heavier than Pyscripter, but it gets the job done and it is 
maintained.

Original comment by sebastie...@gmail.com on 17 Sep 2014 at 10:55

[GoogleCodeExporter]

@#16 Pycharm looks like a good alternative!

I did not know that it existed. I will probably use that from now on then -
thanks for the suggestion :)

Original comment by starbeam...@gmail.com on 17 Sep 2014 at 5:14

[GoogleCodeExporter]

Thanks a million sebastie!

Original comment by frasker...@gmail.com on 4 Oct 2014 at 8:11

[GoogleCodeExporter]

Here are the projects files with some changes, that maybe could fix this (I 
symply added "python34" everywhere "python33" appeared). If someone knows how 
to compile this PLEASE do it. Pyscripter was so good! There were instructions 
on how to compile this somewhere.

Original comment by ca201...@gmail.com on 4 Oct 2014 at 11:35

Attachments:

• files_original.zip
• files_changed.zip

[GoogleCodeExporter]

Found the instructions! In the zip that comment #19 provides there is a
file called "readme.txt". There are some instructions in there.

The dependency list is quite long, but that is not an issue. The real
problem is "Borland Delphi 2010". I have no idea where to get hold of that
- I think that you might have to pay for it?

I am willing to set up a virtual machine and compile it if necessary.

Original comment by starbeam...@gmail.com on 5 Oct 2014 at 8:33

[GoogleCodeExporter]

@#20:
About Delphi 2010. On the manufacturer's site there was a link to this site: 
https://downloads.embarcadero.com/free/delphi, saying you could download a free 
Trial of Delphi 2010 there. Delphi 2010 is (no longer?) listed, but maybe 
Delphi XE7 could do the job. It would be great if you could re-compile the 
source!

Original comment by ca201...@gmail.com on 5 Oct 2014 at 7:45

[GoogleCodeExporter]

Ok, I will have a go next Wednesday afternoon.

Installing the dependencies will take some time though, not sure how long
it will take.

I will be building on windows 7 unless anyone has any objections.

Original comment by starbeam...@gmail.com on 6 Oct 2014 at 6:02

[GoogleCodeExporter]

For convenience, the contents of the readme.txt can be found here: 
http://notepad.cc/share/gjbGeRYTR2

(This is mainly for my own reference since I am using a virtual machine and the 
host machine does not have the files)

Original comment by starbeam...@gmail.com on 6 Oct 2014 at 4:41

[GoogleCodeExporter]

Update:

I found some time and have set up a virtual machine running Windows 7 
Enterprise from https://modern.ie/en-gb/.
However, half of the things on the list don't even have install instructions...

I don't know where to put them as I don't have experience with Delphi / svn - 
does anyone else know?

The other problem is that Delphi XE7 requires all sorts of personal details 
such as one's phone number, just for the trial - I am not willing to give out 
that information.

Original comment by starbeam...@gmail.com on 6 Oct 2014 at 5:02

[GoogleCodeExporter]

It took me whole long effort to put everything into working state. Most of the 
dependent components required code change to get that working as the versions 
of them might have got changed since past few years :)

Python4Delphi component(s) need to be updated to add the support for Python 
3.4. After updating the components for 3.4 support, encountered issues and 
found the same was reported as bug in Python3.4 bug tracker 
(http://bugs.python.org/issue15422).

I have implemented a workaround and now Pyscripter is working fine with Python 
3.4 :)

Original comment by syed.ali...@gmail.com on 8 Oct 2014 at 3:17

[GoogleCodeExporter]

@#25 could you upload the binaries?

Original comment by ca201...@gmail.com on 8 Oct 2014 at 3:20

[GoogleCodeExporter]

Attached please find the Pyscripter executable, as that is the only binary 
which required change. Make backup of existing Pyscripter.exe and un-archive 
this to pyscripter folder.

Use password "python34" without quotes to un-archive. 

If you have multiple versions of Python installed on your box, use --python34 
command line switch to tell the pyscripter to use Python 3.4.

Original comment by syed.ali...@gmail.com on 8 Oct 2014 at 3:48

Attachments:

• PyScripter-Updated.7z

[GoogleCodeExporter]

Above posted binary is 32bit. 

Original comment by syed.ali...@gmail.com on 8 Oct 2014 at 4:00

[GoogleCodeExporter]

THANK YOU!! It works!

Original comment by ca201...@gmail.com on 8 Oct 2014 at 4:12

[GoogleCodeExporter]

@#27:
maybe you should move the (new) source and binaries to somewhere more easily 
accessible like sourceforge or github.

Original comment by ca201...@gmail.com on 8 Oct 2014 at 6:04

[GoogleCodeExporter]

I get the message that Python could not be properly initialized

Original comment by howie...@gmail.com on 8 Oct 2014 at 6:25

[GoogleCodeExporter]

@#30:
  Not sure if that will be kind of infringement of license as doing that will require to open up a new project/branch of same application on different domain.

Original comment by syed.ali...@gmail.com on 9 Oct 2014 at 1:16

[GoogleCodeExporter]

@#31:

     What Python version is/are installed on your machine? did you invoke the compiled binary posted in thread #27?

Original comment by syed.ali...@gmail.com on 9 Oct 2014 at 1:17

[GoogleCodeExporter]

@#32
The license (http://opensource.org/licenses/mit-license.php) doesn't seem to 
restrict anything as long as you use the same license.

Original comment by ca201...@gmail.com on 9 Oct 2014 at 3:54

[GoogleCodeExporter]

With the above download for 32-bit Windows,
if I run it,
with 32-bit "Anaconda" distribution with Python 2.7 ( not 3.4 ) for Windows 
installed,
there is a modal window with the error message

"The Rpyc module is not available. To use the remote Python Engine download 
Rpyc from http://Rpyc.sf.net and install it", with an abort button "Abort".

If I press the abort key, it loads.

Sincerely
Rolf

Original comment by hemmerl...@gmx.net on 10 Oct 2014 at 12:03

[GoogleCodeExporter]

@#35:
The message tells you, that since you haven't got the rpyc module installed, 
you won't be able to use the external Python interpreter in PyScripter. It is 
shipped with the default download of PyScripter (whose .exe doesn't support 
Python 3.4) but you could install it manually via pip.

Original comment by ca201...@gmail.com on 12 Oct 2014 at 10:02

[GoogleCodeExporter]

Thanks for all that effort. It works!

Original comment by rolandra...@gmail.com on 13 Oct 2014 at 5:30

[GoogleCodeExporter]

Thank you so much for this. I havent found (or managed to get to work) any 
python debugger that works so easy with watches, mouse hover over variables, 
etc. I tried spyder since that seems to be regularly updated but I didnt 
understand how that debugger worked.
Pyscripter just still rocks for python debugging and I was so disappointed that 
it stopped working for python 3.4 that seems to become the "new" 2.7.

Thank you again for your efforts and I hope this can keep pyscripter alive for 
some more years.

Original comment by gamingSl...@gmail.com on 13 Oct 2014 at 8:37

[GoogleCodeExporter]

Thanks for your efforts! Is there any chance to build PyScripter for Windows 
64-bit, with support for Python 3.4?
Cheers,
Willi.

Original comment by op...@ipf.tuwien.ac.at on 22 Oct 2014 at 9:14

[GoogleCodeExporter]

Sorry Willi, I managed to update and build the PyScripter on a virtualbox 
running Windows in 32bit mode, so wasn't able to compile 64bit of this 
excellent piece of software.

//Ali

Original comment by syed.ali...@gmail.com on 13 Nov 2014 at 6:22

[GoogleCodeExporter]

Thanks for the 32-bit version! But, is there any chance to have PyScripter, 
with support for Python 3.4 in 64-bit this time?

Original comment by monbloga...@gmail.com on 9 Jan 2015 at 3:56

[GoogleCodeExporter]

It was a time for PyScripter, now the time is for MS Visual Studio. Sad but 
true. 

Original comment by iltch...@gmail.com on 28 Jan 2015 at 5:33

[GoogleCodeExporter]

!!! no comparison. For a tool from Microsoft, there is no room for
community involvement or imperatives other than commercial profit. If M$
decide to offer a tool like VS cheap / for free, that is entirely at
their capricious whim and behest. If they then decide to remove that
'favour' later on, or to remove some key feature you rely on because it
does not suit their 'game plan', there is stuff all you can do about it.
I have been burned in this way before - Class Server and Embedded Visual
Tools to cite just two examples.

By comparison, in the Open Source community, if you need it badly
enough, you can always DIY. To fix PyScripter, all that was needed was a
coder willing to patch the source to support the new version of Python
and a copy of Delphi to recompile it. PyScripter would have been fixed
many months earlier if it had not been reliant on an another even more
capricious, expensive commercial product to compile it.

Original comment by sgpa...@mainscreen.com on 28 Jan 2015 at 6:38

[GoogleCodeExporter]

Better use your energy to develop spyder - no Delphi at all, just Python. Works 
anywhere where Python & PyQt4 works. Btw Python Tools for Visual Studio (PTVS) 
is under Apache license! :idea:

Original comment by iltch...@gmail.com on 28 Jan 2015 at 9:33

[GoogleCodeExporter]

@#27 
wow man thank you!

Original comment by micha...@gmail.com on 25 Feb 2015 at 7:10