Tim Peters wrote:
[Andrew Veitch]
http://collector.zope.org/Zope/1128
Not being able to use the calendar module on Zope 2.7 breaks our
MailManager and more importantly the CMF!
I think the ClearWind Windows Installer works just fine, its built in a
totally different manner from Zope Corps., Plon
> Better would be to install Python 2.3.3 and use that to run zope. This
> also gives the advantage of allowing easier installation of third party
> extensions to Python.
That does make sense. I guess it is time to rtfm to learn how :)
___
Zope-Dev mai
[Andrew Veitch]
>> http://collector.zope.org/Zope/1128
>>
>> Not being able to use the calendar module on Zope 2.7 breaks our
>> MailManager and more importantly the CMF!
...
> Looking at this a bit more I'm guessing that Python's new datetime
> module was removed to avoid conflict with Zope's Da
Better would be to install Python 2.3.3 and use that to run zope. This
also gives the advantage of allowing easier installation of third party
extensions to Python.
Michael Long wrote:
Has there been any progress on this? Or is there a sensible work-around I
can give to our users - other than
> Has there been any progress on this? Or is there a sensible work-around I
> can give to our users - other than to switch to Linux!
The workaround is to install python 2.3.2 onto a windows machine and copy the
datetime.pyd from the python installion to the appropriate location in your zope
instal
> http://collector.zope.org/Zope/1128
>
> Not being able to use the calendar module on Zope 2.7 breaks our MailManager
> and more importantly the CMF!
Looking at this a bit more I'm guessing that Python's new datetime module
was removed to avoid conflict with Zope's DateTime on Window's case
inse