Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #81358
| References | <05D7659F-9D0B-466B-833E-8454DCF0F57A@gmail.com> <CAPTjJmqCgvgUCahVnnTj0+jJgvUrugk2501q7Pci2ZB3q-1J+Q@mail.gmail.com> <0B2C4A0D-401C-446E-9EE6-C04791F904DB@gmail.com> |
|---|---|
| Date | 2014-11-23 21:35 +1100 |
| Subject | Re: Embedded python 'scripting engine' inside Python app |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.16179.1416738955.18130.python-list@python.org> (permalink) |
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
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Embedded python 'scripting engine' inside Python app Chris Angelico <rosuav@gmail.com> - 2014-11-23 21:35 +1100
csiph-web