Re: [Zope3-Users] Duplicate emails from mail queue
Darryl Cousins wrote: Initial tests seem to show that the problem is solved using the trunk. It seems to be working well for us too. I'll see if I can get 3.5.0b1 released some time today. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Duplicate emails from mail queue
Hey, On Nov 5, 2007 4:41 AM, Benji York [EMAIL PROTECTED] wrote: Darryl Cousins wrote: Has anyone experienced duplicate emails being sent using IQueuedMailDelivery? We've seen this when you have more than one process (or thread) attempting to deliver messages from a single maildir. I've recently made changes on the zope.sendmail trunk to eliminate the duplicates. I need to do another release, maybe tomorrow. If you want to try the fix before a release is made, you can try running a trunk checkout. Right, I can confirm seeing this for the same reason as well. Note that there are other issues with using this facility (at least the version I used) if you'd like to configure the mailhost after startup time in some UI, but maybe one can hack ones way around that. Regards, Martijn ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Eggs and classic instance homes, again... (was Re: Eggs, workingenv.py, and 'classic' instance homes)
On Wednesday 07 November 2007, Jeff Shell wrote: So now I see all that's going on with Zope 3 and I still don't understand a thing about how to move forward. We have about twelve active customers deployed on Zope 3, on top of one or two large frameworks that we've built on top if Z3. We still use the basic 'instance home' layout. We don't use eggs - we just check things out directly into the instance home. Even stuff from the Zope community, because it's easier to do that than to even get workingenv or any of these other things running. I'm still lost about what to do. Grok is of no use to us at the moment. Many of these apps have been up and running for longer than Grok's been alive. Is there any kind of migration documentation out there? Or have these new ways of doing things been in use for so long that most people have just rolled along with them? I just don't have the time. I scarcely have time to keep up with the lists (which is obvious since I haven't read a thing for nearly three months). Hi Jeff, last time I promised I would be more responsive to your mails, so here you go. :-) First of all, let me say that I have no system in production yet, which uses eggs. I think only Lovely Systems and Zope Corp. do; and maybe some smaller applications. So I would not worry about not being up-to-date. In fact, the last stable release is still 3.3.1, which tells the story of the big Zope 3 tree. That said, have you seen my Zope 3.4.0b2 announcement _[1]? It was the first public announcement making people aware that eggs are really happening. I purposefully did not say that Zope 3.4 will be the last tarball release, because (a) I think we cannot abandon people that quickly and (b) it is now really easy to create a new tarball release thanks to a couple of scripts I wrote. In the Zope 3.4.0b2 announcement I also sketched out two ways projects can be built using eggs, buildout and recipes. That said, writing a comprehensive migration document is still one of the tasks that need to be done. I was really hoping that the community would step up in writing one. I think that Darryl's response to your mail is a great start actually. It could easily be used as a starting point. .. [1] http://mail.zope.org/pipermail/zope3-users/2007-November/007106.html Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Eggs and classic instance homes, again... (was Re: Eggs, workingenv.py, and 'classic' instance homes)
Oops. Forgot to send this to the list as well as Stephan. Goddamn Gmail. On Nov 8, 2007 8:28 AM, Stephan Richter [EMAIL PROTECTED] wrote: Hi Jeff, last time I promised I would be more responsive to your mails, so here you go. :-) Thanks! First of all, let me say that I have no system in production yet, which uses eggs. I think only Lovely Systems and Zope Corp. do; and maybe some smaller applications. So I would not worry about not being up-to-date. In fact, the last stable release is still 3.3.1, which tells the story of the big Zope 3 tree. That said, have you seen my Zope 3.4.0b2 announcement _[1]? It was the first public announcement making people aware that eggs are really happening. I purposefully did not say that Zope 3.4 will be the last tarball release, because (a) I think we cannot abandon people that quickly and (b) it is now really easy to create a new tarball release thanks to a couple of scripts I wrote. This is where I start to get confused. I understand, and am glad for, the continuation of tarball releases for this round. My main question is: how does one mix and match? We have a lot of external software requirements and I'd rather get some of those as eggs than keep doing individual subversion checkouts. My big concern, which is something that affects all packaging systems, is how to tell packaged stuff that hand-build stuff meets the requirements. If I want to use an egg in a particular environment that has dependencies on: - zope.component 3.4.0 (or anything built into the zope 3.4 tarball) - sqlalchemy 0.4.0 - simplejson Would it know that zope.component was already offered via the whole Zope 3.4 tarball? It seems like you do things the classic way, or the egg/buildout way, and nothing in between. This makes things like z3c.form intimidating to me because I don't know if/how it will work in my vanilla zope environment (and with such a long time span between 3.3.1 and the eventual 3.4, I doubt it or its dependencies could work in 3.3.1). I may be wrong about all of that, but that's how I currently perceive things. Things just look so different between the two. -- Jeff Shell ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Eggs and classic instance homes, again... (was Re: Eggs, workingenv.py, and 'classic' instance homes)
Am Freitag, 9. November 2007 01:31 schrieb Jeff Shell: Oops. Forgot to send this to the list as well as Stephan. Goddamn Gmail. On Nov 8, 2007 8:28 AM, Stephan Richter [EMAIL PROTECTED] wrote: Hi Jeff, - zope.component 3.4.0 (or anything built into the zope 3.4 tarball) - sqlalchemy 0.4.0 - simplejson Btw., how do you integrate Zope3 with SQLAlchemy 0.4? As far as I know zalchemy is not SQLAlchemy-0.4 ready yet? Best Regards, Hermann -- [EMAIL PROTECTED] GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
