Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ImportError: No module named scheduler #10

Open
tonthon opened this issue Nov 5, 2014 · 6 comments
Open

ImportError: No module named scheduler #10

tonthon opened this issue Nov 5, 2014 · 6 comments

Comments

@tonthon
Copy link

tonthon commented Nov 5, 2014

There is no module named scheduler anymore.

File "/.../lib/python2.7/site-packages/pyramid_scheduler/scheduler.py", line 17, in
import apscheduler, apscheduler.scheduler, apscheduler.events
ImportError: No module named scheduler

>>> apscheduler.__version__
'3.0.1'

Solutions

  • setup.py should be updated
  • imports should be modified
@Zitrax
Copy link

Zitrax commented Oct 8, 2015

This still seem to be an issue.

Commenting out that line lead to a second import error: ImportError: No module named ram_store

Sine this issue was reported quite a while ago it makes me wonder if the project is dead or is it just some configuration issue ? I tried to follow the installation doc.

@tonthon
Copy link
Author

tonthon commented Oct 8, 2015

I ended up moving to celery for scheduling tasks

@grabner
Copy link
Member

grabner commented Oct 8, 2015

huge apologies for not seeing this issue earlier! it did not show up in my feed until now...

this is a problem with the 3.x version of APScheduler, which i will look into adding support for shortly (probably today). in the meantime, you can get it working by using a 2.x version of APScheduler (one of the dependencies of pyramid-scheduler).

celery is a good alternative; we just found it far too heavy-handed and sometimes an awkward API for doing fairly simple scheduling and background jobs.

@grabner
Copy link
Member

grabner commented Oct 8, 2015

unfortunately, the 3.x APScheduler API is significantly different, so this will not be a quick fix (but we will eventually do it). in the meantime, you can use a 2.x version of APScheduler.

@meyerjo
Copy link

meyerjo commented May 24, 2016

Any update on that? Is the project still maintained?

@Rogalek
Copy link

Rogalek commented Sep 20, 2018

What about that? problem still occur after some time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants