.. image:: https://secure.travis-ci.org/collective/collective.watcherlist.png?branch=master
:target: http://travis-ci.org/collective/collective.watcherlist
:alt: Travis CI badge
.. image:: https://coveralls.io/repos/collective/collective.watcherlist/badge.png?branch=master
:target: https://coveralls.io/r/collective/collective.watcherlist
:alt: Coveralls badge
Introduction
============
``collective.watcherlist`` is a package that enables you to keep a
list of people who want to receive emails when an item gets updated.
The main use case is something like `Products.Poi <https://pypi.python.org/pypi/Products.Poi>`_, which is an issue
tracker for Plone. That product lets you create an issue tracker. In
this tracker people can add issues. The tracker has managers.
Everytime a new issue is posted, the managers should receive an email.
When a manager responds to an issue, the original poster (and the
other managers) should get an email. Anyone interested in following
the issue, should be able to add themselves to the list of people who
get an email. The functionality for this was in Poi, but has now been
factored out into this ``collective.watcherlist`` package.
Who should use this package?
============================
This is not a package for end users. Out of the box it does nothing.
It is a package for integrators or developers. You need to write some
python and zcml in your own package (like Poi now does) to hook
``collective.watcherlist`` up in your code.
We gladly use the ZCA (Zope Component Architecture) to allow others to
register their own adapters and own email texts, so outside of Zope
the package does not make much sense. And we import some code from
Plone too, so you will need that. If you want to use it in bare Zope
or CMF, contact me: we can probably do some conditional imports
instead.
``collective.watcherlist`` might also be usable as a basis for a
newsletter product. If you feel `Singing and Dancing <https://pypi.python.org/pypi/collective.singing>`_ is overkill
for you, or too hard to adapt to your specific needs, you could try
writing some code around ``collective.watcherlist`` instead.
Basic integration steps
=======================
In its simplest form, the integration that is needed, is this:
- Register an adapter from your content type to
``collective.watcherlist.interfaces.IWatcherList``. In a lot of
cases using the default implementation as factory for this adapter
is fine: ``collective.watcherlist.watchers.WatcherList``
- Create an html form where people can add themselves to the watcher
list. This could also be `PloneFormGen <https://pypi.python.org/pypi/Products.PloneFormGen>`_ form with a custom script
adapter as action.
- Register a BrowserView for your content type, inheriting from
``collective.watcherlist.browser.BaseMail`` and override its
properties ``subject``, ``plain`` and/or ``html``.
- Create an event handler or some other code that gets the adapter for
your content type and uses that to send an email with the subject
and contents defined in the browser view you created.
Events integration
==================
This addons play well with zope's event and plone's contentrules.
It triggers a zope event on all basic actions done on the watcherlist:
* ToggleWatchingEvent
* RemovedFromWatchingEvent
* AddedToWatchingEvent
Those events are registred to be useable as content rule trigger so you can
create a rule based on it.
It also provides a content rule action so you can create an action that's
add or remove the current user to or from the watcherlist attached to the
context.
Credits
=======
People
------
* Maurits van Rees [maurits] <maurits@vanrees.org> author
* Gagaro <gagaro42@gmail.com>
* JeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>
Companies
---------
* Zest Software https://zestsoftware.nl/
* `Makina Corpus <http://www.makina-corpus.org>`_
collective.watcherlist
======================
Sample integration
------------------
Let's give an example of what you need to do in your own code to use
this package. We define a class that holds some info about a party::
>>> class Party(object):
... def __init__(self, reason):
... self.reason = reason
... self.invited = []
We tell the ZCA how to adapt a Party to a watcher list: how to turn it
into an object that holds a list of interested people and knows how to
send them an email. Normally you would define an interface
``IParty``, say that the ``Party`` class implements it and use zcml to
register an adapter for that, something like this::
<adapter
for=".interfaces.IParty"
factory="collective.watcherlist.watchers.WatcherList"
/>
Let's ignore the interface and use python (as that is a bit easier to
use in tests). We will use the default implementation of a
watcherlist as provided by the package::
>>> from zope.component import getGlobalSiteManager
>>> from collective.watcherlist.watchers import WatcherList
>>> sm = getGlobalSiteManager()
>>> sm.registerAdapter(WatcherList, (Party, ))
.. This documentation doubles as automated test, so we run into a test
.. detail here: the WatcherList adapter stores the watchers in an
.. annotation, so we need to tell the ZCA how to do that; for standard
.. Plone/Archetypes content types this is already done, so you usually do
.. not need to care about this. Oh, we can hide this, nice::
:hide:
>>> from zope.annotation.interfaces import IAnnotations
>>> from zope.annotation.attribute import AttributeAnnotations
>>> sm.registerAdapter(AttributeAnnotations, (Party, ), IAnnotations)
Now we create a Party and invite people::
>>> birthday = Party("Maurits' birthday")
>>> birthday.invited.append('Fred')
>>> birthday.invited.append('Mirella')
We see if we can get a watcherlist for it::
>>> from collective.watcherlist.interfaces import IWatcherList
>>> watcherlist = IWatcherList(birthday)
>>> watcherlist
<collective.watcherlist.watchers.WatcherList object at ...>
We can ask several things of this list::
>>> watcherlist.watchers
[]
>>> watcherlist.send_emails
True
>>> watcherlist.addresses
()
We can add watchers. These should be email addresses or (at least in
a Plone context) the ids of members in the site. In your package you
would either create a button or other small form that people can use
to add themselves to the list, or create some code that automatically
adds some people, as Poi does for the creator of a new issue. The
code is simple::
>>> watcherlist.watchers.append('maurits@example.org')
>>> watcherlist.watchers.append('reinout@example.org')
>>> watcherlist.watchers
['maurits@example.org', 'reinout@example.org']
>>> watcherlist.addresses
('maurits@example.org', 'reinout@example.org')
You can always switch off email sending. This has the effect that no
addresses are reported::
>>> watcherlist.send_emails = False
>>> watcherlist.watchers
['maurits@example.org', 'reinout@example.org']
>>> watcherlist.addresses
()
Undo that::
>>> watcherlist.send_emails = True
>>> watcherlist.watchers
['maurits@example.org', 'reinout@example.org']
>>> watcherlist.addresses
('maurits@example.org', 'reinout@example.org')
Now we send an email. We get the email text and subject simply from a
browser view that we define. In the test this means we need to give
the Party a request object::
>>> from zope.publisher.browser import TestRequest
>>> birthday.REQUEST = TestRequest()
We now send an invitation email, but this fails::
>>> watcherlist.send('invitation')
Traceback (most recent call last):
...
ComponentLookupError...
This means we need to create a browser view with that name. As the
basis we should take the base browser view defined in the
``collective.watcherlist`` package. It contains three properties that
you would normally override: subject, plain and html::
>>> from collective.watcherlist.browser import BaseMail
>>> class PartyMail(BaseMail):
... @property
... def subject(self):
... return self.context.reason
... @property
... def plain(self):
... return "Invited are %s" % self.context.invited
... @property
... def html(self):
... return "<p>%s</p>" % self.plain
You would normally register this with zcml, just like any other
browser view. But here we do that in python code::
>>> from zope.interface import Interface
>>> sm.registerAdapter(PartyMail, (Party, TestRequest), Interface, 'invitation')
And we send the invitation again, in both plain text and html. In
this test we have no proper mail host setup, so we simply print the
relevant info so we can see what would happen::
>>> watcherlist.send('invitation')
Subject = Maurits' birthday
Addresses = ('maurits@example.org', 'reinout@example.org')
Message =
From...
Content-Type: multipart/alternative;...
...
Content-Type: text/plain; charset="us-ascii"
...
Invited are ['Fred', 'Mirella']
...
Content-Type: text/html; charset="us-ascii"
...
<p>Invited are ['Fred', 'Mirella']</p>
...
Let's skip the html and see if that simplifies the mail::
>>> PartyMail.html = ''
>>> watcherlist.send('invitation')
Subject = Maurits' birthday
Addresses = ('maurits@example.org', 'reinout@example.org')
Message =
From...
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
<BLANKLINE>
Invited are ['Fred', 'Mirella']
If there is neither plain text nor html, we do not send anything::
>>> PartyMail.plain = ''
>>> watcherlist.send('invitation')
Let's add a bit of html again to see that only html goes fine too::
>>> PartyMail.html = '<p>You are invited.</p>'
>>> watcherlist.send('invitation')
Subject = Maurits' birthday
Addresses = ('maurits@example.org', 'reinout@example.org')
Message =
From...
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit
<BLANKLINE>
<p>You are invited.</p>
If we switch off email sending for this watcherlist... no emails are sent::
>>> watcherlist.send_emails = False
>>> watcherlist.send('invitation')
Reset that::
>>> watcherlist.send_emails = True
Look at `Products.Poi <https://pypi.python.org/pypi/Products.Poi>`_ for some more examples of what you can do.
Changelog
=========
3.1.0 (2018-04-26)
------------------
- Don't test with Plone 4.1, 4.2 or Python 2.6 anymore.
It should still work, but I don't want to spend time fixing the build on Travis.
[maurits]
3.0.1 (2018-04-26)
------------------
- Declare ``zope.formlib`` dependency. [maurits]
3.0 (2016-12-23)
----------------
- Pass ``immediate=False`` by default. This used to be ``True``. The
original idea was to send emails immediately, so that we could catch
any errors ourselves and continue with a warning. But since Plone
4.1 the emails are by default sent at the end of the transaction,
and exceptions are caught. For immediate mails they are not caught
there. So for our uses cases it makes most sense to not send emails
immediately, as then Plone does what we want already. You can still
pass ``immediate=True`` to ``mailer.simple_send_mail`` or now also
to ``watchers.send`` if you want the old behavior back.
This fixes `issue #8 <https://github.com/collective/collective.watcherlist/issues/8>`_.
[maurits]
- Check ``allow_recursive`` on the watcher list. The default value is
true, which gives the same behavior as before. When the value is
false, the ``addresses`` property only looks for watchers on the
current item, not on the parent. A sample usage would be in
Products.Poi to only allow recursive if an issue is not yet
assigned. (I am going to use this in custom code for a client).
[maurits]
- Strip the email address that we get from a member or the site.
I have a site where some email addresses are ``test@example.org\r\n``,
which gives an error when sending.
[maurits]
2.0 (2016-07-07)
----------------
- Removed backwards compatibility code for Plone 3.3 and 4.0. We
already were not testing on 3.3 anymore, and 4.0 is too hard to keep
working too. [maurits]
- Fixed Plone 5 email sending. Improved code quality. Fixed Travis tests. [maurits]
- When the internal watchers list is of type list (instead of tuple),
make sure its updated when toggling a watcher [skurfer]
1.2 (2013-12-03)
----------------
- Added events, triggers and action for content rules. [Gagaro]
1.1 (2012-11-06)
----------------
- Made compatible with Plone 4.3 (keeping compatibility with Plone 3).
[maurits]
- Moved to https://github.com/collective/collective.watcherlist
[maurits]
1.0 (2012-04-21)
----------------
- When showing the plain text in the browser as test, force text/plain
as content-type.
[maurits]
0.3 (2011-05-09)
----------------
- Catch MailHostErrors when sending email.
[maurits]
0.2 (2010-02-27)
----------------
- You can now add ``only_these_addresses`` as an argument to the send
method. This forces sending only to those addresses and ignoring
all others.
[maurits]
- Fixed possible UnicodeDecodeError when the plain text or html part
of the email was not unicode.
[maurits]
0.1 (2010-02-26)
----------------
- Initial release
Raw data
{
"_id": null,
"home_page": "https://github.com/collective/collective.watcherlist",
"name": "collective.watcherlist",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "Plone notifications watching",
"author": "Maurits van Rees",
"author_email": "maurits@vanrees.org",
"download_url": "https://files.pythonhosted.org/packages/fe/d7/eeb09281abd8635f8c0fccca00f9aa9dbf2ff2287948f3b799abd4f03640/collective.watcherlist-3.1.0.tar.gz",
"platform": "",
"description": ".. image:: https://secure.travis-ci.org/collective/collective.watcherlist.png?branch=master\n :target: http://travis-ci.org/collective/collective.watcherlist\n :alt: Travis CI badge\n\n.. image:: https://coveralls.io/repos/collective/collective.watcherlist/badge.png?branch=master\n :target: https://coveralls.io/r/collective/collective.watcherlist\n :alt: Coveralls badge\n\n\nIntroduction\n============\n\n``collective.watcherlist`` is a package that enables you to keep a\nlist of people who want to receive emails when an item gets updated.\nThe main use case is something like `Products.Poi <https://pypi.python.org/pypi/Products.Poi>`_, which is an issue\ntracker for Plone. That product lets you create an issue tracker. In\nthis tracker people can add issues. The tracker has managers.\nEverytime a new issue is posted, the managers should receive an email.\nWhen a manager responds to an issue, the original poster (and the\nother managers) should get an email. Anyone interested in following\nthe issue, should be able to add themselves to the list of people who\nget an email. The functionality for this was in Poi, but has now been\nfactored out into this ``collective.watcherlist`` package.\n\n\nWho should use this package?\n============================\n\nThis is not a package for end users. Out of the box it does nothing.\nIt is a package for integrators or developers. You need to write some\npython and zcml in your own package (like Poi now does) to hook\n``collective.watcherlist`` up in your code.\n\nWe gladly use the ZCA (Zope Component Architecture) to allow others to\nregister their own adapters and own email texts, so outside of Zope\nthe package does not make much sense. And we import some code from\nPlone too, so you will need that. If you want to use it in bare Zope\nor CMF, contact me: we can probably do some conditional imports\ninstead.\n\n``collective.watcherlist`` might also be usable as a basis for a\nnewsletter product. If you feel `Singing and Dancing <https://pypi.python.org/pypi/collective.singing>`_ is overkill\nfor you, or too hard to adapt to your specific needs, you could try\nwriting some code around ``collective.watcherlist`` instead.\n\n\nBasic integration steps\n=======================\n\nIn its simplest form, the integration that is needed, is this:\n\n- Register an adapter from your content type to\n ``collective.watcherlist.interfaces.IWatcherList``. In a lot of\n cases using the default implementation as factory for this adapter\n is fine: ``collective.watcherlist.watchers.WatcherList``\n\n- Create an html form where people can add themselves to the watcher\n list. This could also be `PloneFormGen <https://pypi.python.org/pypi/Products.PloneFormGen>`_ form with a custom script\n adapter as action.\n\n- Register a BrowserView for your content type, inheriting from\n ``collective.watcherlist.browser.BaseMail`` and override its\n properties ``subject``, ``plain`` and/or ``html``.\n\n- Create an event handler or some other code that gets the adapter for\n your content type and uses that to send an email with the subject\n and contents defined in the browser view you created.\n\nEvents integration\n==================\n\nThis addons play well with zope's event and plone's contentrules.\nIt triggers a zope event on all basic actions done on the watcherlist:\n\n* ToggleWatchingEvent\n* RemovedFromWatchingEvent\n* AddedToWatchingEvent\n\nThose events are registred to be useable as content rule trigger so you can\ncreate a rule based on it.\n\nIt also provides a content rule action so you can create an action that's\nadd or remove the current user to or from the watcherlist attached to the\ncontext.\n\nCredits\n=======\n\nPeople\n------\n\n* Maurits van Rees [maurits] <maurits@vanrees.org> author\n* Gagaro <gagaro42@gmail.com>\n* JeanMichel FRANCOIS aka toutpt <toutpt@gmail.com>\n\nCompanies\n---------\n\n* Zest Software https://zestsoftware.nl/\n* `Makina Corpus <http://www.makina-corpus.org>`_\n\ncollective.watcherlist\n======================\n\nSample integration\n------------------\n\nLet's give an example of what you need to do in your own code to use\nthis package. We define a class that holds some info about a party::\n\n >>> class Party(object):\n ... def __init__(self, reason):\n ... self.reason = reason\n ... self.invited = []\n\nWe tell the ZCA how to adapt a Party to a watcher list: how to turn it\ninto an object that holds a list of interested people and knows how to\nsend them an email. Normally you would define an interface\n``IParty``, say that the ``Party`` class implements it and use zcml to\nregister an adapter for that, something like this::\n\n <adapter\n for=\".interfaces.IParty\"\n factory=\"collective.watcherlist.watchers.WatcherList\"\n />\n\nLet's ignore the interface and use python (as that is a bit easier to\nuse in tests). We will use the default implementation of a\nwatcherlist as provided by the package::\n\n >>> from zope.component import getGlobalSiteManager\n >>> from collective.watcherlist.watchers import WatcherList\n >>> sm = getGlobalSiteManager()\n >>> sm.registerAdapter(WatcherList, (Party, ))\n\n.. This documentation doubles as automated test, so we run into a test\n.. detail here: the WatcherList adapter stores the watchers in an\n.. annotation, so we need to tell the ZCA how to do that; for standard\n.. Plone/Archetypes content types this is already done, so you usually do\n.. not need to care about this. Oh, we can hide this, nice::\n :hide:\n\n >>> from zope.annotation.interfaces import IAnnotations\n >>> from zope.annotation.attribute import AttributeAnnotations\n >>> sm.registerAdapter(AttributeAnnotations, (Party, ), IAnnotations)\n\nNow we create a Party and invite people::\n\n >>> birthday = Party(\"Maurits' birthday\")\n >>> birthday.invited.append('Fred')\n >>> birthday.invited.append('Mirella')\n\nWe see if we can get a watcherlist for it::\n\n >>> from collective.watcherlist.interfaces import IWatcherList\n >>> watcherlist = IWatcherList(birthday)\n >>> watcherlist\n <collective.watcherlist.watchers.WatcherList object at ...>\n\nWe can ask several things of this list::\n\n >>> watcherlist.watchers\n []\n >>> watcherlist.send_emails\n True\n >>> watcherlist.addresses\n ()\n\nWe can add watchers. These should be email addresses or (at least in\na Plone context) the ids of members in the site. In your package you\nwould either create a button or other small form that people can use\nto add themselves to the list, or create some code that automatically\nadds some people, as Poi does for the creator of a new issue. The\ncode is simple::\n\n >>> watcherlist.watchers.append('maurits@example.org')\n >>> watcherlist.watchers.append('reinout@example.org')\n >>> watcherlist.watchers\n ['maurits@example.org', 'reinout@example.org']\n >>> watcherlist.addresses\n ('maurits@example.org', 'reinout@example.org')\n\nYou can always switch off email sending. This has the effect that no\naddresses are reported::\n\n >>> watcherlist.send_emails = False\n >>> watcherlist.watchers\n ['maurits@example.org', 'reinout@example.org']\n >>> watcherlist.addresses\n ()\n\nUndo that::\n\n >>> watcherlist.send_emails = True\n >>> watcherlist.watchers\n ['maurits@example.org', 'reinout@example.org']\n >>> watcherlist.addresses\n ('maurits@example.org', 'reinout@example.org')\n\nNow we send an email. We get the email text and subject simply from a\nbrowser view that we define. In the test this means we need to give\nthe Party a request object::\n\n >>> from zope.publisher.browser import TestRequest\n >>> birthday.REQUEST = TestRequest()\n\nWe now send an invitation email, but this fails::\n\n >>> watcherlist.send('invitation')\n Traceback (most recent call last):\n ...\n ComponentLookupError...\n\nThis means we need to create a browser view with that name. As the\nbasis we should take the base browser view defined in the\n``collective.watcherlist`` package. It contains three properties that\nyou would normally override: subject, plain and html::\n\n >>> from collective.watcherlist.browser import BaseMail\n >>> class PartyMail(BaseMail):\n ... @property\n ... def subject(self):\n ... return self.context.reason\n ... @property\n ... def plain(self):\n ... return \"Invited are %s\" % self.context.invited\n ... @property\n ... def html(self):\n ... return \"<p>%s</p>\" % self.plain\n\nYou would normally register this with zcml, just like any other\nbrowser view. But here we do that in python code::\n\n >>> from zope.interface import Interface\n >>> sm.registerAdapter(PartyMail, (Party, TestRequest), Interface, 'invitation')\n\nAnd we send the invitation again, in both plain text and html. In\nthis test we have no proper mail host setup, so we simply print the\nrelevant info so we can see what would happen::\n\n >>> watcherlist.send('invitation')\n Subject = Maurits' birthday\n Addresses = ('maurits@example.org', 'reinout@example.org')\n Message =\n From...\n Content-Type: multipart/alternative;...\n ...\n Content-Type: text/plain; charset=\"us-ascii\"\n ...\n Invited are ['Fred', 'Mirella']\n ...\n Content-Type: text/html; charset=\"us-ascii\"\n ...\n <p>Invited are ['Fred', 'Mirella']</p>\n ...\n\nLet's skip the html and see if that simplifies the mail::\n\n >>> PartyMail.html = ''\n >>> watcherlist.send('invitation')\n Subject = Maurits' birthday\n Addresses = ('maurits@example.org', 'reinout@example.org')\n Message =\n From...\n MIME-Version: 1.0\n Content-Type: text/plain; charset=\"us-ascii\"\n Content-Transfer-Encoding: 7bit\n <BLANKLINE>\n Invited are ['Fred', 'Mirella']\n\nIf there is neither plain text nor html, we do not send anything::\n\n >>> PartyMail.plain = ''\n >>> watcherlist.send('invitation')\n\nLet's add a bit of html again to see that only html goes fine too::\n\n >>> PartyMail.html = '<p>You are invited.</p>'\n >>> watcherlist.send('invitation')\n Subject = Maurits' birthday\n Addresses = ('maurits@example.org', 'reinout@example.org')\n Message =\n From...\n MIME-Version: 1.0\n Content-Type: text/html; charset=\"us-ascii\"\n Content-Transfer-Encoding: 7bit\n <BLANKLINE>\n <p>You are invited.</p>\n\nIf we switch off email sending for this watcherlist... no emails are sent::\n\n >>> watcherlist.send_emails = False\n >>> watcherlist.send('invitation')\n\nReset that::\n\n >>> watcherlist.send_emails = True\n\nLook at `Products.Poi <https://pypi.python.org/pypi/Products.Poi>`_ for some more examples of what you can do.\n\nChangelog\n=========\n\n3.1.0 (2018-04-26)\n------------------\n\n- Don't test with Plone 4.1, 4.2 or Python 2.6 anymore.\n It should still work, but I don't want to spend time fixing the build on Travis.\n [maurits]\n\n\n3.0.1 (2018-04-26)\n------------------\n\n- Declare ``zope.formlib`` dependency. [maurits]\n\n\n3.0 (2016-12-23)\n----------------\n\n- Pass ``immediate=False`` by default. This used to be ``True``. The\n original idea was to send emails immediately, so that we could catch\n any errors ourselves and continue with a warning. But since Plone\n 4.1 the emails are by default sent at the end of the transaction,\n and exceptions are caught. For immediate mails they are not caught\n there. So for our uses cases it makes most sense to not send emails\n immediately, as then Plone does what we want already. You can still\n pass ``immediate=True`` to ``mailer.simple_send_mail`` or now also\n to ``watchers.send`` if you want the old behavior back.\n This fixes `issue #8 <https://github.com/collective/collective.watcherlist/issues/8>`_.\n [maurits]\n\n- Check ``allow_recursive`` on the watcher list. The default value is\n true, which gives the same behavior as before. When the value is\n false, the ``addresses`` property only looks for watchers on the\n current item, not on the parent. A sample usage would be in\n Products.Poi to only allow recursive if an issue is not yet\n assigned. (I am going to use this in custom code for a client).\n [maurits]\n\n- Strip the email address that we get from a member or the site.\n I have a site where some email addresses are ``test@example.org\\r\\n``,\n which gives an error when sending.\n [maurits]\n\n\n2.0 (2016-07-07)\n----------------\n\n- Removed backwards compatibility code for Plone 3.3 and 4.0. We\n already were not testing on 3.3 anymore, and 4.0 is too hard to keep\n working too. [maurits]\n\n- Fixed Plone 5 email sending. Improved code quality. Fixed Travis tests. [maurits]\n\n- When the internal watchers list is of type list (instead of tuple),\n make sure its updated when toggling a watcher [skurfer]\n\n1.2 (2013-12-03)\n----------------\n\n- Added events, triggers and action for content rules. [Gagaro]\n\n\n1.1 (2012-11-06)\n----------------\n\n- Made compatible with Plone 4.3 (keeping compatibility with Plone 3).\n [maurits]\n\n- Moved to https://github.com/collective/collective.watcherlist\n [maurits]\n\n\n1.0 (2012-04-21)\n----------------\n\n- When showing the plain text in the browser as test, force text/plain\n as content-type.\n [maurits]\n\n\n0.3 (2011-05-09)\n----------------\n\n- Catch MailHostErrors when sending email.\n [maurits]\n\n\n0.2 (2010-02-27)\n----------------\n\n- You can now add ``only_these_addresses`` as an argument to the send\n method. This forces sending only to those addresses and ignoring\n all others.\n [maurits]\n\n- Fixed possible UnicodeDecodeError when the plain text or html part\n of the email was not unicode.\n [maurits]\n\n\n0.1 (2010-02-26)\n----------------\n\n- Initial release",
"bugtrack_url": null,
"license": "GPL",
"summary": "Send emails from Plone to interested members (watchers)",
"version": "3.1.0",
"project_urls": {
"Homepage": "https://github.com/collective/collective.watcherlist"
},
"split_keywords": [
"plone",
"notifications",
"watching"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "fed7eeb09281abd8635f8c0fccca00f9aa9dbf2ff2287948f3b799abd4f03640",
"md5": "1e16bc58e2d0e47abefcb5e186d7e741",
"sha256": "ae7fe3918479f5cd4a5faef415c930690d468c7caa098376d386d34b69f647c6"
},
"downloads": -1,
"filename": "collective.watcherlist-3.1.0.tar.gz",
"has_sig": false,
"md5_digest": "1e16bc58e2d0e47abefcb5e186d7e741",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 33071,
"upload_time": "2018-04-26T20:54:05",
"upload_time_iso_8601": "2018-04-26T20:54:05.797498Z",
"url": "https://files.pythonhosted.org/packages/fe/d7/eeb09281abd8635f8c0fccca00f9aa9dbf2ff2287948f3b799abd4f03640/collective.watcherlist-3.1.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2018-04-26 20:54:05",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "collective",
"github_project": "collective.watcherlist",
"travis_ci": false,
"coveralls": true,
"github_actions": true,
"tox": true,
"lcname": "collective.watcherlist"
}
JSON
