Re: [Zope-dev] undeprecating zLOG
Andreas Jung wrote: 0, for keeping zLOG for the time being... -1, for undeprecating it. Using Python's logging module should remain the only recommended solution. I don't want to see any new code using zLOG. Totally agreed... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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: 7 OK
Summary of messages to the zope-tests list. Period Thu Feb 1 12:00:00 2007 UTC to Fri Feb 2 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:09:11 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007167.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:10:41 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007168.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:12:11 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007169.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:13:41 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007170.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:15:11 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007171.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:16:41 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007172.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:18:11 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007173.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: undeprecating zLOG
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: Andreas Jung wrote: 0, for keeping zLOG for the time being... -1, for undeprecating it. Using Python's logging module should remain the only recommended solution. I don't want to see any new code using zLOG. +1 for undeprecating it -- the noise it generates is usesless, and the value which its (attempted) removal has sucked out of our development process is far greater than any hygeine it was intended to create. At this point, the module is a thin compatibility wrapper for the logger, and no more. If *we* introduced lots of bugs into Zope trying to rip out zLOG from the core, why should we induce that same hell on people maintaining third-party products? Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFwzvc+gerLs4ltQ4RAsUaAKCW0eC4+8Tde1kQhztWpzZZD65nsACfUG6D bfanqN4oZMd1EuiXGQVT8uE= =pJAc -END PGP SIGNATURE- ___ 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: undeprecating zLOG
Tres Seaver wrote: Chris Withers wrote: Andreas Jung wrote: 0, for keeping zLOG for the time being... -1, for undeprecating it. Using Python's logging module should remain the only recommended solution. I don't want to see any new code using zLOG. +1 for undeprecating it -- the noise it generates is usesless, and the value which its (attempted) removal has sucked out of our development process is far greater than any hygeine it was intended to create. At this point, the module is a thin compatibility wrapper for the logger, and no more. If *we* introduced lots of bugs into Zope trying to rip out zLOG from the core, why should we induce that same hell on people maintaining third-party products? That is a good point. I should note that the deprecation of zLOG happened a) without a proper proposal that *exactly* outlined how certain zLOG calls should be spelled. Such proposals serve as reference for everyone who has to update their code. b) without moving the whole Zope 2 codebase to the new API. That in turn ended up in a desaster because the different places zLOG was still used were fixed up one by one by different people who made mistakes (mostly because of point a)). I think those points account for some of the problems we've had; there have certainly been wilder refactorings that people could deal better with because they were better documented. Nevertheless, the proposed benefits (less code to maintain, etc.) don't seem to balance the effort we've needed even just for Zope core at this point. As said, I wouldn't mind if zLOG was added back and even undeprecated, just as much as I wouldn't mind keeping the current situation. -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5 ___ 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: undeprecating zLOG
--On 2. Februar 2007 15:09:53 +0100 Philipp von Weitershausen [EMAIL PROTECTED] wrote: Tres Seaver wrote: Chris Withers wrote: Andreas Jung wrote: 0, for keeping zLOG for the time being... -1, for undeprecating it. Using Python's logging module should remain the only recommended solution. I don't want to see any new code using zLOG. +1 for undeprecating it -- the noise it generates is usesless, and the value which its (attempted) removal has sucked out of our development process is far greater than any hygeine it was intended to create. At this point, the module is a thin compatibility wrapper for the logger, and no more. If *we* introduced lots of bugs into Zope trying to rip out zLOG from the core, why should we induce that same hell on people maintaining third-party products? That is a good point. I should note that the deprecation of zLOG happened a) without a proper proposal that *exactly* outlined how certain zLOG calls should be spelled. Such proposals serve as reference for everyone who has to update their code. b) without moving the whole Zope 2 codebase to the new API. That in turn ended up in a desaster because the different places zLOG was still used were fixed up one by one by different people who made mistakes (mostly because of point a)). I think those points account for some of the problems we've had; there have certainly been wilder refactorings that people could deal better with because they were better documented. Nevertheless, the proposed benefits (less code to maintain, etc.) don't seem to balance the effort we've needed even just for Zope core at this point. As said, I wouldn't mind if zLOG was added back and even undeprecated, just as much as I wouldn't mind keeping the current situation. If anyone is interested in putting zLOG back into the core, put it back. However I am still opposed removing the deprecation. It should remain deprecated without the threat to remove it in Zope 2.11. That's a clear message to avoid using zLOG for new code. The recommended solution for logging in Zope 2 country is and will be the 'logging' module of Python. Andreas -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5 ___ 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 ) -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting pgpxfe4pdUlg6.pgp Description: PGP signature ___ 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] Interest in AdvancedQuery and/or ManagableIndex?
Whit (mailto:[EMAIL PROTECTED]) reported that AdvancedQuery is going to ship with Plone3 and that packaging would be easier for them if AdvancedQuery were part of the Zope 2 distribution. According to Whit, Alexander Limi seems to be interested to have Managable Index in the Zope 2 distribution, as well. I have no problems to donate AdvancedQuery and/or Managable Index to the Zope Foundation *BUT* I will not modify the code to bring it in line with the different style requirements usually applied to Zope components: e.g. * my code uses 2 blank indentation rather than the usual 4 blank (to make it more readable and easier to maintain for me) * I much prefer unit tests over doctests; thus, AdvancedQuery and Managable Index come with extensive unit tests and no doctests * I use camel case also for parameters and local variables and not only for functions and global objects. Is there interest in AdvancedQuery and/or Managable Index to become part of the Zope 2 distribution under these conditions? -- Dieter ___ 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: Interest in AdvancedQuery and/or ManagableIndex?
Dieter Maurer wrote: I have no problems to donate AdvancedQuery and/or Managable Index to the Zope Foundation That's great, thank you! :) *BUT* I will not modify the code to bring it in line with the different style requirements usually applied to Zope components: e.g. * my code uses 2 blank indentation rather than the usual 4 blank (to make it more readable and easier to maintain for me) This is the only one that I find a bit difficult, because it means that if I were to fix a bug or make a change to the AQ/MI code, I would need to change my editor settings, and if I were making a simultaneous change to any other part of Zope, I'd have to have different settings in different buffers. I think it'd be silly if this was a show stopper, and I understand it'd be a pain to change every file, but how would you feel if someone else changed it for you and made it consistent with everything else? * I much prefer unit tests over doctests; thus, AdvancedQuery and Managable Index come with extensive unit tests and no doctests You're not alone, and I can't imagine that would be a problem for anyone. * I use camel case also for parameters and local variables and not only for functions and global objects. Are we ever consistent on one or the other? Zope 2 specifically has camelCase all over the place. Anyone, +1 for inclusion or at least moving to svn.zope.org. Martin ___ 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] undeprecating zLOG
Chris McDonough wrote at 2007-2-1 13:32 -0500: 0, for keeping zLOG for the time being... -1, for undeprecating it. Using Python's logging module should remain the only recommended solution. I don't want to see any new code using zLOG. There's a good deal of code using it that we just don't see because it's internal-only. When the API disappears, making people revisit that code is particularly pointless; it's makework. OTOH, if the API is not going to disappear, we should just undeprecate it. But anyway, all I can do is register my concern, you're gonna do whatever you do. ;-) I am on your side, Chris. But, I fear, we will not be heard... I fight pointless deprecation warnings with global deprecation warning deactivation -- probably not what deprecation advocates hope for. -- Dieter ___ 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: Interest in AdvancedQuery and/or ManagableIndex?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dieter Maurer wrote: Whit (mailto:[EMAIL PROTECTED]) reported that AdvancedQuery is going to ship with Plone3 and that packaging would be easier for them if AdvancedQuery were part of the Zope 2 distribution. According to Whit, Alexander Limi seems to be interested to have Managable Index in the Zope 2 distribution, as well. I have no problems to donate AdvancedQuery and/or Managable Index to the Zope Foundation *BUT* I will not modify the code to bring it in line with the different style requirements usually applied to Zope components: e.g. * my code uses 2 blank indentation rather than the usual 4 blank (to make it more readable and easier to maintain for me) * I much prefer unit tests over doctests; thus, AdvancedQuery and Managable Index come with extensive unit tests and no doctests * I use camel case also for parameters and local variables and not only for functions and global objects. Is there interest in AdvancedQuery and/or Managable Index to become part of the Zope 2 distribution under these conditions? +1 from me. Tres - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFw7Pe+gerLs4ltQ4RApLxAJ91UBf1aePQYdJpOhOuFxZfRIqepACgxEF6 +qEijONxSeDNE5EMZldSIkw= =8sl4 -END PGP SIGNATURE- ___ 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] How to recover passwords in Zope 2.6.4
hi all, i have my website in zope 2.6.4 and i have forgotton UserId(admin) and Password of root direcrorty of zope. please tell me Is there any way to recover admin password ? or is there any default UID password provided in zope. i guess passwords are stored in zpasswd.py file in zope installation folder. reply Rohit -- View this message in context: http://www.nabble.com/How-to-recover-passwords-in-Zope-2.6.4-tf3162398.html#a8772083 Sent from the Zope - Dev mailing list archive at Nabble.com. ___ 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] How to map Zope with IIS 5.1
hi all i have a website in zope 2.6.4 , and i want to link that website with IIS 5.1. in other words, i have created a virtual directory in IIS and i want to redirect the request to zope website. so i need to access my Zope website after passing through IIS 5.1 please tell me how to map zope with IIS, Very Urgent thanks rohit -- View this message in context: http://www.nabble.com/How-to-map-Zope-with-IIS-5.1-tf3162485.html#a8772316 Sent from the Zope - Dev mailing list archive at Nabble.com. ___ 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] Interest in AdvancedQuery and/or ManagableIndex?
--On 2. Februar 2007 22:36:37 +0100 Dieter Maurer [EMAIL PROTECTED] wrote: Whit (mailto:[EMAIL PROTECTED]) reported that AdvancedQuery is going to ship with Plone3 and that packaging would be easier for them if AdvancedQuery were part of the Zope 2 distribution. According to Whit, Alexander Limi seems to be interested to have Managable Index in the Zope 2 distribution, as well. I have no problems to donate AdvancedQuery and/or Managable Index to the Zope Foundation *BUT* I will not modify the code to bring it in line with the different style requirements usually applied to Zope components: e.g. +1 * my code uses 2 blank indentation rather than the usual 4 blank (to make it more readable and easier to maintain for me) The source would have to be reformatted to fit at least in some way with the Zope standard :-) Any volunteers? * I much prefer unit tests over doctests; thus, AdvancedQuery and Managable Index come with extensive unit tests and no doctests Unlikely a problem. Unit tests can not be replaced with doctests if you want to cover edge cases. * I use camel case also for parameters and local variables and not only for functions and global objects. No a problem (for me). Is there interest in AdvancedQuery and/or Managable Index to become part of the Zope 2 distribution under these conditions? No problem for importing the current state of your package on svn.zope.org. But we need a volunteer to integrate the packages for Zope 2.11. I think your code contains some ZCatalog monkeypatches...the related code has to be integrated properly. Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting pgpTRrtUIm0rQ.pgp Description: PGP signature ___ 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] undeprecating zLOG
--On 2. Februar 2007 22:53:50 +0100 Dieter Maurer [EMAIL PROTECTED] wrote: There's a good deal of code using it that we just don't see because it's internal-only. When the API disappears, making people revisit that code is particularly pointless; it's makework. OTOH, if the API is not going to disappear, we should just undeprecate it. But anyway, all I can do is register my concern, you're gonna do whatever you do. ;-) I am on your side, Chris. But, I fear, we will not be heard... I fight pointless deprecation warnings with global deprecation warning deactivation -- probably not what deprecation advocates hope for. With the argumentation that some old code might break with deprecated APIs you can fight almost against any kind of deprecation. We could possibly discuss and find some rules (specific for the Zope 2 needs) at Python if some of you guys show up in Dallas later this month. Andreas pgpNnGLrfvXWU.pgp Description: PGP signature ___ 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] How to recover passwords in Zope 2.6.4
--On 2. Februar 2007 10:01:58 -0800 Rohit Arora [EMAIL PROTECTED] wrote: hi all, i have my website in zope 2.6.4 and i have forgotton UserId(admin) and Password of root direcrorty of zope. please tell me Is there any way to recover admin password ? or is there any default UID password provided in zope. i guess passwords are stored in zpasswd.py file in zope installation folder. Wrong. Passwords are stored in the ZODB (/acl_users). You can of course create an emergency user to access the site again. However I can't remember how to do that in Zope 2.6. Somehow you need to create a 'inituser' file. You might look at an old version of the Zope Book 2.5/2.6 edition. -aj pgpSyaJ6ErTTG.pgp Description: PGP signature ___ 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 )
