[Zope-Checkins] SVN: Zope/trunk/ remove empty svn:externals property
Log message for revision 104667: remove empty svn:externals property Changed: _U Zope/trunk/ -=- Property changes on: Zope/trunk ___ Deleted: svn:externals - ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/ Modifications to MailHost send method to fix bugs, specify charset encodings, and permit unicode.
Log message for revision 102757:
Modifications to MailHost send method to fix bugs, specify charset encodings,
and permit unicode.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/Products/MailHost/MailHost.py
U Zope/trunk/src/Products/MailHost/README.txt
U Zope/trunk/src/Products/MailHost/interfaces.py
U Zope/trunk/src/Products/MailHost/tests/testMailHost.py
-=-
Modified: Zope/trunk/doc/CHANGES.rst
===
--- Zope/trunk/doc/CHANGES.rst 2009-08-13 22:31:27 UTC (rev 102756)
+++ Zope/trunk/doc/CHANGES.rst 2009-08-14 03:55:27 UTC (rev 102757)
@@ -37,6 +37,11 @@
Features Added
++
+- The send method of MailHost now supports unicode messages and
+ email.Message.Message objects. It also now accepts charset and
+ msg_type parameters to help with character, header and body
+ encoding.
+
- Updated packages:
- zope.app.appsetup = 3.12.0
@@ -56,6 +61,12 @@
Bugs Fixed
++
+- Fixed issue with sending text containing ':' from MailHost.
+
+- MailHost will now ensure the headers it sets are 7bit.
+
+- MailHost no longer generates garbage when given unicode input.
+
- Made C extensions work for 64-bit Python 2.5.x / 2.6.x.
- Unfutzed test failures due to use of naive timezones with ``datetime``
Modified: Zope/trunk/src/Products/MailHost/MailHost.py
===
--- Zope/trunk/src/Products/MailHost/MailHost.py2009-08-13 22:31:27 UTC
(rev 102756)
+++ Zope/trunk/src/Products/MailHost/MailHost.py2009-08-14 03:55:27 UTC
(rev 102757)
@@ -14,10 +14,25 @@
$Id$
+import logging
+import re
from cStringIO import StringIO
-import logging
-import mimetools
-import rfc822
+from copy import deepcopy
+from email.Header import Header
+from email.Charset import Charset
+from email import message_from_string
+from email.Message import Message
+from email import Encoders
+try:
+import email.utils as emailutils
+except ImportError:
+import email.Utils as emailutils
+import email.Charset
+# We import from a private module here because the email module
+# doesn't provide a good public address list parser
+from email._parseaddr import AddressList as _AddressList
+import uu
+
from threading import Lock
import time
@@ -49,6 +64,12 @@
LOG = logging.getLogger('MailHost')
+# Encode utf-8 emails as Quoted Printable by default
+email.Charset.add_charset(utf-8, email.Charset.QP, email.Charset.QP, utf-8)
+formataddr = emailutils.formataddr
+parseaddr = emailutils.parseaddr
+CHARSET_RE = re.compile('charset=[\']?([\w-]+)[\']?', re.IGNORECASE)
+
class MailHostError(Exception):
pass
@@ -91,7 +112,6 @@
lock = Lock()
# timeout = 1.0 # unused?
-
manage_options = (
(
@@ -185,18 +205,19 @@
encode=None,
REQUEST=None,
immediate=False,
+ charset=None,
+ msg_type=None,
):
Render a mail template, then send it...
mtemplate = getattr(self, messageTemplate)
messageText = mtemplate(self, trueself.REQUEST)
-messageText, mto, mfrom = _mungeHeaders( messageText, mto, mfrom)
-messageText = _encode(messageText, encode)
-trueself._send(mfrom, mto, messageText, immediate)
+trueself.send(messageText, mto=mto, mfrom=mfrom,
+ encode=encode, immediate=immediate,
+ charset=charset, msg_type=msg_type)
-if not statusTemplate:
+if not statusTemplate:
return SEND OK
-
try:
stemplate = getattr(self, statusTemplate)
return stemplate(self, trueself.REQUEST)
@@ -211,10 +232,15 @@
subject=None,
encode=None,
immediate=False,
+ charset=None,
+ msg_type=None,
):
-
-messageText, mto, mfrom = _mungeHeaders(messageText,
-mto, mfrom, subject)
+messageText, mto, mfrom = _mungeHeaders(messageText, mto, mfrom,
+subject, charset, msg_type)
+# This encode step is mainly for BBB, encoding should be
+# automatic if charset is passed. The automated charset-based
+# encoding will be preferred if both encode and charset are
+# provided.
messageText = _encode(messageText, encode)
self._send(mfrom, mto, messageText, immediate)
@@ -327,68 +353,147 @@
class MailHost(Persistent, MailBase):
persistent version
+def uu_encoder(msg):
+For BBB only, don't send uuencoded emails
+orig = StringIO(msg.get_payload())
+encdata = StringIO()
+uu.encode(orig, encdata)
+msg.set_payload(encdata.getvalue())
+# All encodings supported by mimetools for BBB
+ENCODERS = {
+'base64':
[Zope-Checkins] SVN: Zope/branches/tyam-unicodeSplitterPatch/lib/python/Products/ZCTextIndex/Lexicon.py added a hook for CJK process
Log message for revision 104648: added a hook for CJK process Changed: U Zope/branches/tyam-unicodeSplitterPatch/lib/python/Products/ZCTextIndex/Lexicon.py -=- Modified: Zope/branches/tyam-unicodeSplitterPatch/lib/python/Products/ZCTextIndex/Lexicon.py === --- Zope/branches/tyam-unicodeSplitterPatch/lib/python/Products/ZCTextIndex/Lexicon.py 2009-09-30 10:00:33 UTC (rev 104647) +++ Zope/branches/tyam-unicodeSplitterPatch/lib/python/Products/ZCTextIndex/Lexicon.py 2009-09-30 10:20:17 UTC (rev 104648) @@ -80,7 +80,8 @@ def termToWordIds(self, text): last = _text2list(text) for element in self._pipeline: -last = element.process(last) +process = getattr(element, process_post_glob, element.process) +last = process(last) wids = [] for word in last: wids.append(self._wids.get(word, 0)) ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/src/ Ignore pyd's when they're built in place.
Log message for revision 104688: Ignore pyd's when they're built in place. Changed: _U Zope/branches/2.12/src/AccessControl/ _U Zope/branches/2.12/src/DocumentTemplate/ _U Zope/branches/2.12/src/Missing/ _U Zope/branches/2.12/src/MultiMapping/ _U Zope/branches/2.12/src/Products/ZCTextIndex/ _U Zope/branches/2.12/src/Record/ _U Zope/branches/2.12/src/ThreadLock/ _U Zope/branches/2.12/src/initgroups/ -=- Property changes on: Zope/branches/2.12/src/AccessControl ___ Modified: svn:ignore - *so *.pyc build + *so *.pyc build *.pyd Property changes on: Zope/branches/2.12/src/DocumentTemplate ___ Modified: svn:ignore - *so *.pyc build + *so *.pyc build *.pyd Property changes on: Zope/branches/2.12/src/Missing ___ Modified: svn:ignore - *so *.pyc build + *so *.pyc build *.pyd Property changes on: Zope/branches/2.12/src/MultiMapping ___ Modified: svn:ignore - *so *.pyc build + *so *.pyc build *.pyd Property changes on: Zope/branches/2.12/src/Products/ZCTextIndex ___ Modified: svn:ignore - *so *.pyc build + *so *.pyc build *.pyd Property changes on: Zope/branches/2.12/src/Record ___ Modified: svn:ignore - *so *.pyc build + *so *.pyc build *.pyd Property changes on: Zope/branches/2.12/src/ThreadLock ___ Modified: svn:ignore - *so *.pyc build + *so *.pyc build *.pyd Property changes on: Zope/branches/2.12/src/initgroups ___ Modified: svn:ignore - _initgroups.so + _initgroups.so *.pyd ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/doc/ It's not called Zope 3 anymore and this little stub really doesn't add a lot.
Log message for revision 104691: It's not called Zope 3 anymore and this little stub really doesn't add a lot. Changed: D Zope/branches/2.12/doc/ZOPE3.rst U Zope/branches/2.12/doc/index.rst -=- Deleted: Zope/branches/2.12/doc/ZOPE3.rst === --- Zope/branches/2.12/doc/ZOPE3.rst2009-10-01 18:24:33 UTC (rev 104690) +++ Zope/branches/2.12/doc/ZOPE3.rst2009-10-01 18:29:39 UTC (rev 104691) @@ -1,30 +0,0 @@ -Using Zope Components in Zope 2 Applications - - -Background --- - -Zope 3 is a separate project from the Zope community aimed at web -development. It is designed to be more 'programmer-centric' and easier -to learn, use and extend for programmers. Zope 3 introduces an -interface-centric component architecture that makes it easier to develop -and deploy components without requiring developers to learn and -understand the entire Zope framework. - -As of Zope 2.8, the Five project has been integrated into the -Zope 2 core. The Five project implements a compatibility layer -that allows many Zope 3 components and patterns to be used in -new and existing Zope 2 applications. - -Features - - -The Five integration layer provides support for Zope 3 interfaces, -Zope Configuration Markup Language (ZCML), adapters, views, -utilities and schema-driven content. - -Note that the Five layer does *not* attempt to provide a ZMI user -interface for Zope 3 components. - -Zope 2 includes the essential Zope 3 packages, so it is not -necessary to install Zope 3. Modified: Zope/branches/2.12/doc/index.rst === --- Zope/branches/2.12/doc/index.rst2009-10-01 18:24:33 UTC (rev 104690) +++ Zope/branches/2.12/doc/index.rst2009-10-01 18:29:39 UTC (rev 104691) @@ -11,7 +11,6 @@ CHANGES.rst INSTALL.rst SECURITY.rst - ZOPE3.rst SETUID.rst SIGNALS.rst DEBUGGING.rst ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/doc/ These credits are woefully out of date.
Log message for revision 104692: These credits are woefully out of date. Easier to axe this file than give such a short list compared with the huge number of people who've since contributed. Changed: D Zope/branches/2.12/doc/CREDITS.rst U Zope/branches/2.12/doc/index.rst -=- Deleted: Zope/branches/2.12/doc/CREDITS.rst === --- Zope/branches/2.12/doc/CREDITS.rst 2009-10-01 18:29:39 UTC (rev 104691) +++ Zope/branches/2.12/doc/CREDITS.rst 2009-10-01 18:32:45 UTC (rev 104692) @@ -1,64 +0,0 @@ -Credits -=== - -The Zope software receives contributions from far and wide. Here's -the Zope Hall of Fame: - -- Stephen Purcell allows us to distribute his PyUnit unit testing - framework with Zope. - -- Jeff Bauer is Zope Dude Number One. Jeff took over PCGI and - kept pushing it forward through the years. - -- Sam Rushing worked with us at Digital Creations to make Medusa - the publishing platform for ZServer and the concurrency of Zope2. - -- A subset of windows guru Mark Hammond's win32 extensions are - bundled with win32 binary distributions of Zope. - -- Martijn Pieters and Brian Hooper contributed the #in reverse - attribute. - -- Phillip Eby contributed the DTML 'let' tag and many - other useful ideas, including the inspiration for the DTML - 'call', 'with' and 'return' - tags. - -- The DateTime module was based on work from Ted Horst. - -- Jordan Baker contributed the 'try' tag, something we've wanted - for a long, long time. - -- Martijn Pieters chipped in with a safe range function. - -- Michael Hauser came up with the name Zope. - -- Eric Kidd from Userland contributed to ZPublisher's support for - XML-RPC. - -- Andrew M. Kuchling wrote the initial version of mod_pcgi, making - him extremely cool in our book. - -- Oleg Broytmann has taken up the standard of mod_pcgi and moving - it to be a really amazing thing, and ready for prime time. - -- Jephte CLAIN made some patches to European ZopeTime. - -- Thanks to Gregor Hoffleit for his work in getting Zope into the - Debian distribution. - -- All the other Zopistas far and wide that stuck with us during - the Bobo/Principia days and politely push us to make the best damn - app server on this or any other planet. - -- Of course the list of credits would be quite incomplete without - mentioning Guido van Rossum, benevolent dictator of Python and - long-time friend of Digital Creations. Zope Power is Python - Power. - -- Special thanks to Richard Stallman and the Free Software - Foundation for their assistance and feedback on the - GPL-compatible 2.0 version of the Zope Public License. - - - Modified: Zope/branches/2.12/doc/index.rst === --- Zope/branches/2.12/doc/index.rst2009-10-01 18:29:39 UTC (rev 104691) +++ Zope/branches/2.12/doc/index.rst2009-10-01 18:32:45 UTC (rev 104692) @@ -14,5 +14,4 @@ SETUID.rst SIGNALS.rst DEBUGGING.rst - CREDITS.rst ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/doc/ Split, tidy and update docs to do with special users and filesystem permissions.
Log message for revision 104694: Split, tidy and update docs to do with special users and filesystem permissions. Changed: U Zope/branches/2.12/doc/SECURITY.rst A Zope/branches/2.12/doc/USERS.rst U Zope/branches/2.12/doc/index.rst -=- Modified: Zope/branches/2.12/doc/SECURITY.rst === --- Zope/branches/2.12/doc/SECURITY.rst 2009-10-01 18:35:28 UTC (rev 104693) +++ Zope/branches/2.12/doc/SECURITY.rst 2009-10-01 18:47:11 UTC (rev 104694) @@ -1,87 +1,18 @@ -Setting the initial user name and password -== +Filesytem Permissions += -Because Zope is managed through the web, user names and passwords must be -used to assure that only authorized people can make changes to a Zope -installation. - -Some user name and password is needed to bootstrap the creation of -normal managers of your Zope site. This is accomplished through the -use of the file 'inituser'. The first time Zope starts, it will detect -that no users have been defined in the root user folder. It will search -for the 'inituser' file and, if it exists, will add the user defined -in the file to the root user folder. - -Normally, 'inituser' is created by the Zope install scripts. Either -the installer prompts for the password or a randomly generated -password is created and displayed at the end of the build script. - -You can use the 'zpasswd.py' script to create 'inituser' yourself. -Execute 'zpasswd.py' like this:: - -python zpasswd.py inituser - -The script will prompt you for the name, password, and allowed -domains. The default is to encode the password with SHA, so please -remember this password as there is no way to recover it (although -'zpasswd.py' lets you reset it.) - -In some situations you may need to bypass normal security controls -because you have lost your password or because the security settings -have been mixed up. Zope provides a facility called an emergency -user so that you can reset passwords and correct security -settings. - -The emergency user password must be defined outside the application -user interface. It is defined in the 'access' file located -in the Zope directory. It should be readable only by the user -as which your web server runs. - -To create the emergency user, use 'zpasswd.py' to create the -'access' file like this:: - -python zpasswd.py access - -In order to provide a somewhat higher level of security, various -encoding schemes are supported which provide access to either SHA-1 -encryption or the standard UNIX crypt facility if it has been compiled -into Python. Unless you have some special requirements (see below), -you should use the SHA-1 facility, which is the default. - -Format of 'inituser' and 'access' -- - -A password file should consist of a single line of the form:: - -name:password - -Note that you may also add an optional third component to the line in the -access file to restrict access by domain. For example, the line:: - -mario:nintendoRules:*.mydomain.com - -in your 'access' file will only allow permit emergency user access -from `*.mydomain.com` machines. Attempts to access the system from -other domains will fail, even if the correct emergency user name -and password are used. - -Please note that if you use the ZServer monitor capability, you will -need to run with a clear text password. - -Setting permissions on the var directory - - -You need to set permissions on the Zope var directory. -Zope needs to read and write data from its var directory. Before +You need to set permissions on the directory Zope uses to store its +data. This will normally be the `var` directory in the instance home. +Zope needs to read and write data to this directory. Before running Zope you should ensure that you give adequate permissions -to the Zope var directory for the userid Zope will run under. +to this directory for the userid Zope will run under. Depending on how you choose to run Zope you will need to give -different permissions to the var directory. If you use Zope with an +different permissions to the directory. If you use Zope with an existing web server, it will probably run Zope as 'nobody'. In this case 'nobody' needs read and write permissions to the var directory. -If you change the way you run Zope you may need to modify the permissions -of the var directory and the files in it to allow Zope to read and write +If you change the way you run Zope, you may need to modify the permissions +of the directory and the files in it to allow Zope to read and write under its changed userid. Copied: Zope/branches/2.12/doc/USERS.rst (from rev 104684, Zope/branches/2.12/doc/SECURITY.rst) === --- Zope/branches/2.12/doc/USERS.rst(rev 0) +++ Zope/branches/2.12/doc/USERS.rst
[Zope-Checkins] SVN: Zope/branches/2.12/ Use ZODB 3.9.1; note CW's doc fixups.
Log message for revision 104710: Use ZODB 3.9.1; note CW's doc fixups. Changed: U Zope/branches/2.12/doc/CHANGES.rst U Zope/branches/2.12/versions.cfg -=- Modified: Zope/branches/2.12/doc/CHANGES.rst === --- Zope/branches/2.12/doc/CHANGES.rst 2009-10-01 19:58:24 UTC (rev 104709) +++ Zope/branches/2.12/doc/CHANGES.rst 2009-10-01 20:09:00 UTC (rev 104710) @@ -5,6 +5,19 @@ Change information for previous versions of Zope can be found in the file HISTORY.txt. +Zope 2.12.1 (unreleased) + + +Bugs Fixed +++ + +- Updated packages: + + - ZODB3 = 3.9.1 (fixes bug where blob conflict errors hung commits) + +- Assorted documentation cleanups, including a script to rebuild HTML + documentation on Windows. + Zope 2.12.0 final (2009/10/01) --- Modified: Zope/branches/2.12/versions.cfg === --- Zope/branches/2.12/versions.cfg 2009-10-01 19:58:24 UTC (rev 104709) +++ Zope/branches/2.12/versions.cfg 2009-10-01 20:09:00 UTC (rev 104710) @@ -13,7 +13,7 @@ ClientForm = 0.2.10 RestrictedPython = 3.5.1 ZConfig = 2.7.1 -ZODB3 = 3.9.0 +ZODB3 = 3.9.1 docutils = 0.5 lxml = 2.2 mechanize = 0.1.11 ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.11/ updated to ZODB 3.8.4
Log message for revision 104721: updated to ZODB 3.8.4 Changed: U Zope/branches/2.11/doc/CHANGES.txt _U Zope/branches/2.11/lib/python/ -=- Modified: Zope/branches/2.11/doc/CHANGES.txt === --- Zope/branches/2.11/doc/CHANGES.txt 2009-10-02 01:31:17 UTC (rev 104720) +++ Zope/branches/2.11/doc/CHANGES.txt 2009-10-02 04:08:27 UTC (rev 104721) @@ -11,6 +11,8 @@ - LP #414757 (backported from Zope trunk): don't emit a IEndRequestEvent when clearing a cloned request. + - updated to ZODB 3.8.4 + Zope 2.11.4 (2009/08/06) Restructuring Property changes on: Zope/branches/2.11/lib/python ___ Modified: svn:externals - BTrees svn://svn.zope.org/repos/main/ZODB/tags/3.8.2/src/BTrees ClientForm svn://svn.zope.org/repos/main/ClientForm/as_package/0.2.10 RestrictedPython svn://svn.zope.org/repos/main/RestrictedPython/tags/3.5.1/src/RestrictedPython ThreadedAsync svn://svn.zope.org/repos/main/ZODB/tags/3.8.2/src/ThreadedAsync ZConfig svn://svn.zope.org/repos/main/ZConfig/tags/2.5.1/ZConfig ZEO svn://svn.zope.org/repos/main/ZODB/tags/3.8.2/src/ZEO ZODB svn://svn.zope.org/repos/main/ZODB/tags/3.8.2/src/ZODB ZopeUndo svn://svn.zope.org/repos/main/ZODB/tags/3.8.2/src/ZopeUndo docutils svn://svn.zope.org/repos/main/docutils/tags/0.4.0 mechanize svn://svn.zope.org/repos/main/mechanize/tags/0.1.10/mechanize persistent svn://svn.zope.org/repos/main/ZODB/tags/3.8.2/src/persistent pytz svn://svn.zope.org/repos/main/pytz/tags/2008i/pytz transaction svn://svn.zope.org/repos/main/ZODB/tags/3.8.2/src/transaction zdaemon svn://svn.zope.org/repos/main/zdaemon/tags/2.0.4/src/zdaemon zodbcode svn://svn.zope.org/repos/main/zodbcode/tags/3.4.0/src/zodbcode + BTrees svn://svn.zope.org/repos/main/ZODB/tags/3.8.4/src/BTrees ClientForm svn://svn.zope.org/repos/main/ClientForm/as_package/0.2.10 RestrictedPython svn://svn.zope.org/repos/main/RestrictedPython/tags/3.5.1/src/RestrictedPython ThreadedAsync svn://svn.zope.org/repos/main/ZODB/tags/3.8.4/src/ThreadedAsync ZConfig svn://svn.zope.org/repos/main/ZConfig/tags/2.5.1/ZConfig ZEO svn://svn.zope.org/repos/main/ZODB/tags/3.8.4/src/ZEO ZODB svn://svn.zope.org/repos/main/ZODB/tags/3.8.4/src/ZODB ZopeUndo svn://svn.zope.org/repos/main/ZODB/tags/3.8.4/src/ZopeUndo docutils svn://svn.zope.org/repos/main/docutils/tags/0.4.0 mechanize svn://svn.zope.org/repos/main/mechanize/tags/0.1.10/mechanize persistent svn://svn.zope.org/repos/main/ZODB/tags/3.8.4/src/persistent pytz svn://svn.zope.org/repos/main/pytz/tags/2008i/pytz transaction svn://svn.zope.org/repos/main/ZODB/tags/3.8.4/src/transaction zdaemon svn://svn.zope.org/repos/main/zdaemon/tags/2.0.4/src/zdaemon zodbcode svn://svn.zope.org/repos/main/zodbcode/tags/3.4.0/src/zodbcode ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/tyam-unicodeSplitterPatch/ Delete c1-based branch since since final is released.
Log message for revision 104722: Delete c1-based branch since since final is released. Changed: D Zope/branches/tyam-unicodeSplitterPatch/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/tyam-unicodeSplitterPatch/ Making a branch from 2.12.0 to make a hook for CJK processing.
Log message for revision 104723: Making a branch from 2.12.0 to make a hook for CJK processing. Changed: A Zope/branches/tyam-unicodeSplitterPatch/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/tyam-unicodeSplitterPatch/src/Products/ZCTextIndex/Lexicon.py added a hook for CJK processing.
Log message for revision 104724: added a hook for CJK processing. Changed: U Zope/branches/tyam-unicodeSplitterPatch/src/Products/ZCTextIndex/Lexicon.py -=- Modified: Zope/branches/tyam-unicodeSplitterPatch/src/Products/ZCTextIndex/Lexicon.py === --- Zope/branches/tyam-unicodeSplitterPatch/src/Products/ZCTextIndex/Lexicon.py 2009-10-02 04:15:49 UTC (rev 104723) +++ Zope/branches/tyam-unicodeSplitterPatch/src/Products/ZCTextIndex/Lexicon.py 2009-10-02 05:01:33 UTC (rev 104724) @@ -76,7 +76,8 @@ def termToWordIds(self, text): last = _text2list(text) for element in self._pipeline: -last = element.process(last) +process = getattr(element, process_post_glob, element.process) +last = process(last) wids = [] for word in last: wids.append(self._wids.get(word, 0)) ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
