Message5050
I think that the machinery needed to workaround the problem and support
using Class.forName from Python code is not worth the effort.
I propose to explicitely discourage Class.forName('foo.bar.Baz'), since
you can get the desired effect either by doing "import foo.bar.Baz", if
the class name is known beforehand, or __import__(className), if it's not.
We could even hack PyReflectedFunction to check if it is going to call
Class.forName(String) and print a loud warning. |
|
Date |
User |
Action |
Args |
2009-08-17 15:19:36 | leosoto | set | messageid: <1250522376.48.0.42971714704.issue1127@psf.upfronthosting.co.za> |
2009-08-17 15:19:36 | leosoto | set | recipients:
+ leosoto, fwierzbicki, pjenvey, zyasoft, nriley |
2009-08-17 15:19:36 | leosoto | link | issue1127 messages |
2009-08-17 15:19:36 | leosoto | create | |
|