Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #81362
| From | Stefan Behnel <stefan_ml@behnel.de> |
|---|---|
| Subject | Re: Embedded python 'scripting engine' inside Python app |
| Date | 2014-11-23 13:49 +0100 |
| References | <05D7659F-9D0B-466B-833E-8454DCF0F57A@gmail.com> <CAPTjJmqCgvgUCahVnnTj0+jJgvUrugk2501q7Pci2ZB3q-1J+Q@mail.gmail.com> <0B2C4A0D-401C-446E-9EE6-C04791F904DB@gmail.com> <CAPTjJmrQqqVNLXf8PP+sCT6USbvshciQBonK=L+SdM-4TwHmYQ@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.16181.1416746999.18130.python-list@python.org> (permalink) |
Chris Angelico schrieb am 23.11.2014 um 11:35: > On Sun, Nov 23, 2014 at 9:28 PM, Patrick Stinson wrote: >> 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. :) As the author of Lupa, I know that some people have successfully and safely embedded Lua in Python as a simple, small and object-oriented scripting language in a sandbox. https://pypi.python.org/pypi/lupa The overall syntax isn't quite as great as that of Python, but as long as you mostly stick to "here's a bunch of functions you can call" or "here's an object, go and call some methods on it" kind of APIs, there isn't all that much of a difference either. Stefan
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Embedded python 'scripting engine' inside Python app Stefan Behnel <stefan_ml@behnel.de> - 2014-11-23 13:49 +0100
csiph-web