&gt;  Yes, it&#x27;s possible that there could be a problem with a package you didn&#x27;t know existed<p>My limited experience may well be the exception, but I&#x27;ll bring it up anyway. I wrote an RSS module in 2003. Someone else later added it to PyPI, the Python indexer. It has also been distributed by multiple packaging systems. I had no clue. No packager has ever said anything about it to me.<p>Looking now, it&#x27;s distributed by Gentoo, Debian, Slackware, Ubuntu, and more. It&#x27;s also used in PyMediaRSS2Gen, dilbert-rss, and loads more packages.<p>It took me two days to write that package, and another few days of maintenance in the 12 years. Until now I believed this hand-off mechanism, mediated by PyPI, was the way to go. Because <i>it would take me much longer to interact with all of those distributions than to write the code in the first place!</i><p>&gt;  Why not give some [doubt] to the packagers?<p>Because the statement you made earlier, &quot;They need to work with package maintainers, fixing (and not re-creating) problems that make packaging difficult. Anyone who can&#x27;t do that, or isn&#x27;t willing to, can&#x27;t claim to have &quot;learned all they can&quot; about software delivery, as I see in the first paragraph of the other Taskwarrior article posted today.&quot; gave no doubt to the developers.