for me I just want to hijack the interpreter so I don't have to write my own. no imports, no sockets.

I'm talking about the history beyond why rexec and Bastion, and restricted execution, were removed from Python in the 2.x days. See https://python.readthedocs.io/en/v2.7.2/library/restricted.h... , "In Python 2.3 these modules have been disabled due to various known and not readily fixable security holes."

They started because back in the 1.x days there was a Python web browser called Grail, and the hope was to support restricted Python applets in Grail.

Or from 10 years ago, read https://lwn.net/Articles/574215/ about the failure of 'pysandbox' where one of the ways to break out was to "[use] a traceback object to unwind the stack frame to one in the trusted namespace, then use the f_globals attribute to retrieve a global object." ... "Stinner's tale should serve as a cautionary one to anyone considering a CPython-based solution".

You might consider RestrictedPython at https://restrictedpython.readthedocs.io/en/latest/ which supports only a subset of Python, via AST-walking to limit what the code can do. I have no experience with it.

edit: here are my silly little patches: https://github.com/hananbeer/cpython-toy-sandbox/commit/fa3f...

this is of course assuming exec(globals={..}) without certain builtins and is, again, not expected to use system apis like files or sockets or anything.

    d = {"__builtins__": {"print": print}}

    exec("""

    def delay_until_gc():
      try:
        try:
          yield 1
        finally:
          print((1).__class__.__bases__[0].__subclasses__()[:3])
      except:
        raise

    it = delay_until_gc()
    it.__next__()

    """, d, d)
    del d
    print("Finished exec.")

  Finished exec.
  [<class 'type'>, <class 'async_generator'>, <class 'bytearray_iterator'>]

  import gc
  toybox(1)
  exec(..., d, d)
  del d
  gc.collect()
  toybox(0)

If you allow any mutable object into the globals or locals dictionary, such that the exec'ed code can attach something to it, then you can't even use gc.collect() to ensure the exec'ed code can no longer be executed.

ps. browsers basically do that with javascript

for me I just want to hijack the interpreter so I don't have to write my own. no imports, no sockets.

for the record, I found liveportrait to be well within the uncanny valley. it looks great for ai generated avatars, but the difference is very perceptually noticeable on familiar faces. still it's great.

There is "Is identical", "looks identical" and "has lost sufficient detail to clearly not be the original." - being able to differentiate between these three states is useful.

The other two are variations of lossy.

Calling one of them "perceptually lossless" is cheating, to the disadvantage of algorithms that honestly advertise themselves as lossy while still achieving "looks identical" compression.

It's also used in the first paragraph of the Wikipedia article on the term "transparency" as it relates to data compression.

and before you get discouraged by my story know that my first reaction to this incident was "damn these are my favorite headphones", I had them for years, travelled with them, use them practically daily and they still look brand new.

can't say I'm a big user of the noise cancellation or even ambient sounds or bluetooth. just aux in the laptop and on planes, it's amazing.

9.99/10 ears still ringing, would buy again.

powered by D3

At what point, at what scale, (ie. 1bn. users) does it become humanly impossible to offer support? To scale offering "human" support, that is.-

At some point the "right to talk to a human" will become regulated ...