On 05/21/2012 04:49 AM, Gediminas Paulauskas wrote:
2012/5/20 Tres Seaver <tseaver@palladion.com>:
On 05/19/2012 07:23 PM, Jim Fulton wrote:
On Sat, May 19, 2012 at 5:59 PM, Tres Seaver <tseaver@palladion.com> wrote: They already do: 4.0.0 makes them exceptions under Python3: that fact was actually my rationale for the warnings under Python2, to allow folks to find and remediate them before porting.
If they are exceptions under Python 3, developers will get them and have to fix when porting to Python 3. There is a lot of other work to be done at the same time. But under Python 2, implements and friends continue to work, so the warnings are very annoying.
I will release a 4.0.1 silencing the warnings unless somebody speaks up in their favor.
Please, only warn on Python 3.
On Python3, it *needs* to be an exception: code which still uses the class advice APIs won't work. Tres. -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com