Re: [Zope-dev] mxDateTime-based Zope DateTime module
At 11:21 AM 6/7/01 -0400, Chris McDonough wrote: >I think using mxDateTime would be a great idea (it would mean DC would >no longer need to maintain our own DateTime module). And since you've >done a lot of good work in creating a wrapper, we've got a head start. >But I think before it can go in to any release, we need to follow the >fishbowl process. This means creating a proposal on dev.zope.org, >letting Brian know about it, and then letting Brian choose if and when >he wants it to go in (it will subsequently be made into a project). Cool. I will do that. Let's see whether we can get the last Catalog bug out of there, so that we can have a good prototype. I am very excited about that. I think this improvement will also be of advantage to the database adapters and other products that use Dates and Times extensively. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] mxDateTime-based Zope DateTime module
I think using mxDateTime would be a great idea (it would mean DC would no longer need to maintain our own DateTime module). And since you've done a lot of good work in creating a wrapper, we've got a head start. But I think before it can go in to any release, we need to follow the fishbowl process. This means creating a proposal on dev.zope.org, letting Brian know about it, and then letting Brian choose if and when he wants it to go in (it will subsequently be made into a project). Thanks, - C Stephan Richter wrote: > > At 10:28 AM 6/7/01 -0400, Chris McDonough wrote: > >Actually, it's good that the license is BSDish, that means that it's > >legally possible to include mxDateTime inside a Zope distribution. > > Cool, so the license problem is definitely solved. > > Now, we just have to get rid of the last technical issues. From DC's point > of view: Is there a chance, that this port to mxDateTime could make it into > Zope 2.4? I think this would be the correct release in anyway, since there > will be so many changes. > > Regards, > Stephan > > -- > Stephan Richter > CBU - Physics and Chemistry Student > Web2k - Web Design/Development & Technical Project Management ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] mxDateTime-based Zope DateTime module
At 10:28 AM 6/7/01 -0400, Chris McDonough wrote: >Actually, it's good that the license is BSDish, that means that it's >legally possible to include mxDateTime inside a Zope distribution. Cool, so the license problem is definitely solved. Now, we just have to get rid of the last technical issues. From DC's point of view: Is there a chance, that this port to mxDateTime could make it into Zope 2.4? I think this would be the correct release in anyway, since there will be so many changes. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] mxDateTime-based Zope DateTime module
Actually, it's good that the license is BSDish, that means that it's legally possible to include mxDateTime inside a Zope distribution. Stephan Richter wrote: > > >What does being GPL compatible have to do with Zope ? > >Have I missed some licence changes/discussion ? > > Originally mxDateTime was not completely open. This was earlier on a > problem, if we wanted to use it for Zope. But now, we can do this. So I > just wanted to make the point that mxDateTime is now free as in beer and > freedom! ;-) > > Regards, > Stephan > > -- > Stephan Richter > CBU - Physics and Chemistry Student > Web2k - Web Design/Development & Technical Project Management > > ___ > Zope-Dev maillist - [EMAIL PROTECTED] > http://lists.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://lists.zope.org/mailman/listinfo/zope-announce > http://lists.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] mxDateTime-based Zope DateTime module
>What does being GPL compatible have to do with Zope ? >Have I missed some licence changes/discussion ? Originally mxDateTime was not completely open. This was earlier on a problem, if we wanted to use it for Zope. But now, we can do this. So I just wanted to make the point that mxDateTime is now free as in beer and freedom! ;-) Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] mxDateTime-based Zope DateTime module
>We at one point were fiddling with mx from eegenix, for psycopgDA. We found >out the hard way that the mx.h headers in the DateTime were being put in a >funny place. Perhaps that may give you a clue. I hope you are going to use mxDateTime for a new PostGreSQL DA. This would be for me the MAIN reason to choose it, since I really want DateTime objects returned, not strings. For the Zope DateTime module: Since we are working on the Python level I thought it would be no problem on the C level. Unfortunetely I do not know enough about the Python C API to check this. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] mxDateTime-based Zope DateTime module
Stephan Richter wrote: > > Hello everyone, > > after I got finally frustrated enough with the current implementation of > the Zope DateTime module, I decided to write a wrapper for mxDateTime. I > checked the license, and the eGenix Public License is GPL compatible, so > that we can use it for Zope now. What does being GPL compatible have to do with Zope ? Have I missed some licence changes/discussion ? - Hannu ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] mxDateTime-based Zope DateTime module
Hello everyone, after I got finally frustrated enough with the current implementation of the Zope DateTime module, I decided to write a wrapper for mxDateTime. I checked the license, and the eGenix Public License is GPL compatible, so that we can use it for Zope now. For more details, see http://www.lemburg.com/files/python/mxDateTime.html. You can find the first version of the new DateTime module here: http://www.zope.org/Members/srichter/Products/DateTimeNG Currently, it has a problem with ZCatalog. If you create a catalog and then restart Zope, you get a nasty setstate error: 2001-06-07T04:54:40 ERROR(200) ZODB Couldn't load state for '\000\000\000\000\000\000 \015' Traceback (innermost last): File /opt/devel/dev11480/lib/python/ZODB/Connection.py, line 533, in setstate SystemError: Failed to import class localtime from module __main__ (This is abbreviated debug output from the console.) Since I would like to see this new module in the Zope core ASAP (best in Zope 2.4), I wanted to ask you guys, whether you could have a look at this problem, since I do not know much about the Catalog and the entire ZODB pickle/unpickle process. Furthermore, I would love to hear your comments and ideas. With mxDateTime we can do much more now and have many more possibilities. The current version of the new DateTime module handles most of the old API functions correctly. Only some timezone issues are left open, but using the existing time zone mappers this should be no problem. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
