Hi Tomas, please get the sources of the cxfreeze plug-in from the source code repository and run it within eric5. If it is okay, I'll publish the plug-in via the plug- in repository.
Regards, Detlev On Mittwoch, 27. April 2011, Tomas Sobota wrote: > Hi Detlev, > > Yes, there are code paths for Python 2. What you propose is reasonable, go > ahead. > > Cheers > Tom > > On Wed, Apr 27, 2011 at 10:56 AM, Detlev Offenbach > <[email protected] > > > wrote: > > > > Hello Tom, > > > > thanks for the patches. I have just a question to the one for > > PluginCxFreeze. > > There seems to be some code paths for Python2. Is this correct? If so, I > > would > > remove them for the eric5 plug-in and do it vice versa for the eric4 > > plug-in > > variant. Furthermore I would change the catch all excepts into "except > > ImportError". > > > > Regards > > Detlev > > > > On Mittwoch, 27. April 2011, Tomas Sobota wrote: > > > Here you are > > > > > > cheers > > > Tom > > > > > > > > > On Tue, Apr 26, 2011 at 1:25 PM, Detlev Offenbach > > > > > > <[email protected]>wrote: > > > > On Dienstag, 26. April 2011, Tomas Sobota wrote: > > > > > Yes, I understand the problem. Anyway I modified slightly two > > > > > scripts of your cxfreeze plugin so that, when in Windows, the > > > > > plugin makes more efforts to find the Python installation path. I > > > > > would gladly submit these changes to your consideration. In which > > > > > form and where should I send > > > > > > > > them? > > > > > > > > Send them as a unified diff to me. > > > > > > > > > Tom Sobota > > > > > Madrid, Spain > > > > > > > > > > On Tue, Apr 26, 2011 at 12:54 PM, Detlev Offenbach > > > > > <[email protected] > > > > > > > > > > > wrote: > > > > > > > > > > > > On Sonntag, 24. April 2011, Tomas Sobota wrote: > > > > > > > I finally got to install (thanks, Tobias!) and make work the > > > > > > > cxfreeze plugin for Eric5. But it is not straightforward on > > > > > > > Windows. > > > > > > > > > > > > > > First, I installed everything on a 64 bit Win 7. In this > > > > > > > environment, cxfreeze installs a bat file called cxfreeze.bat > > > > > > > in the Python > > > > > > > > Scripts > > > > > > > > > > > folder, which in a standard installation of the latest Python 3 > > > > is > > > > > > > > > at C:\Python32\Scripts. > > > > > > > > > > > > > > However, in the cxfreeze.bat file Python 3 gets called like > > > > > > > "C:\Python32-64\Python32-64.exe", so it is never found. This > > > > > > > problem > > > > > > > > is > > > > > > > > > > > attributable to the cxfreeze installation and not to the > > > > > > > plugin, > > > > > > > > > > > > naturally. > > > > > > > > > > > > > So I changed the cxfreeze.bat so that it points to > > > > > > > > > > > > C:\Python32\Python.exe. > > > > > > > > > > > > > But the plugin still would not work, with a diagnostic that > > > > > > > "the cxfreeze executable was not found". Looking at the plugin > > > > > > > sources > > > > I > > > > > > > > > noticed that > > > > > > > > > > > > it > > > > > > > > > > > > > is looking for cxfreeze.bat in the path. The problem with this > > > > > > > > approach > > > > > > > > > > in > > > > > > > > > > > > > a Windows installation is that the Python scripts folder never > > > > gets > > > > > > > > > appended to the path during Python installation. Once I > > > > > > > appended the scripts folder to the path manually, the plugin > > > > > > > works correctly. > > > > > > > > > > > > > > In a 32 bit Win 7 installation, the cxfreeze.bat file correctly > > > > > > > > points > > > > > > > > > > > to C:\Python32\Python.exe, so it doesn't need to be edited. But > > > > the > > > > > > > > > path problem is the same as above. > > > > > > > > > > > > > > I guess that on a Linux or Unix box all these problems don't > > > > arise. > > > > > > > > > Later > > > > > > > > > > > > I > > > > > > > > > > > > > will install Python32/PyQt/Eric5/cxfreeze in my FreeBSD box and > > > > > > > > verify > > > > > > > > > > what > > > > > > > > > > > > > happens in that environment. > > > > > > > > > > > > > > Tom > > > > > > > > > > > > Due to the fact, that eric cannot know exactly where all the > > > > > > tools are installed, it assumes, that they are available via the > > > > > > executable path setting. If the scripts folder doesn't get added > > > > (or > > > > > > > > any other > > > > > > > > directory > > > > > > > > > > on non Win machines) you have to add it to the PATH variable. > > > > > > Maybe > > > > I > > > > > > > > should offer a configuration option where you can set the path to > > > > the > > > > > > > > cxfreeze executable. Feedback is welcome. > > > > > > > > > > > > Detlev > > > > > > -- > > > > > > Detlev Offenbach > > > > > > [email protected] > > > > > > > > -- > > > > Detlev Offenbach > > > > [email protected] > > > > -- > > Detlev Offenbach > > [email protected] -- Detlev Offenbach [email protected] _______________________________________________ Eric mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/eric
