-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tools: the docserve
make target doesn't seem to finally serve
#34977
Comments
For reference, the target code is the following: Lines 778 to 780 in c2996ce
This is indeed Python 3 only (https://docs.python.org/3/library/http.server.html). I don't know if we want to patch it given the fact that Python 2 has reached End-of-Life and this is not actually part of the build chain anyway.
Python 2 users can use |
I see why this is happening now. I am running Debian 10, so the following line in the Makefile detects Line 4 in a1faa8d
Here's the reason why…
For this to work for me, I would need line 4 to be … PYTHON ?= python3 … to execute the following. Lines 778 to 780 in c2996ce
However, doing so would likely break all the other commands expecting We could add a new constant called PYTHON3 ?= python3 And update the Makefile to use it for all of the newest targets Python is being used quite heavily in the build tooling, so I wonder what our stance is on this. Here are Debian's goals.
💭 We probably want to ensure everything is working w/ Python 3 in the near-term. |
Lines 225 to 230 in a1faa8d
If you have Python 3 installed but isn't used by the build tools, there is a bug somewhere. FWIW Python 2 is currently still supported for UNIX/Linux systems only. On Windows, Python 3 is already required according to our docs: Lines 523 to 529 in a1faa8d
|
This would technically fall under UNIX prerequisites, but somehow the |
This patch improves the means by which the docs are viewed locally. * Remove extraneous code in the `docserve` Makefile target * Document the `docserve` task for all to know * Bring all code snippets in this section up to speed * Clarify the purpose of each documentation browsing method Fixes: #34977 PR-URL: #34986 Reviewed-By: Richard Lau <riclau@uk.ibm.com>
This patch improves the means by which the docs are viewed locally. * Remove extraneous code in the `docserve` Makefile target * Document the `docserve` task for all to know * Bring all code snippets in this section up to speed * Clarify the purpose of each documentation browsing method Fixes: #34977 PR-URL: #34986 Reviewed-By: Richard Lau <riclau@uk.ibm.com>
This patch improves the means by which the docs are viewed locally. * Remove extraneous code in the `docserve` Makefile target * Document the `docserve` task for all to know * Bring all code snippets in this section up to speed * Clarify the purpose of each documentation browsing method Fixes: #34977 PR-URL: #34986 Reviewed-By: Richard Lau <riclau@uk.ibm.com>
This patch improves the means by which the docs are viewed locally. * Remove extraneous code in the `docserve` Makefile target * Document the `docserve` task for all to know * Bring all code snippets in this section up to speed * Clarify the purpose of each documentation browsing method Fixes: #34977 PR-URL: #34986 Reviewed-By: Richard Lau <riclau@uk.ibm.com>
This patch improves the means by which the docs are viewed locally. * Remove extraneous code in the `docserve` Makefile target * Document the `docserve` task for all to know * Bring all code snippets in this section up to speed * Clarify the purpose of each documentation browsing method Fixes: nodejs#34977 PR-URL: nodejs#34986 Reviewed-By: Richard Lau <riclau@uk.ibm.com>
What steps will reproduce the bug?
Simply clone the repo and run
make docserve
.How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior?
To actually serve the static documentation pages.
What do you see instead?
Additional information
It's possible that this issue should be in @nodejs/help, but I'm somewhat convinced that this is indeed a bug in the Makefile code since this doesn't work using Python 2.7.16. If it's supposed to be Python 3 code, perhaps we should force that to make this work, but at the same time, I don't understand why the command is so complex. Shouldn't it just be the following?
Refs: https://docs.python.org/2/library/simplehttpserver.html
/cc @aduh95 as was the one who introduced this feature in #33221
The text was updated successfully, but these errors were encountered: