Issue 36 in deap: Creator enhancement - warning with classes having the same name

[de...@googlecode.com]

Status: Accepted
Owner: felix.antoine.fortin
Labels: Type-Review Priority-Medium

New issue 36 by felix.antoine.fortin: Creator enhancement - warning with
classes having the same name
http://code.google.com/p/deap/issues/detail?id=36

I have just pushed a modification to the creator that I would like to be
reviewed and commented.

The problem: if a user create two classes with the creator.create function
and both of these classes have the same name, the first created class will
be overwritten and no warning will be expressed. While this can be
tolerable if the creation of classes could only occur in the same module,
where it would be relatively easy to find out that two classes with the
same name have been created, if the classes creation is done in multiple
module, chaos will ensue.

I think the global aspect of class creation with the creator has its
benefits. However, I think we should warn users of potential problem with
this very aspect.

See revision bf3204c3e5fc

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[de...@googlecode.com]

Updates:
Labels: Milestone-Release1.1.0

Comment #1 on issue 36 by felix.antoine.fortin: Creator enhancement -

warning with classes having the same name
http://code.google.com/p/deap/issues/detail?id=36

(No comment was entered for this change.)

[de...@googlecode.com]

Updates:
Status: Verified

Comment #2 on issue 36 by f.derain...@gmail.com: Creator enhancement -

warning with classes having the same name
http://code.google.com/p/deap/issues/detail?id=36

Accepted see github