There are at least two types of ‘patzer’ in the ‘Software Development’ domain, these two have caused me more hassle and annoyance than any other part of the mangled shit we have to deal with frequently:-

• The complete innocent who ‘contributes’ an article and/or code project, without specifying the version and/or revision of the software environment on which his/her project depends.
• The developer/maintainer who deletes/alters previously published library code, with nary a thought for whatever has been written for the previous version.

By far, the worst offenders are ‘contributors’ in the Python Development Community. Yes, things have changed, certainly for me.If anyone used to develop software on Microsoft’s ‘environment’, they will remember, probably with horror, the ‘DLL Hell’ everyone had to experience.
‘Things’ should have changed, but they haven’t, well not much.

In the above, just a few simple rules are required. The ‘developer’ does NOT delete/alter previously released functions. These should be supported but marked as ‘deprecated’. All too often the developer is making use of an ‘exposed’ interface him/herself. This is simply sloppy and lazy.
The ‘contributor’ simply provides the version and revision of his Python interpreter, and similar for the libraries he is using.

As is usual when there is ‘misunderstanding’ between folks speaking different languages, we could blame the interpreter.
Mostly, this is the root cause of the problem, with Python, and similar interpreters.

Several times I see ‘solutions’ involving downloading and building libraries from scratch on my own machine. So apparently I have to ‘manufacture’ my ‘batteries’? On such occasions I’m tempted to comment by suggesting that the ‘contributor’ finds a quiet corner, and stands with his face in it,
Well, no I’m not tempted to say that, but something quite different, but have no wish to offend.