Re: [Zope3-dev] Zope3 and ZEO

2005-09-08 Thread Tim Peters
[Uwe Oestermeier] I dedected another problem: bin/runzeo doesn't start ZEO. This script calls ZEO/runzeo.py which has a main function but no if __name__ == __main__ : main() at the end. There are two instances of runzeo, one in Zope3's bin/ directory (at least in a Zope3 checkout), and

Re: [Zope3-dev] Zope3 and ZEO

2005-09-07 Thread Uwe Oestermeier
Tim Peters wrote: Zope3 3.1's bin/mkzeoinstance seems to work now, I dedected another problem: bin/runzeo doesn't start ZEO. This script calls ZEO/runzeo.py which has a main function but no if __name__ == __main__ : main() at the end. Has this already been fixed in the mentioned internal

Re: [Zope3-dev] Zope3 and ZEO

2005-09-07 Thread Fred Drake
On 9/7/05, Uwe Oestermeier [EMAIL PROTECTED] wrote: I dedected another problem: bin/runzeo doesn't start ZEO. This script calls ZEO/runzeo.py which has a main function but no if __name__ == __main__ : main() at the end. Has this already been fixed in the mentioned internal branch?

Re: [Zope3-dev] Zope3 and ZEO

2005-09-06 Thread Fred Drake
On 9/6/05, Tim Peters [EMAIL PROTECTED] wrote: I made an internal release of ZODB 3.5.1b1 (with Fred's changes) and stitched it into Zope3/branches/Zope-3.1. Zope3 3.1's bin/mkzeoinstance seems to work now, but I never used this Zope3 script before, so it would be good if someone who has