➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients asvetlov, barry, brett.cannon, chris.jerdonek, cvrebert, eric.snow, ezio.melotti, maker
Date 2013-02-11.15:40:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1360597240.54.0.959928685756.issue15767@psf.upfronthosting.co.za>
In-reply-to
Content 
For me, it mostly comes down to whether end-users are expected to see such errors generally or not.  We see ImportErrors all the time, and they are clearly errors.  If we're expected to see and deal with MNF, and if in such cases it's generally considered an error, then MNFError is better.  If it's mostly an internal/hidden thing, then MNF doesn't bother me.
History
Date User Action Args
2013-02-11 15:40:40barrysetrecipients: + barry, brett.cannon, ezio.melotti, cvrebert, asvetlov, chris.jerdonek, maker, eric.snow
2013-02-11 15:40:40barrysetmessageid: <1360597240.54.0.959928685756.issue15767@psf.upfronthosting.co.za>
2013-02-11 15:40:40barrylinkissue15767 messages
2013-02-11 15:40:40barrycreate