abobla@lemm.ee to Programming@programming.devEnglish · 1 year agoDeath by a thousand microservicesrenegadeotter.comexternal-linkmessage-square21fedilinkarrow-up1121arrow-down15cross-posted to: [email protected][email protected][email protected][email protected]
arrow-up1116arrow-down1external-linkDeath by a thousand microservicesrenegadeotter.comabobla@lemm.ee to Programming@programming.devEnglish · 1 year agomessage-square21fedilinkcross-posted to: [email protected][email protected][email protected][email protected]
minus-squaremagic_lobster_party@kbin.sociallinkfedilinkarrow-up5·1 year agoYou know the cleaning up probably won’t happen. If some dependency doesn’t work anymore because Python introduced a breaking change, then you stick with the old Python version.
minus-squarethbb@kbin.sociallinkfedilinkarrow-up3·1 year agoPython is actually a good example of this: see the mess that the transition from 2.6 to 3 generated.
minus-squaremagic_lobster_party@kbin.sociallinkfedilinkarrow-up2·edit-21 year agoPython 3.7 is another good example. The new await and async keyword broke a lot of programs.
You know the cleaning up probably won’t happen. If some dependency doesn’t work anymore because Python introduced a breaking change, then you stick with the old Python version.
Python is actually a good example of this: see the mess that the transition from 2.6 to 3 generated.
Python 3.7 is another good example. The new await and async keyword broke a lot of programs.