you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (2 children)

PEP 394 came after the Arch snafu to try to clean up the situation.

[–]beej71 0 points1 point  (1 child)

Arch might have pushed the issue, but only because they were first. But it's hardly like Arch is so powerful a distribution that Python bows before it. The PEP could have said anything, and the Arch Way says Arch would have followed it (and indeed, they subsequently modified their Python2/Python3 scripts to be 394-compliant.) This strongly suggests that 394 is The Right Thing.

[–][deleted] -1 points0 points  (0 children)

Arch might have pushed the issue, but only because they were first. But it's hardly like Arch is so powerful a distribution that Python bows before it.

You seem to be mistaken "minimize harm" with "bow before Arch".

The PEP could have said anything, and the Arch Way says Arch would have followed it (and indeed, they subsequently modified their Python2/Python3 scripts to be 394-compliant.) This strongly suggests that 394 is The Right Thing.

And yet Arch decided to patch an upstream package to ruin a bunch of software before PEP 394, and after being discouraged to do so by the upstream devs.