Fuckit.py – The Python error steamroller

https://github.com/ajalt/fuckitpy

by aburan28 • 11 years ago

86 42 11 years ago

github.com

ocdtrekkie• 11 years ago

"This module is like violence: if it doesn't work, you just need more of it."

How could anyone not love this tool?

kelvin02• 11 years ago

It's the Serious Sam of Python programming ... moar bullets

bsg75• 11 years ago

s/module/XML/ is another favorite

ljk• 11 years ago

previous discussion - https://news.ycombinator.com/item?id=6858855

wyldfire2• 11 years ago

There's debate in that thread whether this project is satire or not. I must admit it looks remarkably like satire, especially the test suite.

That said, I have met some developers who would find this as an advantage and might actually try to put it into use. Generally these are folks who prefer the default soldier-on-in-the-face-of-errors behavior from sh and perl.

Mithaldu2• 11 years ago

Generally these are folks who prefer the default soldier-on-in-the-face-of-errors behavior from ... perl.

Nobody in the Perl world prefers that, outside of people who are complete newbies. In fact, collectively Perl has been yelling at newbies for decades that anything not containing `use strict;` and `use warnings;` is almost without fail broken code, mainly because there are a lot of very old and outdated tutorials which introduce these modules as optional and/or way too late.

doki_pen• 11 years ago

Works as advertised. I just added it to my project and now all tests are 100% passing! Even 1 == 0!

3pt14159• 11 years ago

Well to be fair...

http://lmgtfy.com/?q=zero+factorial

Roodgorf• 11 years ago

That took me a few seconds, well played.

r3bl• 11 years ago

I'm definitely going to use this thing!

dacox• 11 years ago

The tests are gold

ninetax2• 11 years ago

I've been searching for something similar I saw years ago. It was a python library that would remove "heretical" code or something like that. Any error would be "eradicated".

It was funny! There was a religious or medieval theme or something. I can never find it...

pit• 11 years ago

Vigil, the eternal morally vigilant programming language:

https://github.com/munificent/vigil

ninetax2• 11 years ago

yes! thank you!

jerf• 11 years ago

HN discussion, for your convenience: https://news.ycombinator.com/item?id=5002597

Skunkleton• 11 years ago

This needs SCM support added too it. After all, what use is it if its grand moral vision can be reversed by a simple git checkout?

avian• 11 years ago

In my previous life I was maintaining some backend services. One of the most common reasons for a service dying was a typo in a name in some rarely visited code path. I was tempted to write a similar module that would be a little bit smarter: when some identifier (variable, method, etc.) was not found, instead of raising an exception, try to find a similarly named thing and use that instead. I never did find a good way of implementing that.

insertnickname2• 11 years ago

That's probably for the best.

ChicagoBoy11• 11 years ago

I spilled tea because of laughter induced by your comment. well done.

vlunkr• 11 years ago

Seriously, that's asking for unpredictable behavior. Maybe if it printed the suggestion to the logs and then failed it would be ok.

kelvin02• 11 years ago

How about better testing and path coverage of your code? I hope that was also explored as a way to stabilize your codebase? Otherwise your suggestion does come offa bit as 'cowboy-ish' to say the least ...

HCIdivision17• 11 years ago

I think you might like something like TheFuck? EDIT: This bash commandline completion has been updated to by default wait for the user to verify the replacement command is what they wanted; this pretty much turns this from a terminal Russian Roulette into a kinda handy autosuggestion!

https://github.com/nvbn/thefuck

(Previous discussion: https://news.ycombinator.com/item?id=9396116 )

dgcoffman• 11 years ago

Ruby has a language feature for this and it's pure 100% poison.

http://rubylearning.com/satishtalim/ruby_method_missing.html

riffraff• 11 years ago

that is neither what OP mentioned (automatic matching of a typo) nor poison.

Also, it's from Smalltalk, and found in some ways also in python, objective-c and many others.

pekk2• 11 years ago

That came from Smalltalk, where it was named doesNotUnderstand. It's always difficult to choose between crippling the language and encouraging stupidity.

kevinschumacher• 11 years ago

Looks to be inspired by fuckit.js:

https://github.com/mattdiamond/fuckitjs

So if you want the same thing but for JS give the above a shot.

collyw• 11 years ago

JS doesn't really need an extra library for that, does it?

irl_zebra• 11 years ago

From the test suite:

def test_context_manager(): with fuckit: pass

    assert 'P' != 'NP' # proof is left as an excercise for the reader

jefurii• 11 years ago

There's also this for your text conversion needs.

http://bazaar.launchpad.net/~leonardr/beautifulsoup/bs4/view...

hyperion20102• 11 years ago

Ah, this leads to some of my favourite python bugs. Silent failures because you are catching and ignoring an error in some higher calling function where the error type that was once designed to deal with a single case is now overly broad. I've almost given up using try/catch for KeyErrors as a result.

pekk2• 11 years ago

Python uses try/except, not try/catch. The only reason to catch KeyError is to detect missing keys, so if you are trying to do that, only wrap your dict access rather than wrapping large blocks of code where anything could happen. If you are writing code to ignore errors, that is a bug in your own code, not a python bug.

hyperion20102• 11 years ago

Yes. s/python bugs/bugs in my python code

pikeymick• 11 years ago

The license model is great.

ronjouch2• 11 years ago

Yup. The WTFPL is an actual, (semi)-recognized license used in other projects: https://en.wikipedia.org/wiki/WTFPL

alblue• 11 years ago

It's not an OSI approved license, nor does it actually grant any rights. If you use the WTFPL then you are preventing others from legally using it.

ndr• 11 years ago

From the implementation:

     try:
         [...]
     except IOError:
         # Worst-case scenario we can only catch errors at a granularity
         # of the whole function.
         [...]
     else:
         # If we have access to the source, we can silence errors on a
         # per-expression basis, which is "better".
         [...]

and then:

    def __exit__(self, exc_type, exc_value, traceback):
        # Returning True prevents the error from propagating. Don't silence
        # KeyboardInterrupt or SystemExit. We aren't monsters.

Brilliant.

mcfunley• 11 years ago

Visual Basic has/had this and not as a joke. It was called "On Error Resume Next."

teh_klev• 11 years ago

From last time around:

https://news.ycombinator.com/item?id=6858855

Fuckit.py – The Python error steamroller

Related Stories