- Zope-Dev - Zope lists

[Weakness] analysis of Zope startup problems
by Dieter Maurer 30 Apr '04

30 Apr '04

Zope 2.7 delays access to log files until Zope is properly set up. This means: log files cannot be used to analyse startup problems. The official advice to analyse startup problems is to start Zope in the foreground and interpret the console log messages. However, this does *NOT* work when Zope is not running in debug mode. "Zope.Startup.ZopeStarter.setupStartupHandler" expressly suppresses messages to "stderr" when Zope is not running in debug mode. Apparently, we do not have an easy way to analyse startup problems for Zope in production mode. In my view, this is really bad. Please provide a way to control how startup messages should be handled. The best place would be a file (at least for all installations that do not start Zope as root and later switch the effective user). I suggest to always use the standard log file unless told otherwise by an explicit configuration option. -- Dieter

3 3

RE: [Zope-Coders] RE: ATTENTION! cvs tosubversion transitiontomorrow
by Scott A. Pascoe 30 Apr '04

30 Apr '04

Tim, Thanks for the tips. I'm new to the "zope writers guild" :) I believe that I've correctly added my public ssh keys to zope, but when I follow your procedure outlined here, I get the following message: Using username "spascoe". No supported authentication methods left to try! Anyone have any thoughts? -- Thanks, Scott -----Original Message----- From: Tim Peters [mailto:tim@zope.com] Sent: Thursday, April 29, 2004 12:11 PM To: jim(a)zope.com Cc: zope3-dev(a)zope.org; zope-coders(a)zope.org; zodb-dev(a)zope.org; zope-dev(a)zope.org Subject: [Zope-Coders] RE: ATTENTION! cvs tosubversion transitiontomorrow One more on access from Windows. TortoiseSVN will probably be more popular on Windows than the cmdline version of svn -- it's a slick integration of intelligent svn context-menus and icon overlays into the Windows Explorer GUI, including a nice GUI diff/merge component. Turns out it has its own kinds of svn+ssh access problems, and some of the articles on the web about worming around them are plain crazy. I'll skip all that and just explain a clean way that works (which I stumbled into on my own): TortoiseSVN comes with its own implementation of ssh, which appears to be a renamed version of plink.exe from the popular PuTTY suite of Windows connection tools. It's not documented anywhere, but it turns out TortoiseSVN accepts a PuTTY session name for the hostname portion of an svn+ssh URL. That's the key. So download the PuTTY tools too (I expect most developers on Windows already have them). This is what I did: + Ran putty.exe, and created a new session in the GUI: - Under Session, used Host Name svn.zope.org, and selected the SSH protocol. - Under Connection, put tim_one in the "auto-login username" box. - Under Connection -> SSH -> Auth, entered the path to my private key file. - Back under Session, saved the session under name svnzope (this is arbitrary). - Closed putty. That's a one-time setup dance. PuTTY saves this config info in the Windows registry, where other programs can get at it via the session name you chose, and turns out that's enough for TortoiseSVN. Now when using any Tortoise action where a svn+ssh svn.zope.org URL is needed, just use "svnzope" (or whatever name you picked for your session) instead of "svn.zope.org". For example, svn+ssh://svnzope/repos/main/ZConfig/trunk instead of svn+ssh://svn.zope.org/repos/main/ZConfig/trunk If you have an SSH passphrase, you can also run PuTTY's pageant.exe to supply it for you for as long as you leave pageant running (pageant is like the Unixish ssh-agent). Bottom line: while none of it is documented or obvious, there are clean and effective ways to use ssh+svn on Windows, both via cmdline and via the TortoiseSVN GUI, and even if your Windows username differs from your zope.org username. All the *obvious* ways of using SSH with client-side svn on Windows didn't work for me -- although they all do work for me (and have worked, for years) using SSH with client-side cvs on Windows. Disclaimer: All my experiments were on WinXP Pro. It's possible that other flavors of Windows will act differently, although I don't expect that in the cases talked about here. _______________________________________________ Zope-Coders mailing list Zope-Coders(a)zope.org http://mail.zope.org/mailman/listinfo/zope-coders --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.670 / Virus Database: 432 - Release Date: 4/27/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.672 / Virus Database: 434 - Release Date: 4/28/2004

1 0

RE: ATTENTION! cvs tosubversion transitiontomorrow
by Tim Peters 29 Apr '04

29 Apr '04

One more on access from Windows. TortoiseSVN will probably be more popular on Windows than the cmdline version of svn -- it's a slick integration of intelligent svn context-menus and icon overlays into the Windows Explorer GUI, including a nice GUI diff/merge component. Turns out it has its own kinds of svn+ssh access problems, and some of the articles on the web about worming around them are plain crazy. I'll skip all that and just explain a clean way that works (which I stumbled into on my own): TortoiseSVN comes with its own implementation of ssh, which appears to be a renamed version of plink.exe from the popular PuTTY suite of Windows connection tools. It's not documented anywhere, but it turns out TortoiseSVN accepts a PuTTY session name for the hostname portion of an svn+ssh URL. That's the key. So download the PuTTY tools too (I expect most developers on Windows already have them). This is what I did: + Ran putty.exe, and created a new session in the GUI: - Under Session, used Host Name svn.zope.org, and selected the SSH protocol. - Under Connection, put tim_one in the "auto-login username" box. - Under Connection -> SSH -> Auth, entered the path to my private key file. - Back under Session, saved the session under name svnzope (this is arbitrary). - Closed putty. That's a one-time setup dance. PuTTY saves this config info in the Windows registry, where other programs can get at it via the session name you chose, and turns out that's enough for TortoiseSVN. Now when using any Tortoise action where a svn+ssh svn.zope.org URL is needed, just use "svnzope" (or whatever name you picked for your session) instead of "svn.zope.org". For example, svn+ssh://svnzope/repos/main/ZConfig/trunk instead of svn+ssh://svn.zope.org/repos/main/ZConfig/trunk If you have an SSH passphrase, you can also run PuTTY's pageant.exe to supply it for you for as long as you leave pageant running (pageant is like the Unixish ssh-agent). Bottom line: while none of it is documented or obvious, there are clean and effective ways to use ssh+svn on Windows, both via cmdline and via the TortoiseSVN GUI, and even if your Windows username differs from your zope.org username. All the *obvious* ways of using SSH with client-side svn on Windows didn't work for me -- although they all do work for me (and have worked, for years) using SSH with client-side cvs on Windows. Disclaimer: All my experiments were on WinXP Pro. It's possible that other flavors of Windows will act differently, although I don't expect that in the cases talked about here.

1 0

Bug day!
by Casey Duncan 29 Apr '04

29 Apr '04

Just a reminder that bug day is on today. Meet us over on the #zope-dev channel of irc.zope.org if you can! -Casey

1 0

is threading in zope useful ?
by sathya 29 Apr '04

29 Apr '04

greetings, I read somewhere that each zope thread acquires the global python interpreter lock before processing a request and until it releases it the other zope threads are essentially locked out. Does that mean zope threads are eventually serialized and there are no benefits to be gained from concurrent execution ? Any thoughts ? your ideas are much appreciated ty sathya

4 6

Zope 3 (or 2 1/2 ;) sprint at EuroPython?
by Jim Fulton 28 Apr '04

28 Apr '04

Martijn Faassen wrote: > Martijn Faassen wrote: > >> So far nobody has stepped up to organize a Zope 3 sprint before and/or >> after EuroPython this year. >> >> If you want to organize a sprint please send a mail to >> europython(a)python.org. > > > No such mail was sent as far as I can see. I just sent it. >> Organizing a sprint means getting in touch with the right people to >> organize a sprint accomodation, and communicating the sprint time and >> place to all developers. It's also a good idea to get in touch with >> Jim about potential sprint topics. I can do that. ;) >> If nobody steps up to organize a sprint, there will be no Zope 3 >> sprint at EPC 2004. > > > I guess we can conclude that there will be no Zope 3 sprint at > EuroPython. Too bad! I would like to lead a sprint *after* the conference. A possible topic is Zope 2 -> Zope 3 migration/compatability. Or working on Zope 2.8. :) If you are interested in participating in a sprint after the conference, please let me know ASAP, including which days you would be participating. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

1 0

RE: [Zope-dev] Re: Demonstration subversion repository created
by Scott A. Pascoe 28 Apr '04

28 Apr '04

I pounded on it a few minutes before responding.. I'm not having problems... -- Thanks, Scott -----Original Message----- From: Jim Fulton [mailto:jim@zope.com] Sent: Wednesday, April 28, 2004 2:02 PM To: Max M Cc: zope-dev(a)zope.org Subject: [Zope-dev] Re: Demonstration subversion repository created Max M wrote: > Jim Fulton wrote: > >> >> I've done a conversion of a snapshot of the CVS database from yesterday. >> This is just to allow people to play with subversion and see what the >> respoitory >> might look like when we do cut over. >> >> To browse the respository: >> >> http://svn.zope.org/ > > > > It seems to have some kind of dns problem? Hm, I can get to it from a machine outside of ZC or Zope.org. Is anyone else haveing troubles getting to it? Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org _______________________________________________ Zope-Dev maillist - Zope-Dev(a)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 ) --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.670 / Virus Database: 432 - Release Date: 4/27/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.670 / Virus Database: 432 - Release Date: 4/27/2004

1 0

is threading within zope useful ?
by sathya 27 Apr '04

27 Apr '04

greetings, I read somewhere that each zope thread acquires the global python interpreter lock before processing a request and until it releases it the other zope threads are essentially locked out. Does that mean zope threads are eventually serialized and there are no benefits to be gained from concurrent execution ? Any thoughts ? your ideas are much appreciated ty sathya

1 0

Policy for Collector-Issues 545 and 1217?
by Maik Jablonski 27 Apr '04

27 Apr '04

Hi, there are two collector-issues related to problems when Zope-Objects get ids like 'content_type' or 'URL1'. I think this problem exists for all names used in the REQUEST-object or general acquisitionable attributes of ObjectManagers. http://zope.org/Collectors/Zope/545 http://zope.org/Collectors/Zope/1217 I don't think that these issues cannot easily be solved in Zope2 without breaking the whole acquisition-magic. What to do? The problem exists, but a fix is hard to find... if at all. Accepting? Rejecting? Cheers, Maik

3 5

Subversion repository layout
by Jim Fulton 27 Apr '04

27 Apr '04

The standard subversion repository layout is by project: proj1 /trunk /branches /br1 /br2 ... /tags /tag1 /tag2 ... proj2 /trunk /branches /br1 /br2 ... /tags /tag1 /tag2 ... ... With this layout, when you want to checkout the main development branch (aka head) of ZODB, you do: svn co svn+ssh://svn.zope.org/repos/ZODB/trunk ZODB That is, you need to include "/trunk" at the end and provide "ZODB" as the name of the output directory so as not to get a directory named "trunk". If you forget the "/trunk", you'll get a checkout that includes copies of all of the various tags and branches, which could be huge. I suggest, instead to use the following layout: proj1 proj2 tags /proj1 /tag1 /tag2 ... /proj2 /tag1 /tag2 ... branches /proj1 /br1 /br2 ... /proj2 /br1 /br2 ... With this layout, when you want to checkout the main development branch (aka head) of ZODB, you do: svn co svn+ssh://svn.zope.org/repos/ZODB which seems cleaner and less error prone. The only disadvantage I see in this layout is that we couldn't have projects named "tags" or "branches", but I could live with that. Alternatively, we could have a top-level trunk directory: trunk /proj1 /proj2 tags /proj1 /tag1 /tag2 ... /proj2 /tag1 /tag2 ... branches /proj1 /br1 /br2 ... /proj2 /br1 /br2 ... But that would require inclusion of a "/trunk" dead chicken in checkouts: svn co svn+ssh://svn.zope.org/repos/trunk/ZODB which seems unnecessary to me. Thoughts? Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

5 10