(no title)
jarboot | 11 months ago
In the rationale for this that I can find [1], a maintainer says the following:
> I'm inclined to say we should do it, even though it will cause some disruption.
They also say an alternative is to "accept the status quo", which is exactily what they should be doing. I can't find maintainers giving a compelling reason not to support this status quo of `long-description` as an alias to `long_description` besides "simplifying code." Code simplification should never take precedence over massive breakage of compatibility.
[1] https://github.com/pypa/setuptools/pull/4870#pullrequestrevi...
HereBeBeasties|11 months ago
> The maintainers of setuptools get paid by Tidelift to
> implement industry-leading secure software development
> practices and document the practices they follow.
Well, that really doesn't seem so in this case now, does it?
Numerlor|11 months ago
jarboot|11 months ago
The conditions that lead to having two tokens pointing to the same functionality should be prevented, but in this case it is a "de facto" alias which no amount reasonable amount of labor could fix.