On 19 mars 02:58, Fletcher Johnson wrote: > > > >IMO we should: > >* *not infer anything here* > >* check for 2-uple and warn about potential misspelling of the assert > >statement > >* check for literal true (eg True, not empty container, non zero number, > >etc..) > > of false (False, None, 0, etc...) expression and warn about always/never > > verified > > assertion > > I'm not really sure what you are looking for in the literal > false/true cases. Do we want to generate warnings for statements > such as 'assert 5'? > > Currently I only understand that we would want to check assertion > statements where we are issuing a statement such as 'assert (x,msg)' > because the user probably meant assert x, msg. This means that we no > longer care about checking statements like 'assert (x,)' even though > python gives a warning.
right. -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
