Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

FIOC exception classes

Name: Anonymous 2012-05-30 5:35

Which approach do you prefer:

1. Create new exceptions for each class of error in your libs.

2. Just use stuff from the exceptions module most of the time and create new exceptions when using a standard one is really inappropriate.

My colleagues strongly prefer #1, and go around making dozens of FilePermissionsError or ValueErrorBecauseFuckYou.  They are also OOP and Patterns nuts.  I am not a very happy man because I have to import their horde of bullshit exceptions into my modules instead of just using standard classes.

Name: Anonymous 2012-06-22 8:22

>>42
That won't work when you change the directory. Use >>43 instead.

Also, be sure to put:
cat <<EOF
$(uname -o) [Version $(uname -r)]
Copyright (c) $(date +%Y) Richard Matthew Stallman.  All freedoms respected.
EOF

at the end of your .bashrc

Result:
GNU/Linux [Version 3.4.2-4.fc17.x86_64]
Copyright (c) 2012 Richard Matthew Stallman.  All freedoms respected.
C:\home\chris>

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List