[Zope-dev] Re: Removing 'inst'
[Philipp von Weitershausen] > ... > Therefore, just to reduce confusion, I would move Makefile.in and > configure.py to the root (and remove the decoys). I'd also suggest we > rename 'inst' to 'installer' so that it won't be confused with > "instance". Then again, this is just me and my weird sense of aesthetics ;). That all sounds good to me, assuming people still find a Makefile to be useful (I've been on Windows for a lng time now ;-)). ___ 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 )
Re: [Zope-dev] Re: Zope tests: 6 OK, 2 Failed
AFAIK the default configuration used by tests does not have a dbtab. See lib/python/App/config.py. Stefan On Jan 14, 2006, at 16:45, Florent Guillaume wrote: I'll look at it. Florent Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This failure is tie up with Florent's recent checkin: Log message for revision 41303: When a database is created "by hand" from a custom_zodb.py during startup, we still want to put it in the dbtab multidatabases dict. This happens when unit tests call Zope2.startup(), because Testing has a specific custom_zodb.py loaded at startup that uses a DemoStorage. Zope tests summarizer wrote: Summary of messages to the zope-tests list. Period Fri Jan 13 12:01:01 2006 UTC to Sat Jan 14 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures - Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:10:37 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004008.html Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:12:07 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004009.html -- The time has come to start talking about whether the emperor is as well dressed as we are supposed to think he is. /Pete McBreen/ ___ 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 )
Re: [Zope-dev] Re: Seeking brave souls to try Zope 2.9 Windows installer
On 1/15/06, Tim Peters <[EMAIL PROTECTED]> wrote: > Sorry, I'm not following this. The installer never offers to create a > user (although it does ask you to supply a password for the fixed > "admin" user). So you must be talking about something else, but I > don't know what. For example, when logged in to the installed Zope as > "admin", I had no problems creating new users from the acl_users > thingie. Is this "admin" user the emergency user? Because I couldn't log in, and I tried to create a new manager with inituser, and it worked, and there is no admin user in my acl_users... Still can't log in with admin, maybe I mistyped the password twice... :-) > > And of course zopectl doesn't work, so zopectl adduser > > is out of the question. Luckily creating an inituser still works! :-) > > > > Also, installing the shell files runzope and zopectl is kinda > > pointless. > > I'm sure the Zope 2.8 (etc) Windows installers did the same here. Me too. And in fact the linux install installs runzope.bat. Still pretty pointless. > r TAB > > in an instance's bin directory completes to > > runzope > > and that's what you want. That doesn't actually run the file named > "runzope", it actually runs the file named "runzope.bat" on Windows. Oh, right. No, I *want* runzope.bat, but yeah, just runzope works fine too, because the shell will look for exe, bat and com files when you do that. :-) If you delete the runzope file, and then do the same, you see it expands to "runzope.bat". > I'm sure all earlier Zope Windows installers created stuff that did > the same here too. If that isn't wanted, then Zope's > utilities/mkzopeinstance.py is again the thing that would need to be > changed. It should probably print the current directory. That's pointless on UNIX, because then you know what the current directory is, but when clicking on an icon, you don't. > Thank you for trying it! I'm just relieved it didn't melt your hard drive ;-) No, it works fine (except for the weirdness about the admin creation. Maybe I'll try again and make sure I donn't mistype this time.) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ 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 )
Re: [Zope-dev] [Zope 2.10] ZPT going Unicode
Dieter Maurer schrieb: > Tino Wildenhain wrote at 2006-1-13 16:45 +0100: > >>... >>Maybe just have new uZPT with Unicode and leave the "old" ZPT allone? >>Maybe with limited ability to "add" old ZPT from ZMI or such. >> >>This would solve the backward-compatibility problems and would be a more >>smooth transition w/o the need of upgrade hacks and "strict" hacks >>(after all, we arent perl/php ;)) > > > I fear it is not that easy: > > Unless we set Python's "defaultencoding" to the site encoding > (and we have such a thing), Python cannot mix Unicode and non-Unicode. > > Thus, your "old" ZPT's would need to use only other old ZPT's and > "old" Python scripts and "old" methods (returning encoded texts) > while "strict" ZPT's would need to use only new (strict) ZPT's, scripts > and methods. Quite unfeasible... Dont think so. The uZPTs would be aware of the fact of "unfriendly" environment. So handling of encoded templates can be done when they are used in a uZPT they would be promoted to unicode w/o touching the default python encoding. (If not unicode ... get encoding from template or site-default -> decode) Mixing all that capabilty with a single "switchable" ZPT implementation strikes me a lot harder to get right, useable and performant. But after all its just an idea. We can discuss it ;) ++Tino ___ 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 )
[Zope-dev] Zope tests: 6 OK, 2 Failed
Summary of messages to the zope-tests list. Period Sat Jan 14 12:01:02 2006 UTC to Sun Jan 15 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures - Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:10:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004016.html Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:12:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004017.html Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:01:39 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004010.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:03:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004011.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:04:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004012.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:06:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004013.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:07:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004014.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:09:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004015.html ___ 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 )
[Zope-dev] Re: Putting pullparser and clientform where they belong (reverting 39890)
Brian Sutherland wrote: > Since we are close to the release, I felt compelled to ask before I did > this. Could I revert 39890 [1] for the 3.2 release? > > It seems that phillip finished zpkg's module support some time ago [2]. > > (I ask as this is causing me headaches doing the Debian packaging for > the latest zope3) > > [1] http://mail.zope.org/pipermail/zope3-checkins/2005-November/026485.html > [2] http://mail.zope.org/pipermail/zpkg/2005-November/77.html Sorry for replying to this so late, I only stumbled upon this recently. While I agree that the sys.modules/sys.path mangling was bad, this now raises the problem of correctly stitching in pullparser and ClientForm into Zope 2. Unfortunately, svn:externals doesn't work with files, so we'll have to make copies. They will have to be updated whenever pullparser and ClientForm have been updated and a newer Zope 3 is stitched in. Philipp ___ 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 )
