Change __future__ docs description to avoid confusion with concurrency futures

[arhadthedev]

Currently, the library index page describes __future__ as:

__future__ — Future statement definitions

However, it creates confusion with futures from the concurrency domain. So this PR changes the description to:

__future__ — Early access to language features created for future versions of Python

Edit: replaced with a shorter wording:

__future__ — Early access to future language features

[carljm]

Looks like an improvement to me.

[carljm]

LGTM!

[arhadthedev]

Could anybody merge the PR if possible please? This is the last one after gh-92761 and gh-92762.

[JelleZijlstra]

I don't find the current wording unclear, and the proposed new wording is so long that it will make the page title spill into multiple lines on many screens. If another core dev has a different opinion, I won't object to merging this though.

[arhadthedev]

@JelleZijlstra Will Early access to future language features be better?

Edit: for comparison:

original: Future statement definitions
initial: Early access to language features for future versions of Python
fixed: Early access to future language features

[arhadthedev]

Applied the shorter wording described above.

[arhadthedev]

Ping.

[JelleZijlstra]

Sorry, I still don't see a reason for change here. I'm leaving this open in case another core dev thinks there's room for improvement, but I'm not planning to merge anything.