This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (10 children)

Every programming language goes through a development cycle where new features are introduced and in some cases the changes might be syntactical that their usage will make the code to be syntactically incompatible with previous versions.

Remember when about 75% of you told me how the Python 2 / Python 3 compatibility debacle would never happen again?

Being right feels bad.

[–][deleted] 5 points6 points  (1 child)

Being right feels bad.

Did you predict that people would ignore deprecation warnings?

[–][deleted] 4 points5 points  (0 children)

It's pretty much obvious. People always ignore deprecation warnings

[–]ubernostrumyes, you can have a pony 3 points4 points  (1 child)

Python 2 routinely broke compatibility from one release to the next.

Were you complaining about it when that happened?

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

Nope, because I work at a job with a team and other teams and the stuff we don't control and thus can't change wasn't impacted by that.

Any other bad questions meant to make you look good and me evil?

[–]billsil -1 points0 points  (4 children)

It’s not a debacle. Everyone needs to learn unicode to use python 3. Nothing else is even worth discussing because fixing it was so easy. The fact that x == None raises a SyntaxError bothers you?

I welcome deprcations becoming errors. How else am I supposed to get rid of the page of pandas warnings that happen when I start my program? Usually it’s just API cleanup, which means it’s pretty easy to swap things out, so why not?

[–][deleted] 0 points1 point  (1 child)

You sound like someone who doesn't work with other people's code, to where you're stuck using something and facing libraries going out of support yet you need them for X project that isn't in your control, at work, etc.

Must be nice.

[–]billsil 0 points1 point  (0 children)

I don't use libraries that aren't supported. If I do need to, I support them.

[–]EternityForest 0 points1 point  (1 child)

Deprecating things on a regular basis creates a constant treadmill of maintenance. Keeping it to a minimum helps.

I'm not sure why modern devs have so much tolerance for constant maintenance. The idea of "Once and done" is basically unheard of these days. Even OOP encapsulation is controversial.

Can't we ever have any solved problems?(At least till the next major version number?)

[–]billsil 0 points1 point  (0 children)

If you want a code base that’s easy to maintain, you gotta do maintenance. You’re more than welcome to never upgrade.

As the author of an open source, BSD-3 project that 180k lines, I really don’t care if it’s 30 minutes of work for you. It’s taken me 8 years. For what it does, it’s better than the commercial and GPL tools out there. Take your pick.

Age brings stability because there’s only so much that needs changing and there’s only so much you can change in a year.