4 ms·

This isn't abuse. This is abuse: https://github.com/ajalt/fuckitpy https://github.com/ajalt/fuckitpy

sifoo 9y ago
The semitic versioning scheme makes up for it, though; brilliant.
quickthrower2 9y ago
Is this essentially "On Error Resume Next" for Python? [0] https://msdn.microsoft.com/en-us/library/aa266173(v=vs.60).aspx https://msdn.microsoft.com/en-us/library/aa266173(v=vs.60).a... "On Error Resume Next specifies that when a run-time error occurs, control goes to the statement immediately following the statement where the error occurred where execution continues. Use this form rather than On Error GoTo when accessing objects."
- electroly 9y ago
  The point of "On Error Resume Next" is that you can check the error code on the next line. It changes the error handling from exception-style to error-return-style.
kortex 9y ago
This brings me maniacal joy :D. One time, I had to make the opposite functionality: a streaming module was eating all errors inside a while True loop. This was making debugging really aggravating. So I made a DieWithHonor exception that caused the program to call process.kill() on its own PID >:D
jamesdutc 9y ago
Absolute child's play compared to: https://gist.github.com/llllllllll/b1ac68a6b77535a64c0b13bfd887c05a https://gist.github.com/llllllllll/b1ac68a6b77535a64c0b13bfd... (Python's LOAD_FAST bytecode does `fastlocals[i]`: how can we abuse the lack of bounds checking on this array access?) (We've also discussed potential extensions this to approach "lift" C-extension code in bytestrings into interpreter objects. This would be useful to escalate existing interpreter attacks in environments that try to lock things down.)
- Myrmornis 9y ago
  That's amazing, but doesn't work for me (python 3.6.4). Not sure I'm going to try debugging it... t = (0, 1) tuple_setitem(t, 0, 99) print(t) # (0, 1) EDIT: Ah, it seems to work in 3.6.3
dingo_bat 9y ago
> The web devs tell me that fuckit's versioning scheme is confusing, and that I should use "Semitic Versioning" instead. So starting with fuckit version ה.ג.א, package versions will use Hebrew Numerals. Heh.
- golergka 9y ago
  ה.ג.א is 5.3.1, not 4.8.1: https://github.com/ajalt/fuckitpy/blob/master/setup.py#L16 https://github.com/ajalt/fuckitpy/blob/master/setup.py#L16
  - jwilk 9y ago
    It doesn't use SV yet (as evidenced by the fact it's stil using Arabic numerals).
andreareina 9y ago
There was a (proposed? I don't remember) library or language that deleted source lines that caused errors. Repeated invocations would eventually yield source that did not produce any errors. Of course, it might be an empty file...
- Liquid_Fire 9y ago
  You must be thinking of this: https://github.com/munificent/vigil https://github.com/munificent/vigil
  - andreareina 9y ago
    That's the one!

The semitic versioning scheme makes up for it, though; brilliant.

Is this essentially "On Error Resume Next" for Python? [0] https://msdn.microsoft.com/en-us/library/aa266173(v=vs.60).aspx https://msdn.microsoft.com/en-us/library/aa266173(v=vs.60).a... "On Error Resume Next specifies that when a run-time error occurs, control goes to the statement immediately following the statement where the error occurred where execution continues. Use this form rather than On Error GoTo when accessing objects."

electroly 9y ago
The point of "On Error Resume Next" is that you can check the error code on the next line. It changes the error handling from exception-style to error-return-style.

kortex 9y ago

This brings me maniacal joy :D. One time, I had to make the opposite functionality: a streaming module was eating all errors inside a while True loop. This was making debugging really aggravating. So I made a DieWithHonor exception that caused the program to call process.kill() on its own PID >:D

jamesdutc 9y ago

Absolute child's play compared to: https://gist.github.com/llllllllll/b1ac68a6b77535a64c0b13bfd887c05a https://gist.github.com/llllllllll/b1ac68a6b77535a64c0b13bfd... (Python's LOAD_FAST bytecode does `fastlocals[i]`: how can we abuse the lack of bounds checking on this array access?) (We've also discussed potential extensions this to approach "lift" C-extension code in bytestrings into interpreter objects. This would be useful to escalate existing interpreter attacks in environments that try to lock things down.)

Myrmornis 9y ago
That's amazing, but doesn't work for me (python 3.6.4). Not sure I'm going to try debugging it... t = (0, 1) tuple_setitem(t, 0, 99) print(t) # (0, 1) EDIT: Ah, it seems to work in 3.6.3

dingo_bat 9y ago

> The web devs tell me that fuckit's versioning scheme is confusing, and that I should use "Semitic Versioning" instead. So starting with fuckit version ה.ג.א, package versions will use Hebrew Numerals. Heh.

golergka 9y ago
ה.ג.א is 5.3.1, not 4.8.1: https://github.com/ajalt/fuckitpy/blob/master/setup.py#L16 https://github.com/ajalt/fuckitpy/blob/master/setup.py#L16
- jwilk 9y ago
  It doesn't use SV yet (as evidenced by the fact it's stil using Arabic numerals).

andreareina 9y ago

There was a (proposed? I don't remember) library or language that deleted source lines that caused errors. Repeated invocations would eventually yield source that did not produce any errors. Of course, it might be an empty file...

Liquid_Fire 9y ago
You must be thinking of this: https://github.com/munificent/vigil https://github.com/munificent/vigil
- andreareina 9y ago
  That's the one!