Bump apscheduler from 3.9.1.post1 to 3.11.0

[dependabot]

Bumps apscheduler from 3.9.1.post1 to 3.11.0.

Release notes

Sourced from apscheduler's releases.

3.11.0

• Dropped support for Python 3.6 and 3.7
• Added support for ZoneInfo time zones and deprecated support for pytz time zones
• Added CalendarIntervalTrigger, backported from the 4.x series
• Added the ability to export and import jobs via scheduler.export_jobs() and scheduler.import_jobs(), respectively
• Removed the dependency on six
• Changed ProcessPoolExecutor to spawn new subprocesses from scratch instead of forking on all platform
• Fixed AsyncIOScheduler inadvertently creating a defunct event loop at start, leading to the scheduler not working at all
• Fixed ProcessPoolExecutor not respecting the passed keyword arguments when a broken pool was being replaced

Changelog

Sourced from apscheduler's changelog.

Version history

To find out how to migrate your application from a previous version of APScheduler, see the :doc:migration section <migration>.

3.11.0

• Dropped support for Python 3.6 and 3.7
• Added support for ZoneInfo time zones and deprecated support for pytz time zones
• Added CalendarIntervalTrigger, backported from the 4.x series
• Added the ability to export and import jobs via scheduler.export_jobs() and scheduler.import_jobs(), respectively
• Removed the dependency on six
• Changed ProcessPoolExecutor to spawn new subprocesses from scratch instead of forking on all platform
• Fixed AsyncIOScheduler inadvertently creating a defunct event loop at start, leading to the scheduler not working at all
• Fixed ProcessPoolExecutor not respecting the passed keyword arguments when a broken pool was being replaced

3.10.4

• Fixed incorrect module name being generated for references to class methods via a subclass where the subclass does not override the method

3.10.3

• Fixed TypeError related to entry point iteration on Python 3.9 (PR by CrypticDriver)

3.10.2

• Ensured consistent support for both PySide and PyQt (v6 to v2) on QtScheduler
• Replaced uses of the deprecated pkg_resources module with importlib.metadata (PR by Ran Benita)
• Fixed scheduling class methods like B.methodname where the B class inherits from class A and methodname is a class method of class A
• Fixed scheduler sleeping for too long (and thus jobs missing their scheduled run times) if its wakeup cycle takes too much time (fix by kbasten)

3.10.1

• Fixed TypeError: arguments did not match any overloaded call: in QtScheduler due to wait_time being float and not an integer which QT needs it to be

3.10.0

• Fixed compatibility with SQLAlchemy 2.0 and bumped minimum supported version to 1.4

... (truncated)

Commits

• 6c72a51 Backported release job from master
• 4b96510 Added the release version
• fcec69c Added user's guide section for export/import
• 50f67c8 Added scheduler methods for job export/import
• 40431e5 Removed the obsolete timedelta_seconds function
• 9483bb4 Rearranged triggers tests to better match the master branch
• ac55c86 Fixed project links to point to the correct branch on RTD
• 811e973 Changed version history formatting to match the master branch
• f3c68df Pass pool_kwargs to the replacement process pool too
• 4584091 Removed unwarranted classifier
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.