Sub-Module .set() .get() behaviour is not as expected #8

wellcaffeinated opened this Issue Jul 19, 2012 · 1 comment


None yet

2 participants



I love Stapes, but its submodule behaviour is really getting me down. I'm pretty sure this is a bug, and I'm pretty sure I know what's causing it.

Here's the test case

I expect sub-modules to store their_own values (attributes) using .set(). But this is not the case.

I think what's going on is that when module.create() is called, the instance._guid (line: 243) is defined... it's inherited, so the sub-module doesn't get its own guid.

I'm trying to use Stapes in a few projects... I'd appreciate an official fix for this soon.


hay commented Jul 20, 2012

thanks for reporting this bug. I've noticed this a few days ago as well and it's already been fixed in this commit, so as a temporary fix you can get the latest version from master. I'll release a bugfix release soon.

Thanks for using Stapes!

-- Hay

@hay hay closed this Jul 20, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment