python / python/cpython

Can't start new Python release 3.13.0 b1

Open
#118,860 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.13 OS-windows stale type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

Bug report

Bug description:

py
Fatal Python error: Failed to import encodings module
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00034e24 (most recent call first):

CPython versions tested on:

3.12

Operating systems tested on:

Windows

Linked PRs
  • gh-153382

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.

Research direction

The report names no source file or test; begin by reproducing the Windows startup failure with CPython 3.12 and inspect linked PR gh-153382. Done means the affected Python release starts without the fatal encodings import error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.