Comments (3)
Original comment by Alex Grönholm (Bitbucket: agronholm, GitHub: agronholm):
That is understandable as the documentation has not been updated for 3.0 syntax yet.
They are given as keyword arguments to add_job().
from apscheduler.
Original comment by croxis (Bitbucket: croxis, GitHub: croxis):
I wasn't sure how to pass the cron attributes in the add_job format. At the time the documentation wasn't clear to me.
from apscheduler.
Original comment by Alex Grönholm (Bitbucket: agronholm, GitHub: agronholm):
Good catch. The error was introduced while the trigger API was in a flux. Seems like the tests didn't catch it. That said, it still should've worked through scheduler.add_job(). Is there a particular reason why you're constructing a trigger instance manually?
from apscheduler.
Related Issues (20)
- AsyncIOScheduler not working with MongoDBJobStore (PicklingError) HOT 3
- AsyncIOScheduler not working with MongoDBJobStore (cannot pickle 'TaskStepMethWrapper' object) HOT 3
- `__{a}exit__` typing
- sqlalchemy.exc.ProgrammingError: (asyncmy.errors.ProgrammingError) (1064, "You have an error in your SQL syntax; HOT 3
- TypeError: RetryMixin._retry.<locals>.after_attempt() missing 1 required positional argument: 'retry_state' HOT 1
- Worker stops if there are "too much" simultaneous jobs HOT 2
- Objects inside the job are instantiated multiple times HOT 2
- SQLAlchemyDataStore doesn't respect a custom schema for types
- Create a Cron Trigger with month="*/12" does not work HOT 6
- Allows defining custom pickling method. HOT 5
- So confusing between sync and async. HOT 2
- Logger not logging events of the scheduler instance
- Infinite loop in CalendarIntervalTrigger with UTC timezone
- Support pausing and unpausing schedules HOT 4
- When a job is forcibly cancelled by calling `stop()`, the added schedule to the scheduler will no longer create new job.
- background cron job getting stopped after time run HOT 1
- Implement schedule filters
- [v4.0.0a4] Combining daily and weekly triggers increments by 14 days HOT 7
- [v4.0.0a4] Setting `timezone` in `CalendarIntervalTrigger` loops forever HOT 1
- RuntimeError: cannot schedule new futures after interpreter shutdown when the job is triggered HOT 6
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 apscheduler.