Re: [Zope-dev] Standard namechooser
On Feb 11, 2008, at 10:15 AM, Aaron Lehmann wrote: Possibly instead of returning an error, it might resolve the name, and take an optional callback that performs said resolution? That way, people who have their own resolution code can easily factor it in. Or is this a case where another NameChooser should be registered? I'm going to shut up now, because I think my schitzophrenia is showing. Aaron Lehmann ___ 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] Standard namechooser
On Feb 11, 2008, at 10:06 AM, Christian Theune wrote: Hi, Aaron Lehmann schrieb: Christian, What if people are relying on those error messages to do different things? Possibly they already have normalization code they expect to come into play in this situation, which is different than yours . I see that people might be doing that, however, it seems like a bad idea to code that way. ;) Maybe. But enforcing this on others seems to cut against consenting adults. After all, how do you know that your desired resolution is the resolution for everyone? On the other hand, having to do this seems annoying, so as someone writing new code I'd consider your proposed patch a feature, rather than a bugfix. I'd be happy to declare it a feature, but I consider the existing state to not be ideal and thus it should be changed. Possibly instead of returning an error, it might resolve the name, and take an optional callback that performs said resolution? That way, people who have their own resolution code can easily factor it in. Aaron Lehmann ___ 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] Standard namechooser
Hi, Aaron Lehmann schrieb: Christian, What if people are relying on those error messages to do different things? Possibly they already have normalization code they expect to come into play in this situation, which is different than yours . I see that people might be doing that, however, it seems like a bad idea to code that way. ;) On the other hand, having to do this seems annoying, so as someone writing new code I'd consider your proposed patch a feature, rather than a bugfix. I'd be happy to declare it a feature, but I consider the existing state to not be ideal and thus it should be changed. Christian -- gocept gmbh co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ 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] Standard namechooser
Christian, What if people are relying on those error messages to do different things? Possibly they already have normalization code they expect to come into play in this situation, which is different than yours . On the other hand, having to do this seems annoying, so as someone writing new code I'd consider your proposed patch a feature, rather than a bugfix. My two cents, Aaron Lehmann On Feb 11, 2008, at 9:55 AM, Christian Theune wrote: Hi, the standard name chooser makes sure that the character '+', '@' are not used in the beginning of a name and '/' is never used. When asking the name chooser to choose a name for me, I thought it would normalize those characters away, giving me a usable name. Reading the interface, there is a distiction between checking a name (and giving an error) and choosing a name (create one, maybe with a given name to start from) that is valid. I'd consider this to be a bug and change the name chooser accordingly. What do people think? Christian -- gocept gmbh co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ 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 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] Standard namechooser
Hi, Aaron Lehmann schrieb: On Feb 11, 2008, at 10:15 AM, Aaron Lehmann wrote: Possibly instead of returning an error, it might resolve the name, and take an optional callback that performs said resolution? That way, people who have their own resolution code can easily factor it in. Or is this a case where another NameChooser should be registered? Well, my point is that I think it's not the case, because we're really not doing anything specific. We're happy with this simple name chooser. I really think that simple default components are quite ok, but they should behave correctly. I'm still trying to find out what 'correct' is though. Christian -- gocept gmbh co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ 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] zc.extrinsicreference release
Hi. Wondering if zc.extrinsicreference ought to be included in the versions.cfg. Currently it is at 0.1dev. It has been this way in the repository for about a year. Could/should it be released? Many thanks. Regards, David ___ 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] Standard namechooser
Hi, the standard name chooser makes sure that the character '+', '@' are not used in the beginning of a name and '/' is never used. When asking the name chooser to choose a name for me, I thought it would normalize those characters away, giving me a usable name. Reading the interface, there is a distiction between checking a name (and giving an error) and choosing a name (create one, maybe with a given name to start from) that is valid. I'd consider this to be a bug and change the name chooser accordingly. What do people think? Christian -- gocept gmbh co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ 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] zeo and queuecatalog conflict-resolution
You might be interested in: https://bugs.launchpad.net/zope2/+bug/143770 Joachim Schmitz wrote: Andreas Jung schrieb: --On 10. Februar 2008 18:34:54 +0100 Joachim Schmitz [EMAIL PROTECTED] wrote: What is the recommended method to make the conflict-resolution-code available to the zeo-server ? Is there a Products directive for zeo.conf ? I think it is sufficient that the Products directory is in the PYTHONPATH or available through sys.path. would something like: INSTANCE_PRODUCTS=/home/Zope/instances/waeup/Products ZODB3_HOME=/home/Zope/install/z296/lib/python PYTHONPATH=$ZODB3_HOME:$INSTANCE_PRODUCTS export PYTHONPATH INSTANCE_HOME in zeoctl do, and how can I check that it is realy effective ? ___ 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
Summary of messages to the zope-tests list. Period Sun Feb 10 12:00:00 2008 UTC to Mon Feb 11 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Feb 10 21:02:03 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009089.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Feb 10 21:03:33 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009090.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Feb 10 21:05:04 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009091.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Feb 10 21:06:34 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009092.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Feb 10 21:08:04 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009093.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Feb 10 21:09:35 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009094.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 )
Re: [Zope-dev] Standard namechooser
Aaron Lehmann schrieb: On Feb 11, 2008, at 10:06 AM, Christian Theune wrote: Hi, Aaron Lehmann schrieb: Christian, What if people are relying on those error messages to do different things? Possibly they already have normalization code they expect to come into play in this situation, which is different than yours . I see that people might be doing that, however, it seems like a bad idea to code that way. ;) Maybe. But enforcing this on others seems to cut against consenting adults. After all, how do you know that your desired resolution is the resolution for everyone? Sure, that's why I'm discussing it here. ;) On the other hand, having to do this seems annoying, so as someone writing new code I'd consider your proposed patch a feature, rather than a bugfix. I'd be happy to declare it a feature, but I consider the existing state to not be ideal and thus it should be changed. Possibly instead of returning an error, it might resolve the name, and take an optional callback that performs said resolution? That way, people who have their own resolution code can easily factor it in. Hmm. Sounds like a little too much engineering and not very componentish to me. Up to this point my thinking went this way: We have an interface that allows us to a) check whether a name is ok b) create a name that is ok for us, probably considering a name that we give him. The second method feels like it should never raise an error - that's what the `check` method is for. If you want to customize the behaviour, you can always create a different name chooser implementation. It doesn't have to be 100% correct for everyone, but it should avoid the 80% pitfalls and it certainly should implement the interface the way it is intended. Unfortunately the interface is a bit unspecific whether chooseName may raise an error if the given name does not conform to checkName or whether it is obligued to always pick a good one. Christian -- gocept gmbh co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ 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 )
