You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node.js configure: Found Python 3.15.0...
Please use python3.14 or python3.13 or python3.12 or python3.11 or python3.10.
But I think python 3.15 rc1 should work too. Is this check perhaps a bit too
conservative? Or is there a way to work around it?
Anyway I guess I'll downgrade python momentarily to compile node, but I think
python 3.15 should work fine. Just reporting this here.
TL;DR: Please consider supporting python 3.15, even if it is not yet stable, for
configuring and then compiling node. In my opinion it should work just fine
for the compilation step.
Locally you can adjust acceptable_pythons near the top of the configure script to allow it to run 3.15. Obviously "at your own risk" :-)
It might just work ... It might not. A few years ago I did propose a change that gave you a hint on how to make this change - #41051 - but it was rejected.
This release, 3.15.0rc1, is the first of two planned candidate releases. Entering the release candidate phase, only reviewed code changes which are clear bug fixes are allowed between this release candidate and the final release.
The next release of Python 3.15 will be 3.15.0rc2, scheduled for 2026-09-01.
Locally you can adjust acceptable_pythons near the top of the configure script to allow it to run 3.15. Obviously "at your own risk" :-)
You only need to run configure (without the .py extension) if you want the script to detect the Python version(s) and select a known compatible version. If you know what Python you want to run you should instead run configure.py which does not go through the version detection logic.
The BUILDING > Prerequisites documentation has been updated to clarify that pre-release Python versions are not supported by Node.js, although they are listed in Python's Supported versions list.
PR #65750 is already set up to add Python 3.15 support to Node.js once the final release, planned for 2026-10-01 2026-10-09, is available.
Activity
[-]Please support python 3.15[/-][+]configure does not support Python 3.15[/+]sxa commentedon Aug 28, 2026
Locally you can adjust
acceptable_pythonsnear the top of theconfigurescript to allow it to run 3.15. Obviously "at your own risk" :-)It might just work ... It might not. A few years ago I did propose a change that gave you a hint on how to make this change - #41051 - but it was rejected.
MikeMcC399 commentedon Aug 28, 2026
8bc7dfd was the equivalent for updating to 3.14 prerelease.
I would expect Python 3.15 to get addressed nearer to its planned release date of 2026-10-01.
https://www.python.org/downloads/release/python-3150rc1/ says:
MikeMcC399 commentedon Aug 29, 2026
@rubyFeedback
Downgrading to a supported version of Python would be your best option at this time.
You may be right, however before Node.js accepts Python 3.15 it needs to be fully tested on all environments.
[-]configure does not support Python 3.15[/-][+]Python 3.15 rc1 release candidate unsupported[/+]MikeMcC399 commentedon Sep 2, 2026
richardlau commentedon Sep 3, 2026
You only need to run
configure(without the.pyextension) if you want the script to detect the Python version(s) and select a known compatible version. If you know what Python you want to run you should instead runconfigure.pywhich does not go through the version detection logic.doc: clarify supported Python releases
MikeMcC399 commentedon Sep 8, 2026
The BUILDING > Prerequisites documentation has been updated to clarify that pre-release Python versions are not supported by Node.js, although they are listed in Python's Supported versions list.
PR #65750 is already set up to add Python 3.15 support to Node.js once the final release, planned for
2026-10-012026-10-09, is available.doc: clarify supported Python releases