On Wed, 2002-09-04 at 02:02, Edmund Lian wrote:
>
> On 09/04/2002 02:41:19 AM Ian Bicking wrote:
>
> >It *is* 2.2 compatible (AFAIK), I think you are proposing that it should
> >use 2.2 features. This would make it incompatible with pre-2.2 Python.
>
> Are you sure about this Ian? AFAIK, calls
On 09/04/2002 03:37:12 AM Ian Bicking wrote:
>I think you are still confusing 2.2-compatibility with taking advantage
>of 2.2 features. Webware is 2.2 compatible, but does not use any 2.2
>features. If it did it would *require* 2.2. I'm sure you are correct
>that Webware would require some ch
On 09/04/2002 08:51:00 AM I wrote:
>In fact, the situation is greyer. I do use Python 2.2 features in all the
>objects that I create and instantiate in Webware. I just can't use the
>features in any subclass of Servlet or any subclass that mixes in my
>objects (because of the assertion in line
Edmund Lian wrote:
> I just checked... it is indeed true that mixins to any
> Servlet subclass
> cannot be new style classes due to the assertion in line 187 of
> ServletFactory. If you comment out that assertion, Webware is
> happy to use
> new style class mixins.
Which assertion causes the pr
On 09/04/2002 09:30:55 AM Geoffrey Talvola wrote:
>Which assertion causes the problem?
>
>assert type(theClass) is ClassType
>or
>assert issubclass(theClass, Servlet)
>?
>I assume it's the first one, right?
>
>Is there a way to rewrite the assertion so that it still provides some
>protec
Hey folks,
I've just run up against a nasty little exception block in Application.py
which drops import errors on context initialization. I was trying to figure
out why some of my context's __init__.py code wasn't executing - eventually
I simply tried to import the context from command line Pyth
