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! 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! A
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 insensitive file system. Checking out http://www.python.org/peps/pep-0235.html and followed up by some quick testing it looks like it works fine so datetime could be added back to the installer without causing any problems. I think work-around for us will be just to supply the missing file with advice on were to put it. Is this sensible or have I missed something? A
[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 DateTime on Window's case insensitive file system.
I believe it's just a symptom of a more pervasive problem: if you look at Control Panel in your 2.7b3 Windows installation, you'll see that it identifies the Zope version as 2.7b2. Something went wrong with the Windows installer build process, packaging an odd mix of new and old code. I'm sure this will be fixed in the next Zope 2.7 Windows beta.
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., Plone built from the same base works fine anyway. Its a beta installer, havent got much feedback, so be warned :) http://www.clearwind.ca/zope -- Andy McKay ClearWind Consulting http://www.clearwind.ca
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 installation. I don't have my windows box in front of me but IIRC it goes in the Zope-2.7.0-b3/bin folder. hth, Mike
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 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 installation. I don't have my windows box in front of me but IIRC it goes in the Zope-2.7.0-b3/bin folder.
hth, Mike
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
participants (5)
-
Andrew Veitch -
Andy McKay -
Michael Long -
Phil Harris -
Tim Peters