Prepare Python 3.16 deprecation for windows asyncio

Open
#13,713 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
jupyter, python

Research direction

Start with src/resources/jupyter/jupyter.py at line 28 and read the asyncio policy deprecation documentation linked in the issue. Reproduce the warning while rendering with Python 3.14 on Windows, then verify the updated behavior does not emit these deprecation warnings and remains compatible with Python 3.16.

Written by the indexing model from the issue text.

Description

engines-jupyter enhancement
Starting python3 kernel...C:\Users\chris\Documents\DEV_R\quarto-cli\src\resources\jupyter\jupyter.py:28: DeprecationWarning: 'asyncio.WindowsSelectorEventLoopPolicy' is deprecated and slated for removal in Python 3.16
  asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())
C:\Users\chris\Documents\DEV_R\quarto-cli\src\resources\jupyter\jupyter.py:28: DeprecationWarning: 'asyncio.set_event_loop_policy' is deprecated and slated for removal in Python 3.16
  asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())

This is while rendering with Python 3.14.0

See

We need to prepare for that.

Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from quarto-dev/quarto-cli

All issues in quarto-dev/quarto-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.