3 ms·

I don't disagree with your claim, but like all moral claims, I don't see how it's actually useful or actionable. Children should not get cancer. People should n

I don't disagree with your claim, but like all moral claims, I don't see how it's actually useful or actionable. Children should not get cancer. People should not drive without seatbelts. Our optic nerve exit the back of our eye instead of having to go through blind spot on our retina. And yet here we are. The Python ecosystem is older than our modern conception of how a package manager should behave. Any new package manager must build on top of that chaotic history. Absent a time machine, your comment just seems like a vague lament about the state of the world.

d0mine 6y ago
Actionable: use backward-compatible behavior by default. Use opt-in for new features. Question: is the new resolver opt-in or is it enabled by default in the new pip version?
- colechristensen 6y ago
  It is enabled by default. I think there was a beta period where it was an option.
  - user5994461 6y ago
    And there is an argument to disable the check.
- xapata 6y ago
  How long should someone wait before deprecating the old behavior?
colechristensen 6y ago
The action is simple, stop making breaking changes. There is frustration with breaking changes being in the history, but that is much less troubling than the reoccuring answer to the question “What is wrong with my code?” being “A new version of the package manager was released.” It is also very possible to write code to completely work around old issues so the newest version of your package manager just works or at least outputs clear error messages with mitigation steps, but instead what you get is obscure stack traces when you run pip install.
- user5994461 6y ago
  I tried the new version of pip and it's giving clear error messages when there are incompatibilities between versions. That should make your life easier.
- ptx 6y ago
  Many of the breaking changes had to do with removing accidental features from the constraint file implementation. It seems a lot better to break that now rather than wait for people to accidentally start using and depending on those unintentional implementation quirks.

d0mine 6y ago

Actionable: use backward-compatible behavior by default. Use opt-in for new features. Question: is the new resolver opt-in or is it enabled by default in the new pip version?

colechristensen 6y ago
It is enabled by default. I think there was a beta period where it was an option.
- user5994461 6y ago
  And there is an argument to disable the check.
xapata 6y ago
How long should someone wait before deprecating the old behavior?

colechristensen 6y ago

The action is simple, stop making breaking changes. There is frustration with breaking changes being in the history, but that is much less troubling than the reoccuring answer to the question “What is wrong with my code?” being “A new version of the package manager was released.” It is also very possible to write code to completely work around old issues so the newest version of your package manager just works or at least outputs clear error messages with mitigation steps, but instead what you get is obscure stack traces when you run pip install.

user5994461 6y ago
I tried the new version of pip and it's giving clear error messages when there are incompatibilities between versions. That should make your life easier.
ptx 6y ago
Many of the breaking changes had to do with removing accidental features from the constraint file implementation. It seems a lot better to break that now rather than wait for people to accidentally start using and depending on those unintentional implementation quirks.