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


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

Re: Embedded python 'scripting engine' inside Python app

Started byChris Angelico <rosuav@gmail.com>
First post2014-11-23 21:35 +1100
Last post2014-11-23 21:35 +1100
Articles 1 — 1 participant

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 Chris Angelico <rosuav@gmail.com> - 2014-11-23 21:35 +1100

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

FromChris Angelico <rosuav@gmail.com>
Date2014-11-23 21:35 +1100
SubjectRe: Embedded python 'scripting engine' inside Python app
Message-ID<mailman.16179.1416738955.18130.python-list@python.org>
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

[toc] | [standalone]


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


csiph-web