Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Subject: Re: Embedded python 'scripting engine' inside Python app
From: Patrick Stinson <patrickkidd@gmail.com>
In-Reply-To: <CAPTjJmok5WwvMZymSyssVy-sD23zbw6fpPiyEc-PV3WHdJJoeA@mail.gmail.com>
Date: Mon, 24 Nov 2014 22:38:48 -0900
Content-Transfer-Encoding: quoted-printable
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> <CCBF6B5F-8F53-4B57-9F61-41FA33EC8E67@gmail.com> <CAPTjJmok5WwvMZymSyssVy-sD23zbw6fpPiyEc-PV3WHdJJoeA@mail.gmail.com>
To: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <python-list@python.org>
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.16271.1416901139.18130.python-list@python.org>
Lines: 60
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:81492


> On Nov 23, 2014, at 4:57 AM, Chris Angelico <rosuav@gmail.com> wrote:
>=20
> On Mon, Nov 24, 2014 at 12:20 AM, Patrick Stinson =
<patrickkidd@gmail.com> wrote:
>> I think this is the way I=E2=80=99ll 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=E2=80=99ll still stick it on the app store.
>>=20
>=20
> (Please note, the convention on this list/newsgroup - as with most
> tech lists - is to put your text underneath what you're quoting -
> so-called "bottom-posting" or "interleaved" style.)
>=20
> Yep. I got in some trouble for doing this at my last salaried
> employment, because the boss couldn't get his head around the idea
> that an XKCD 936-compliant password is secure enough for a code
> executor, and that the absence of a code executor makes debugging much
> harder. (In the end, I just renamed it to "calculator" so it wasn't so
> obvious, and left it there. Debugging is important.) In my open-source
> MUD client, Gypsum, there's a code executor built-in, which I use
> regularly as a simple calculator, and also to manipulate the program's
> internals. Some examples:
>=20
>> /x 123+456*789
> 359907
>> /x asin(.5)*180/3.14159
> 30.0000253399374
>> /x "Test "*5 + "Haha"
> "Test Test Test Test Test Haha"
>> /x window.mainwindow.iconify()
> GTK2.Window
> (and the main window has just been minimized, aka iconified)

Thanks for the stories in this and the other thread. I love these =
interesting problems that push the limits :)


>=20
> Basically, any expression that I type after "/x" will be parsed and
> executed as code. There's no sandboxing at all; it's executed in its
> own globals() and locals(), but if it wants to tinker with external
> state, it's free to do that. Since all the code is there for the user
> to peruse anyway, I don't distinguish between "this you may do" and
> "this you may not do", but instead between "this is pledged to be
> supported throughout this major version" and "this is undocumented,
> use at your own risk" - on the understanding that most of the latter
> category is actually pretty stable, and can happily be used anyway.
>=20
> Interpreted languages tend to make this kind of thing fairly easy, and
> on the day you have a weird error that you can't figure out, you will
> be no end of glad you have this. No triggering a core dump and then
> doing a post-mortem, just examine state live, using the language's
> natural syntax.
>=20
> ChrisA
> --=20
> https://mail.python.org/mailman/listinfo/python-list