Re: [boinc_dev] Command as main program w/out files

2009-06-16 Thread Jeremy Cowles
Windows and Mac seem pretty straight forward and easy to compile in advance, but would you have to compile on the client for Linux or would you just make assumptions about what libraries are present? At the moment I'm having bigger problems compiling it on Windows. The prebuilt Python

Re: [boinc_dev] Command as main program w/out files

2009-06-16 Thread Nicolás Alvarez
El Martes 16 Jun 2009 15:24:42 Jeremy Cowles escribió: Windows and Mac seem pretty straight forward and easy to compile in advance, but would you have to compile on the client for Linux or would you just make assumptions about what libraries are present? At the moment I'm having

Re: [boinc_dev] Command as main program w/out files

2009-06-15 Thread Michael Tughan
program w/out files

Re: [boinc_dev] Command as main program w/out files

2009-06-14 Thread yoyo
Jeremy Cowles wrote: El Sáb 13 Jun 2009 18:09:30 Jeremy Cowles escribió: Here is my Python-BOINC wrapper. It *embeds* the Python interpreter, so the process-level wrapper isn't needed. http://bitbucket.org/nicolas17/pyboinc/ So embedding the interpreter looks really straight

Re: [boinc_dev] Command as main program w/out files

2009-06-14 Thread Nicolás Alvarez
El Sáb 13 Jun 2009 20:17:06 Jeremy Cowles escribió: Windows and Mac seem pretty straight forward and easy to compile in advance, but would you have to compile on the client for Linux or would you just make assumptions about what libraries are present? At the moment I'm having bigger problems

Re: [boinc_dev] Command as main program w/out files

2009-06-13 Thread Jeremy Cowles
El Vie 12 Jun 2009 16:21:06 David Anderson escribió: Jeremy Cowles wrote: Agreed. Also, it would be nice to expose the suspend/quit/checkpoint api (boinc_status) into Python, or is this already available? This page has a link to a python binding of the BOINC API:

Re: [boinc_dev] Command as main program w/out files

2009-06-13 Thread Nicolás Alvarez
El Sáb 13 Jun 2009 18:09:30 Jeremy Cowles escribió: El Vie 12 Jun 2009 16:21:06 David Anderson escribió: Jeremy Cowles wrote: Agreed. Also, it would be nice to expose the suspend/quit/checkpoint api (boinc_status) into Python, or is this already available? This page has a

Re: [boinc_dev] Command as main program w/out files

2009-06-12 Thread David Anderson
Not currently. The main program must be a file downloaded from the server. We could potentially change this, but I'm not sure it would be useful. If the BOINC client were to invoke a python interpreter directly, the resulting job would not response to suspend or quit commands, and its CPU time

Re: [boinc_dev] Command as main program w/out files

2009-06-12 Thread Nicolás Alvarez
El Vie 12 Jun 2009 15:50:03 Jeremy Cowles escribió: Agreed. Also, it would be nice to expose the suspend/quit/checkpoint api (boinc_status) into Python, or is this already available? You don't need to notify the Python code when it's suspended, since it will be suspended at the process level

Re: [boinc_dev] Command as main program w/out files

2009-06-12 Thread David Anderson
Jeremy Cowles wrote: Agreed. Also, it would be nice to expose the suspend/quit/checkpoint api (boinc_status) into Python, or is this already available? This page has a link to a python binding of the BOINC API: http://boinc.berkeley.edu/trac/wiki/PythonApps This is probably out of date but