On Fri, 18 Apr 2008 16:19:38 -0700, Kay Schluehr wrote: > On 18 Apr., 23:09, Matimus <[EMAIL PROTECTED]> wrote: >> The reason it doesn't work is that you are unpacking the dictionary >> with **, and you have done nothing to define any keys or define a >> length. > > This is a non-issue. The class derives from dict; it has all the desired > attributes. It is also not a problem in particular because these > properties are not requested by format ( at least not in the code I have > examined which was admittedly just a critical section that caused the > exception ). > >> Adding to that... don't worry about py3k. Nobody is forcing you to >> switch. In fact, you are encouraged not to until you are comfortable. >> Py3k won't _break_ your code. You wrote the code for Python 2.x use it >> in 2.x. Python 2.x probably has a good 5-10 years remaining. > > These advices start to get annoying. > > Software hardly ever exists in isolation for the sake of the beauty of > the algorithm but is supplementary to a large framework/engine/ library. > So if e.g. Django switches to 3 everyone who works with it has to switch > sooner or later as well or lose track otherwise, no matter how long > Python 1.5.2 or Python 2.5.2 or whatever version will be maintained. If > Pythons code base becomes fragmented it will be harmful and affect > almost everyones work.
This Py3k-Django-related FUD starts to get annoying. AFAIK Django is going to support everything from 2.3 to 3.0 from single codebase. 2to3 tool will be called from setup.py and code will have few 'if sys.version_info < (3, 0)/else' tricks. Proof of concept already exists: http://wiki.python.org/moin/PortingDjangoTo3k I work with Django as well as *on* Django and 3rd party Django addons and don't see any reason to worry. Your particular problem may be solved by using a real dictionary with real keys which will probably have positive performance impact on your code and make it more clean. Even if Python code base will become fragmented why is it harmfull? This is a way our life work - you rise and get better or die. It is essential part of progress and evolution. IMHO, we'll only get better Python and better Python libraries. -- Ivan -- http://mail.python.org/mailman/listinfo/python-list
