-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/18/2011 06:09 PM, Wichert Akkerman wrote: > On 2011-5-18 20:10, Chris McDonough wrote: >> I'm not sure what it means for actions to leak. The actions are kept on >> an attribute of the configurator, so if the configurator dies, the >> actions die too. I don't understand how they'd survive the death of the >> original configurator. > > It has me baffled as well. However all signs point to that direction as > far as I could see: > > * adding a config.commit() in the tests that create a Configuration > instance made the problem go away, and the only thing commit() does > as far as I can see is process all actions. > > * at the point where the test fails the RendererHelper instance for > the view had a different self.registry instance than > system['request'].registry, and self.registry did not have any > registrations that are handled via actions, specifically it had > no IRendererGlobalsFactory entry. > > Do you have any ideas what it might be if this is something other than > leaking actions?
Hmm, smells like maybe an unintended mutable default arg? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3UWPsACgkQ+gerLs4ltQ4TlwCgsdf8G4y0jjzRRXE9pbeRuCug fboAoLKOpnLSwAdWRO/BsUv65v8B02y0 =O4Am -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
