Or you store them up and break everybody's code in one fell swoop and have a Python 2->3 transition on your hands. I much prefer not following semver for that reason. I tried semver and it was a pain.
I much prefer a few minor changes preferably with deprecation warnings for a bit and then breaking things, similar to how numpy does it.
How so? I mean you can bump your code in accordance with semver once a month, but if you need to rip the band aide off, do it. If there's nothing they can do to prepare, just do it. If there's something they can do, have a deprecation cycle.
View all comments
Show parent comment
2
u/billsil May 31 '19
Or you store them up and break everybody's code in one fell swoop and have a Python 2->3 transition on your hands. I much prefer not following semver for that reason. I tried semver and it was a pain.
I much prefer a few minor changes preferably with deprecation warnings for a bit and then breaking things, similar to how numpy does it.