Comments (3)
It looks like your problem is caused by reusing the schedule returned by parse_work_schedule
, rather than where the functions are defined; you can see this by swapping the order in which you call sched
-- only the last one called will actually be scheduled (this is expected, since do
will just overwrite the job function each time it's called).
Instead, you could try something like changing all
to a lambda so that it returns a new schedule every time:
def parse_work_schedule(self, work):
options = {
'all': lambda: self.schedule.every().minute.do,
}
return options['all']
and then using it as such:
for work in self.works:
if sched and sched():
sched()(pp, work['name'])
sched()(work['func'], work['name'])
print 'Scheduled: {0}'.format(sched)
else:
print 'Function pointer {0} returned None value.'.format(sched)
from schedule.
Hi dylwhich,
I tried your suggestion but it didn't work.
Perhaps I'm not clear with my question (and code).
If you uncomment and comment out:
sched(pp, work['name'])
# sched(work['func'], work['name'])
The code, as it is, works. However, when the comments are swapped, i.e.
# sched(pp, work['name'])
sched(work['func'], work['name'])
the code doesn't work. Why is that? Both are functions.
from schedule.
I found the answer. Both are not functions. pp is a function hence it works correctly. But work['func'] is an instancemethod type. So the solution is to have a method within the class that returns a function object. Then I can provide that function object to the schedule.
Thanks for your help.
from schedule.
Related Issues (20)
- python
- Potential problem of spawning sub processes HOT 2
- Unable to schedule from a specific time and following a specific calendar HOT 2
- odd daylight saving behaviour HOT 2
- instant execution of job with every().days.at on first run HOT 6
- still having cross-timezone problems in 1.2.1 HOT 2
- weekday
- daylight saving bug HOT 3
- Inconsistent startup behaviour on daily tasks at midnight - Timezone related HOT 10
- Extract only the time from next_run_datetime() HOT 2
- How can I retrieve the name of the next scheduled job?
- Weekly job fails with interval > 1
- Why did three separate python scripts using schedule start at different time eventually converged to be in sync?
- the time of job needed will be count for every ?
- Schedule only runs once? HOT 2
- Questions about Copilot + Open Source Software Hierarchy
- Timer reset.
- Returning a value from a scheduled function
- Job won't stop with schedule.every(1).minute.until(timedelta(3)).do(function, args) HOT 1
- scaling / multiple workers
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from schedule.