Creator's try/except often hide initialization error about deap HOT 6 CLOSED

From [email protected] on July 17, 2010 07:05:41

Seems that issues doesn't display code correctly, sorry for the markups

from deap.

From [email protected] on August 15, 2010 07:37:21

It seems that that the TypeError catching might be an artifact from version 0.4 or before, and might be removed in future release as it is no more related to the initialization of of a single base class (multiple inheritance was allowed in older versions).

from deap.

From [email protected] on August 17, 2010 17:29:28

By the way, the transformation of Warnings in Errors is not necessary, we can still catch the warning.

Status: Fixed

from deap.

From felix.antoine.fortin on August 17, 2010 18:38:13

The warning could not be catch with a certain version of Python, which explains the transformation.

from deap.

From [email protected] on August 17, 2010 19:26:07

It seems that the DeprecationWarning was thrown in Python2.5. In Python2.6, initializing the class "object" with arguments does throw a TypeError which is good since initializing an "object" with arguments is not what is supposed to be done and might lead to unwanted/misleading behavior.

I'm in favor that we remove completely the try/except clause from line 51 of creator as an error throw is better than the initialization of the base class with no arguments. I simply don't see when this could be ok.

Status: Started

from deap.

From [email protected] on August 18, 2010 13:34:04

This issue has been fixed, the TypeError seems not to be necessary but the DeprecationWarning is. The later is raised when the base class does not have override the init method of the object class.

Changes have been made in the hg trunk, tests have been run and examples sill work.

Status: Verified

from deap.