Setting a computed attribute triggers two change events

[emileber]

Related to the line 486, if I set a computed attribute, the following events are triggered:

• change:myField change with (model, value) from epoxy,
• standard backbone change with (model, options)

This has the side-effect of calling every listeners of the change event for this model twice, and with the wrong params the first time.

I don't get when this would be necessary (and a good idea)? Am I missing something?

[jekuno]

Please also have a look at #138 regarding this issue.