snake-guice - Project Hosting on Google Code

Last 30 days Nov 20, 2009 issue 11 (Singletons should be scope of the injector) reported by mark.chadwick - What steps will reproduce the problem? 1. Create an injector to build my instances (somewhere there's a Singleton) 2. Teardown what I'm doing, create a new injector, create new instances What is the expected output? What do you see instead? Singleton instances are the same instances across injectors. I would expect all singletons created from the same injector to be equal, but singletons created from different injectors to be different instances. What version of the product are you using? On what operating system? 0.2.1dev rev d28d5e34beb6 on Ubuntu 8.10, Python 2.5.2 Please provide any additional information below. Though a running system should never be strung together by multiple injectors, this is a common pattern in tests. In the setup method, create an injector with a TestModule, pull out the instances you'd like to test, then test them. This is extraordinarily convenient when dealing with Singletons because they hold some state almost by definition. IMHO, one of the big wins of using DI is isolated tests without complicated tearDown procedures to reset the system's state. I'm not intimately familiar with the source, but I believe a reasonable way to fix this is to attach GuiceData instances to the Injector instead of the class. If this sounds reasonable to the author (and he/she agrees this is the expected behavior), I'd be more than happy to implement the patch. I have attached a failing test. What steps will reproduce the problem? 1. Create an injector to build my instances (somewhere there's a Singleton) 2. Teardown what I'm doing, create a new injector, create new instances What is the expected output? What do you see instead? Singleton instances are the same instances across injectors. I would expect all singletons created from the same injector to be equal, but singletons created from different injectors to be different instances. What version of the product are you using? On what operating system? 0.2.1dev rev d28d5e34beb6 on Ubuntu 8.10, Python 2.5.2 Please provide any additional information below. Though a running system should never be strung together by multiple injectors, this is a common pattern in tests. In the setup method, create an injector with a TestModule, pull out the instances you'd like to test, then test them. This is extraordinarily convenient when dealing with Singletons because they hold some state almost by definition. IMHO, one of the big wins of using DI is isolated tests without complicated tearDown procedures to reset the system's state. I'm not intimately familiar with the source, but I believe a reasonable way to fix this is to attach GuiceData instances to the Injector instead of the class. If this sounds reasonable to the author (and he/she agrees this is the expected behavior), I'd be more than happy to implement the patch. I have attached a failing test. Earlier this year Nov 06, 2009 9 new revisions pushed by dstanek....@gmail.com - b3ddd7d68d:removed property inject validation because property injection was removed 054f59fa58:fixed some spacing issues to make pylint a little happier 19c892b9bc:refactored tests to remove old/dated mocking libraries 788e2d8386:merging r48 and r49 f2c692a7b8:patched together a first attempt at a @provides decorator f3bbad16eb:merging -r47 and -r51 05a24d76a5:removing DecorationError because the builtin TypeError is good enough 10abce7b43:started to move tests to a more BDD style d28d5e34be:created a new key object which is better than using a tuple - i plan to extend this later b3ddd7d68d:removed property inject validation because property injection was removed 054f59fa58:fixed some spacing issues to make pylint a little happier 19c892b9bc:refactored tests to remove old/dated mocking libraries 788e2d8386:merging r48 and r49 f2c692a7b8:patched together a first attempt at a @provides decorator f3bbad16eb:merging -r47 and -r51 05a24d76a5:removing DecorationError because the builtin TypeError is good enough 10abce7b43:started to move tests to a more BDD style d28d5e34be:created a new key object which is better than using a tuple - i plan to extend this later Nov 04, 2009 9 new revisions pushed by dstanek....@gmail.com - eb6836d560:added more TODOs 4dfd8bafd9:Removing the dependency on DecoratorTools. This means no more property injection and no more magic Python 2.3 decorators. 19d56f7424:Removed DecoratorTools which means no more 2.3 support and no more property injection. bea0c996b8:Removing some code that became useless when property injection was dropped. 4110eef092:merging r39 and r40 b43091c770:merging r43 and r42 68a4ffbf6a:fixed the webob import cc0231d7a1:cleanup up some smelly code 7ed8ce6fca:merging r44 and r46 eb6836d560:added more TODOs 4dfd8bafd9:Removing the dependency on DecoratorTools. This means no more property injection and no more magic Python 2.3 decorators. 19d56f7424:Removed DecoratorTools which means no more 2.3 support and no more property injection. bea0c996b8:Removing some code that became useless when property injection was dropped. 4110eef092:merging r39 and r40 b43091c770:merging r43 and r42 68a4ffbf6a:fixed the webob import cc0231d7a1:cleanup up some smelly code 7ed8ce6fca:merging r44 and r46 Sep 07, 2009 issue 10 ([Patch] Remove final remnants of DecoratorTools) reported by pjen...@underboss.org - Missed a usage of it in interceptors Missed a usage of it in interceptors Jul 09, 2009 Revision d3e53a50f3 (Adding a really simple implementation for InjectingConfigura...) pushed by dstanek....@gmail.com - Adding a really simple implementation for InjectingConfiguration. Adding a really simple implementation for InjectingConfiguration. Jul 07, 2009 2 new revisions pushed by dstanek....@gmail.com - Revision 868936f4ec:Removing some debugging prints. Revision 422845bf07:Adding a new spec that shows injecting a class object. Revision 868936f4ec:Removing some debugging prints. Revision 422845bf07:Adding a new spec that shows injecting a class object. Jul 07, 2009 4 new revisions pushed by dstanek....@gmail.com - Revision 87cf30ce96:A little clean up. Revision c352b62889:Fixed the specs to remove property injection and use the new annotate decorator. Revision e4650bb246:Removed unused kwargs from the inject decorator. Currently annotatio and scope are not supported. Revision 24d799864e:Remove the type check when creating an object. Revision 87cf30ce96:A little clean up. Revision c352b62889:Fixed the specs to remove property injection and use the new annotate decorator. Revision e4650bb246:Removed unused kwargs from the inject decorator. Currently annotatio and scope are not supported. Revision 24d799864e:Remove the type check when creating an object. Jul 07, 2009 3 new revisions pushed by dstanek....@gmail.com - Revision 0d3738ca0e:Removing the dependency on DecoratorTools. This means no more property injection and no more magic Python 2.3 decorators. Revision 204c7a465a:Remove the lazy/eager singleton concept. Will probably be added back at a later point when the need is clearer. Revision afcf737e23:Adding a new decorator @annotate that allows annotations to be specified for individual method parameters. Revision 0d3738ca0e:Removing the dependency on DecoratorTools. This means no more property injection and no more magic Python 2.3 decorators. Revision 204c7a465a:Remove the lazy/eager singleton concept. Will probably be added back at a later point when the need is clearer. Revision afcf737e23:Adding a new decorator @annotate that allows annotations to be specified for individual method parameters. Jun 28, 2009 3 new revisions pushed by dstanek....@gmail.com - Revision 01f9a594c8:Modifying pavement.py to include all of the setuptools tasks. Revision 5600774500:Adding a new task to run unit tests and specs. Revision 42e32ad33e:Initial routes integration. This is still a bit rough. Revision 01f9a594c8:Modifying pavement.py to include all of the setuptools tasks. Revision 5600774500:Adding a new task to run unit tests and specs. Revision 42e32ad33e:Initial routes integration. This is still a bit rough. Jun 28, 2009 4 new revisions pushed by dstanek....@gmail.com - Revision 1b4e765f74:I like Guice's naming conventions better. Revision 6b9f2f10d9:Add a paver task for runninng mote specifications. Revision b7d8480e7c:Updating the TODO list. Revision 2b538bacd7:Why should the Injector and Binder objects know the details of the binding map? Revision 1b4e765f74:I like Guice's naming conventions better. Revision 6b9f2f10d9:Add a paver task for runninng mote specifications. Revision b7d8480e7c:Updating the TODO list. Revision 2b538bacd7:Why should the Injector and Binder objects know the details of the binding map? Jun 22, 2009 9 new revisions pushed by dstanek.com - Revision 0d74f07745:Renaming so that I'll not shadowing builtins. Revision 93fcd8622b:Adding an ordered dict implementation. Revision a8fdbd0c07:Modified GuiceData to use an ordered dict instead of lists. Revision d84a93a1c1:Added yet another todo. Revision b0c7ecd596:Renaming tests to make more sense. Revision 03d335c7c9:Renaming tests to make more sense. Revision 283fb4da7e:Spec updated. When overriding a parent's method only the child's should be executed. Revision 9d6d1fdc48:Setting up the directory for the extra modules. Revision 8569cfac64:Refactoring. Moving Injected into the main __init__. Revision 0d74f07745:Renaming so that I'll not shadowing builtins. Revision 93fcd8622b:Adding an ordered dict implementation. Revision a8fdbd0c07:Modified GuiceData to use an ordered dict instead of lists. Revision d84a93a1c1:Added yet another todo. Revision b0c7ecd596:Renaming tests to make more sense. Revision 03d335c7c9:Renaming tests to make more sense. Revision 283fb4da7e:Spec updated. When overriding a parent's method only the child's should be executed. Revision 9d6d1fdc48:Setting up the directory for the extra modules. Revision 8569cfac64:Refactoring. Moving Injected into the main __init__. Apr 30, 2009 issue 9 (Better massaging when using the inject decorator incorrectly) reported by dstanek.com - We are getting this traceback: {{{ File "/home/mgriffith/src/sandbox/src/applib/app/pw/controller/test.py", line 35, in TestController @inject(customer_facade=cf.CustomerFacade) File "build\bdist.win32\egg\peak\util\decorators.py", line 576, in tracer File "build/bdist.linux-i686/egg/snakeguice/decorators.py", line 66, in callback _validate_property_args(func, args, kwargs) File "build/bdist.linux-i686/egg/snakeguice/decorators.py", line 46, in _validate_property_args raise DecorationError('only 1 decorator argument allowed') DecorationError: only 1 decorator argument allowed }}} when using inject incorrectly. We were specifying property injection and including a keyword arg that was unexpected. Can we make this more obvious? We are getting this traceback: {{{ File "/home/mgriffith/src/sandbox/src/applib/app/pw/controller/test.py", line 35, in TestController @inject(customer_facade=cf.CustomerFacade) File "build\bdist.win32\egg\peak\util\decorators.py", line 576, in tracer File "build/bdist.linux-i686/egg/snakeguice/decorators.py", line 66, in callback _validate_property_args(func, args, kwargs) File "build/bdist.linux-i686/egg/snakeguice/decorators.py", line 46, in _validate_property_args raise DecorationError('only 1 decorator argument allowed') DecorationError: only 1 decorator argument allowed }}} when using inject incorrectly. We were specifying property injection and including a keyword arg that was unexpected. Can we make this more obvious? Apr 23, 2009 snake_guice-0.2.0dev-py2.6.egg (An experimental release of version 0.2.0 ) file uploaded by dsta...@dstanek.com Apr 22, 2009 snake-guice-0.2.0dev.tar.gz (An experimental release of version 0.2.0 ) file uploaded by dsta...@dstanek.com Apr 13, 2009 snake_guice-0.2.0dev-py2.5.egg (An experimental release) file uploaded by roninds Mar 31, 2009 InjectingConfiguration (HOWTO inject configuration data into objects) Wiki page added by dsta...@dstanek.com Mar 31, 2009 TableOfContents (One-sentence summary of this page.) Wiki page edited by dsta...@dstanek.com Mar 31, 2009 TableOfContents (One-sentence summary of this page.) Wiki page edited by dsta...@dstanek.com Mar 31, 2009 UserGuide (snake-guice User Guide) Wiki page added by dsta...@dstanek.com Mar 31, 2009 TableOfContents (One-sentence summary of this page.) Wiki page added by dsta...@dstanek.com Mar 29, 2009 r49 (Creating an experimental branch for 2.6 only features. ) committed by roninds - Creating an experimental branch for 2.6 only features. Creating an experimental branch for 2.6 only features. Mar 29, 2009 issue 2 (Please limit the about of magic vars added to my classes) Status changed by dsta...@dstanek.com - Status: Fixed Status: Fixed Mar 29, 2009 r48 (A fix for issue 2. Combine the guice* attributes into a sing...) committed by roninds - A fix for issue 2 . Combine the guice* attributes into a single private __guice__ one. A fix for issue 2 . Combine the guice* attributes into a single private __guice__ one. Mar 28, 2009 issue 8 (Injecting third-party code) reported by dsta...@dstanek.com - How can this be done? There are probably a number of ways. Is there code required to make this happen? Possible use cases: * Local interfaces bound to a 3rd party implementation * Injecting into 3rd party instances How can this be done? There are probably a number of ways. Is there code required to make this happen? Possible use cases: * Local interfaces bound to a 3rd party implementation * Injecting into 3rd party instances Mar 28, 2009 issue 7 (Graph Visualizer like the real Guice) reported by dsta...@dstanek.com - Graph visualizer ala http://code.google.com/p/google-guice/wiki/Grapher Graph visualizer ala http://code.google.com/p/google-guice/wiki/Grapher Mar 28, 2009 issue 6 (I want a way to specify a default implementation for an inte...) reported by dsta...@dstanek.com - Maybe something like an @implemented_by decorator. Maybe something like an @implemented_by decorator. Mar 28, 2009 issue 5 (Should class decoration support be added to @inject?) reported by dsta...@dstanek.com - Should it? How would it work? Should it? How would it work? Mar 28, 2009 issue 4 (I was to construct objects with settings from configuration ...) reported by dsta...@dstanek.com - I want a way to declare a provider that gets it's value out of a configuration file. I want a way to declare a provider that gets it's value out of a configuration file. Mar 28, 2009 issue 2 (Please limit the about of magic vars added to my classes) Status changed by dsta...@dstanek.com - Status: Started Status: Started Mar 28, 2009 issue 3 (Add a nice way to use routes) reported by dsta...@dstanek.com - It seems that adding a really simple module that allows me to add routes in a guicey way would be cool. It seems that adding a really simple module that allows me to add routes in a guicey way would be cool. Mar 28, 2009 issue 2 (Please limit the about of magic vars added to my classes) reported by dsta...@dstanek.com - Instead of adding three public attributes to my class I really wish that you can just add one 'special' one. Something like __guice__ that stores a new object containing the injection type mappings. Instead of adding three public attributes to my class I really wish that you can just add one 'special' one. Something like __guice__ that stores a new object containing the injection type mappings. Mar 28, 2009 r47 (Fixing the classifiers.) committed by roninds - Fixing the classifiers. Fixing the classifiers. Mar 20, 2009 r46 (clean up the provide decorator, no logic changes) committed by michaeldavidgriffith - clean up the provide decorator, no logic changes clean up the provide decorator, no logic changes Mar 19, 2009 UsingProviders (How to use injected providers with snake-guice) Wiki page edited by michaeldavidgriffith Mar 19, 2009 UsingProviders (How to use injected providers with snake-guice) Wiki page added by michaeldavidgriffith Mar 19, 2009 r43 (Enable the "provide" decorator, which helps methods that wan...) committed by michaeldavidgriffith - Enable the "provide" decorator, which helps methods that want an instance of a provided class Enable the "provide" decorator, which helps methods that want an instance of a provided class Mar 03, 2009 snake_guice-0.1.0-py2.6.egg (0.1.0 Python 2.6 Source Dist) file uploaded by dsta...@dstanek.com Mar 03, 2009 snake_guice-0.1.0-py2.3.egg (0.1.0 Python 2.3 Egg) file uploaded by dsta...@dstanek.com Mar 03, 2009 snake_guice-0.1.0-py2.5.egg (0.1.0 Python 2.5 Egg) file uploaded by dsta...@dstanek.com Mar 03, 2009 snake-guice-0.1.0.tar.gz (0.1.0 Source Dist) file uploaded by dsta...@dstanek.com Mar 03, 2009 snake-guice-0.1.1.tar.gz (0.1.1 Source Dist) file uploaded by dsta...@dstanek.com Mar 03, 2009 snake-guice-0.1.0.tar.gz (0.1.0 Source Dist) file uploaded by dsta...@dstanek.com Older Nov 29, 2008 r42 (Merging the child_injector branch.) committed by roninds - Merging the child_injector branch. Merging the child_injector branch. Nov 29, 2008 r41 (Small name refactoring.) committed by roninds - Small name refactoring. Small name refactoring. Nov 29, 2008 r40 (Moving the scope implementation to be a little closer to the...) committed by roninds - Moving the scope implementation to be a little closer to the real Guice. Moving the scope implementation to be a little closer to the real Guice. Nov 29, 2008 r39 (Enable figleaf coverage in pavement.) committed by roninds - Enable figleaf coverage in pavement. Enable figleaf coverage in pavement. Nov 29, 2008 r38 (Began to add support for figleaf coverage. No network access...) committed by roninds - Began to add support for figleaf coverage. No network access to get figleaf right now. Began to add support for figleaf coverage. No network access to get figleaf right now. Nov 29, 2008 r37 (Updating the TODOs.) committed by roninds - Updating the TODOs. Updating the TODOs. Nov 29, 2008 r36 (Removing an unused class.) committed by roninds - Removing an unused class. Removing an unused class. Nov 29, 2008 r35 (Renaming InstanceProvider to SimpleProvider. Fixing and addi...) committed by roninds - Renaming InstanceProvider to SimpleProvider. Fixing and adding a test for injecting a provider. Renaming InstanceProvider to SimpleProvider. Fixing and adding a test for injecting a provider.

issue 11 (Singletons should be scope of the injector) reported by mark.chadwick - What steps will reproduce the problem? 1. Create an injector to build my instances (somewhere there's a Singleton) 2. Teardown what I'm doing, create a new injector, create new instances What is the expected output? What do you see instead? Singleton instances are the same instances across injectors. I would expect all singletons created from the same injector to be equal, but singletons created from different injectors to be different instances. What version of the product are you using? On what operating system? 0.2.1dev rev d28d5e34beb6 on Ubuntu 8.10, Python 2.5.2 Please provide any additional information below. Though a running system should never be strung together by multiple injectors, this is a common pattern in tests. In the setup method, create an injector with a TestModule, pull out the instances you'd like to test, then test them. This is extraordinarily convenient when dealing with Singletons because they hold some state almost by definition. IMHO, one of the big wins of using DI is isolated tests without complicated tearDown procedures to reset the system's state. I'm not intimately familiar with the source, but I believe a reasonable way to fix this is to attach GuiceData instances to the Injector instead of the class. If this sounds reasonable to the author (and he/she agrees this is the expected behavior), I'd be more than happy to implement the patch. I have attached a failing test.

What steps will reproduce the problem? 1. Create an injector to build my instances (somewhere there's a Singleton) 2. Teardown what I'm doing, create a new injector, create new instances What is the expected output? What do you see instead? Singleton instances are the same instances across injectors. I would expect all singletons created from the same injector to be equal, but singletons created from different injectors to be different instances. What version of the product are you using? On what operating system? 0.2.1dev rev d28d5e34beb6 on Ubuntu 8.10, Python 2.5.2 Please provide any additional information below. Though a running system should never be strung together by multiple injectors, this is a common pattern in tests. In the setup method, create an injector with a TestModule, pull out the instances you'd like to test, then test them. This is extraordinarily convenient when dealing with Singletons because they hold some state almost by definition. IMHO, one of the big wins of using DI is isolated tests without complicated tearDown procedures to reset the system's state. I'm not intimately familiar with the source, but I believe a reasonable way to fix this is to attach GuiceData instances to the Injector instead of the class. If this sounds reasonable to the author (and he/she agrees this is the expected behavior), I'd be more than happy to implement the patch. I have attached a failing test.

Last 30 days

Earlier this year

Older