Dieter Maurer wrote:
A colleague of mine will be very happy:

  The hundreds of (mostly stupid deprecation) warnings prevent him
  to efficiently find the true problems in the test runner reports.

In principle, he could fix the warnings -- but they (mostly) come
not from our code but third party one. And, if possible, he
would perfer not to such third party code...

So be explicit about this and add warn filters to your zope.conf, they work just fine in testing. (I have a big chunk of them for Plohn 2.1 if you're interested)

Using the new option will mean you don't get any warnings of problems coming from your code :-(

Chris

--
Simplistix - Content Management, Zope & Python Consulting
           - http://www.simplistix.co.uk

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

Reply via email to