Hi,
With regard to sandboxing, there is PyPy:
http://pypy.readthedocs.org/en/latest/sandbox.html
although this would be a little complicated, as it's not just a
cPython package or extension or whatever, but an alternative to
cPython...
Oh, and in general, there does exist some precedent for thi
Hi Peter,
On Wed, May 4, 2011 at 6:56 PM, Pete Meyer wrote:
>
> - Sandboxing would be ideal, but I don't know if there's infrastructure in
> python to support it. It might be easier to filter fetched scripts to only
> allow a restricted subset of python functions (the ast library looks like it
Hi,
From a security perspective, it seems like the ideas on the wiki page
are all related to securing the remote source. It might be worth
considering what could be done to minimize how much pymol has to trust
the remote source or the network.
A few ideas:
- Sandboxing would be ideal, but
Hi Michael,
it's a good idea! A working proof-of-concept userland script should be
quick to implement I guess.
I think the design should go together with the planned new plugin
architecture (http://pymolwiki.org/index.php/PluginArchitecture ).
Cheers,
Thomas
Michael Lerner wrote, On 05/04/
Sounds awesome! Adding an option to chose whether to load the script every
time PyMol launches, or just fetch and use it once, would be even more
convenient. It would resemble installation of packages from Linux
repositories ;)
On 4 May 2011 18:59, Michael Lerner wrote:
> Hi all,
>
> I'm consid
Hi all,
I'm considering building in a mechanism for automatically fetching scripts
from the PyMOL Wiki. The goal is to allow users to say
fetch findSurfaceResidues, type=script
findSurfaceResidues doShow=True, cutoff=0.5
The convenience benefits are obvious, especially for new users, and I think
