On Tuesday, March 19, 2013 2:31:09 PM UTC-4, Vincent Catalano wrote:
>
> I am not using a commandline interface. I ended up creating a new
> APScheduler instance from within the applications main() function. That
> way, the scheduled service will run only when the server is running. It is
> in t
I am not using a commandline interface. I ended up creating a new
APScheduler instance from within the applications main() function. That
way, the scheduled service will run only when the server is running. It is
in the applications main() function that I create a pyramid_mailer instance
and pass i
reading your question... are you using a commandline interface/script for
the nightly task ?
>
>
http://docs.pylonsproject.org/projects/pyramid/en/1.4-branch/narr/commandline.html
after initiating the bootstrap, it would be just a few lines of logic to
handle your work -- and it all would
Thanks for the reply, Eric. I think I figured out a solution, albeit my
question was a bit confusing. I have an e-commerce website that integrates
with a payment gateway in order to manage paid subscriptions for users.
Sometimes these subscription payments fail - either from expired cards or
insuff
I may be misunderstanding the question because I am not too familiar with
APScheduler, but it sounds like you want to use
mailer.send_to_queue(message) instead of mailer.send(message).
As long as you're sending it to the queue for later processing there
shouldn't be any need to have multiple Maile
I'm attempting to setup pyramid_mailer with a website I'm developing. The
current documentation (
http://docs.pylonsproject.org/projects/pyramid_mailer/en/latest/)
recommends creating a single instance of the Mailer and adding it to the
configuration setup. However, I want to configure numerous job
