[Clam-devel] Re: Task Runner removed?

[David García Garzón]

Py2exe is something we should aboard some time soon to enable python scripts 
execution in windows, as we need either installing Python from the Annotator 
installer or generating executables from the python scripts.

There is a python script 'freeze.py' that comes with the regular python 
distribution that generates c sources that compile a python script as a 
binary application. We could try that or py2exe.



On Diumenge 17 Agost 2008, David García Garzón wrote:
> On Diumenge 17 Agost 2008, Jun Jun wrote:
> > yes, in the commit rev11997 I removed the Task Runner in Annotator, but
> > it is not for that problem I met (which is temporarily calmed down by
> > commenting out the 'addDockWidget').
> >
> > I replaced the Task Runner with QProcess::execute to check whether the
> > second one can execute .py executable file in Annotator. The answer is
> > NO. By the way, you used to suggest the second: "Maybe using taskRunner
> > is not such a good idea, because it makes the whole thing asyncronous,
> > meaning that while saving, the user can manipulate the descriptors, and
> > you have to deal with the state when the task is done, which is
> > complex...."
>
> Yes, but i was thinking on a modal taskRunner window which gives no access
> to the rest of the application functionality. Current solution just freezes
> the interface until the extractor is done which may seem that the
> application is not responding.
>
> > The Task Runner can be reverted, if needed?
>
> If it implies not advance and you still have python problems, yes, you
> should revert it. It gives the user information on what's happening and we
> should not loose that.
>
> I think that the problem is that the system doesn't consider python scripts
> as executables. So the solution is to call python interpret. I can figure
> out some solutions:
>
> * First check whether the problem is that python has registered .py files
> as executable but we are trying to execute an extensionless script (which
> is nice on linux but maybe inconvenient on windows) Try whether executing
> scripts with the .py extension work, if so, do a caller script that
> redirects the call to the extensionless script.
> * Another solution could be configuring the extractor as 'python script.py'
> instead of 'script.py'. That could work but i think it won't. Just because
> in command + parameter list interface of QProcess, the first is the command
> and we are adding the script which is a parameter in this form.
> * So, the next would be try the same using the single string interface. It
> should work but the problem here is handling properly song files with
> spaces. * Using an intermediate .bat file that does the 'python script.py'
> call. * Using py2exe or similar in windows
>
> > Maybe that problem can be fixed by the replacement. I'll try it anyway.
> > (intending to sacrifice this sunday to gain the commit rev12000!!)
>
> ¬¬   ;-)



-- 
David García Garzón
(Work) dgarcia at iua dot upf anotherdot es
http://www.iua.upf.edu/~dgarcia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.clam-project.org/pipermail/clam-devel-clam-project.org/attachments/20080817/775fc233/attachment.sig>