On Sat, Dec 20, 2003 at 10:55:48AM -0500, Aahz wrote: > > to some extent, i didn't care about things like __class__ because > > 1) the users weren't that bright. > > 2) the user's weren't that hostile. > > Yup. By "what's the point?" I didn't mean that there were no use cases; > the problem is that such cases are not frequent enough to justify the > effort. ... which is why i made some recommendations to add in the concept of run-time-defineable public and protected class interfaces. such a concept 1) fits with the principle of capabilities 2) is an enhancement that goes beyond the small requirements of restricted execution 3) offers a means through which rexec can be implemented. > > rexec fitted the requirements perfectly - and it still does: it's > > just been disabled and also changed into something that stops even > > the library functions from writing to log files. > > i couldn't even use the MySQLdb module which was kinda critical to > > the database-driven backend. > > Well, you're free to maintain rexec as a separate project (or borrow > from the still-maintained Zope system). But anything shipped as part of > Python can't afford to assume your points 1) and 2). i appreciate that. so it turns into a wishlist: a class named RExecDontUseThisItsBrokenForMostPeople and a class named RExec which simply pulls that exception. l.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4