> > I don't see why. As Chris said, side effects in asserts are nothing new > and >
Indeed -- this new feature makes it easier to affect the local scope in all sorts of new places. It was decided that the additional complexity is worth it to make the language more expressive, and it was also decided not to try to "lock down" this new feature to only "appropriate" places. > this PEP is not the one to do something about it. Hmm --- not sure if it's PEP-worthy, but I'd sure love to see the community make a strong stance that: asserts are for tests, and only for tests Which doesn't necessarily mean that assert statements only exist in test code (though I personally follow that practice), but it does mean that assert statements, wherever they live, should not be counted on at run time, ever. -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
