I've further enhanced yesterday's patch with the following additions:
* "Short-circuit evaluation" of local roles in User.getRolesInContext().
This speeds up security evaluation for complex DTML by stopping the local
role search as soon as one of the desired roles is found. The change is
fully b
There's a problem with strftime() in DateTime.py.
Try this DTML method to see:
Time:
Time:
Time:
Bad Time:
Time:
Time:
Time:
Time:
Time:
Time:
Note that the time given in the line "Bad Time:" above is actually wrong
-- it reports itself
Steve Alexander wrote:
>
> This is particularly apparent in the current DateTime.py, because its
> strftime method just interprets the internal representation of the time
> as GMT, whatever.
>
> We can fix this easily:
>
> *** lib/python/DateTime/DateTime.py Sun Jul 23 20:03:05 2000
> --- l
Steve Alexander wrote:
>
> No, no, no!
>
> Ignore the patch, it is a placebo :-/
> I should read these things back more carefully...
>
> The bit about reimplementing time.strftime() in DateTime.py still holds
> though.
In brief, though -- and hopefuly clearer this time:
If you format DateTime
I've compiled up a mxODBC DA for use under windows so that multi-threaded
odbc drivers can be me used in a multi-threaded way.
This works good so far except for one aspect. NULL values are being returned
as "None" objects. This seems reasonable but it is not how ZODBC returns
results. It will re
