Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #81444 > unrolled thread

Re: Embedded python 'scripting engine' inside Python app

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Embedded python 'scripting engine' inside Python app Patrick Stinson <patrickkidd@gmail.com> - 2014-11-23 04:20 -0900

#81444 — Re: Embedded python 'scripting engine' inside Python app

I think this is the way I’ll take it, and for all the same reasons. The only way they can break it is if they really want to. I guess anything other Franken-apps would be interesting to hear about too. And I’ll still stick it on the app store.


> On Nov 23, 2014, at 1:35 AM, Chris Angelico <rosuav@gmail.com> wrote:
> 
> On Sun, Nov 23, 2014 at 9:28 PM, Patrick Stinson <patrickkidd@gmail.com> wrote:
>> Thanks for your great reply. I even augmented the reloading with the same
>> dict by clearing all of the non-standard symbols from the dict. This
>> effectively resets the dict:
> 
> You may as well start with an empty dict and then pick up the few
> things you want, I think.
> 
>> Is there a better and more secure way to do the python-within-python in
>> order allow users to automate your app?
> 
> More secure? Basically no. You could push the inner script into a
> separate process, but I would recommend simply acknowledging the
> insecurity. Embrace the lack of security and call it a debugging
> feature - make it possible to introspect, control, manipulate internal
> structures. Feature, not flaw. :)
> 
> ChrisA
> -- 
> https://mail.python.org/mailman/listinfo/python-list

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web