On 2011-03-01 17:58:37 -0800, oO said:
is there a framework adapter for pyramid in TurboMail yet? or can you
just use the pylons one?
The Pylons adapter is broken in the current release (due to changes
present in the release of Pylons 1.0) and adapters, in general, will be
phased out in the next major version of TurboMail. There are too many
frameworks to warrant the additional code to the general package;
adapters belong in a separate small package or in the framework itself.
The next major release will also be accompanied by a name change to
distance the package from TurboGears. (There is nothing
TurboGears-specific or -required by the TurboMail package.)
Also, the Pylons adapter would simply not be compatible with Pyramid.
One of the nice things about pyramid_mailer is the fact that you stick
your settings in the ini file, and you have a simple
Mailer.from_settings(settings) call.
I'm not sure how much adaption would be necessary, however, utilizing
TurboMail is very similar to the process you describe:
from turbomail.control import interface
interface.start(settings)
However, if the values from the configuration are loaded without
typecasting (integers to integers, etc.) than you might need to model
your adapter after the Pylons one:
https://bitbucket.org/gothalice/turbomail/src/d6331182b0a6/turbomail/adapters/tm_pylons.py
The
atexit code is a nicety for gracefully shutting down the thread pool
while allowing the message queue to drain before actually exiting the
application.
— Alice.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
