Skip to content
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

Proposal: Deprecate process.features.ipv6 and process.features.uv #55537

Closed
Renegade334 opened this issue Oct 25, 2024 · 4 comments · Fixed by #55545
Closed

Proposal: Deprecate process.features.ipv6 and process.features.uv #55537

Renegade334 opened this issue Oct 25, 2024 · 4 comments · Fixed by #55545
Labels
deprecations Issues and PRs related to deprecations.

Comments

@Renegade334
Copy link
Contributor

process.features.ipv6 and process.features.uv have both been hard-coded to true since pre-v1.0.0. Indeed, by the looks of things, process.features.ipv6 has always been hard-coded to true since process.features was first added.

There has been a longstanding todo comment about improving the features API (cc @joyeecheung) but for now, seems like deprecating these would be fairly uncontroversial.

@RedYetiDev RedYetiDev added the deprecations Issues and PRs related to deprecations. label Oct 25, 2024
@marco-ippolito
Copy link
Member

pr welcome

@Renegade334
Copy link
Contributor Author

Renegade334 commented Oct 25, 2024

Where would you recommend these live in terms of deprecation cycle? They've been redundant for well over a decade, so is there a case for sending them straight to runtime?

The tls_* properties are also redundant since v11.0.0 (a76f029) so could probably also take the opportunity to doc-deprecate these.

@RedYetiDev
Copy link
Member

so is there a case for sending them straight to runtime?

I don't believe so, IIRC everything must go through the cycle.

@bnoordhuis
Copy link
Member

Doc-deprecating is fine (if kind of pointless IMO) but runtime warnings or removing them is potentially disruptive for no benefit whatsoever.

Having a few superfluous properties doesn't cost anything. Just keep them around forever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deprecations Issues and PRs related to deprecations.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants