New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Calling LBYL an anti-pattern is not exactly correct #125

Open

tucked opened this issue May 15, 2019 · 0 comments

tucked commented May 15, 2019

https://mail.python.org/pipermail/python-dev/2014-March/133118.html

I disagree with the position that EAFP is better than
LBYL, or "generally recommended" by Python. (Where do you get that? From
the same sources that are so obsessed with DRY they'd rather introduce a
higher-order-function than repeat one line of code? :-)

IMO, the primary motivation for EAFP over LBYL is avaoiding TOCTOU bugs.

dmtucker mentioned this issue

readability/EAFP: update to Py 3, use specific exception, add race condition note #144

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment