On Friday 15 March 2002 07:15 pm, Tripp Lilley wrote:
> I'm planning on converting wholesale to Python 2.2. While I'm doing
> so, I'm going to spend some head-time getting to know iterators,
> generators, the new attributes stuff, and so on.
>
> What are you feelings on making MK require 2.2? One of the things I
> don't like about it right now is the impedance mismatch between how
> MK objects behave and how pure Python objects behave. I -think-
> (though I haven't explored it fully) that some of 2.2's features
> could lessen, if not eliminate, this mismatch.
>
> Since MK's thoroughly advertised as being alpha right now anyway,
> and, to the best of my knowledge, you, me, and Geoff are the only
> people with actual serious production apps running on top of it, I
> think now would be the most appropriate time for me to take on such a
> project.
I've considered the same thing, but mostly regarding properties. I'm
not touching generators any time soon and iterators are pure frosting
that we can get around to whenever. I don't think iterators will
actually shorten your code. eg, you'll still have pretty much the same
for loops.
BUT Python 2.2 has more caveats about its new features than I can fit
in my head. It also has some bugs that have been mentioned on their
site, but I don't remember them off the top of my head. And Guido has
admitted that the syntaxes for things like invoking super and
specifying properties are less than ideal.
For the first time, I'm actually skipping a Python version. I prefer to
wait for the next one hoping that bugs, caveats and syntactic ugliness
get reduced.
I would make the same recommendation to you, but it's your call.
There's no reason we couldn't enhance MK to support 2.0 through 2.2 as
Python seems flexible enough for that sort of thing.
But frankly, 2.2 isn't exactly a pot of honey. Just a step in the right
direction.
BTW There are more MK users coming out of the woodwork on the mailing
list, and had I thought of it, I would have marked it beta for the last
release.
Also, I plan that a future version of Webware would use the
attributes/properties style rather than the current all-methods style.
Such a change would come with a script to update existing sites. We
have, of course, big juicy projects to develop and test such a script
with. :-)
self.store.model.klass('foo')
self.session['foo']
I CCed webware-devel as these seem like thoughts to be shared.
-Chuck
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
