On Fri, 04 Aug 2006 11:23:10 -0700, Josiah Carlson <[EMAIL PROTECTED]> wrote: > >There's one problem with generating a warning for 2.5, and that is the >same problem as generating a warning for possible packages that lack an >__init__.py; users may start to get a bunch of warnings, and be unaware >of how to suppress them. > >All in all though, I'm +0 on the warning, and +1 on it not raising an >exception in 2.5 . >
Um. This warning would indicate a bug in the code which will lead to actual misbehavior in a future version of Python. The __init__.py warning would have indicated a deployment configuration which didn't actually cause any misbehavior. They aren't the same case at all, unless you think that all warnings should be classed this way (a position I do not think is completely unreasonable, but since you singled out the package warning by way of comparison, I assume this is not the argument you are trying to make). Jean-Paul _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
