2 ms·
(With apologies to those who've heard it before) the solution is to model the domain (of packaging/distribution) using Python itself and provide a simple Python
by carapace 4y ago
(With apologies to those who've heard it before) the solution is to model the domain (of packaging/distribution) using Python itself and provide a simple Pythonic API for it, like what pathlib does for filesystems.
- zbentley 4y agoI think that's not the problem. Modelling isn't the issue. Half of these tools have good, usable ways of making an API for development and packaging. The issue is that they all make slightly different decisions. "Just make a domain model" falls apart when it encounters users with different subjective preferences or objective requirements--to say nothing of vastly different skill levels, which the article touches on.
- carapace 4y agoHmm, if that's the case then I'm not sure there's a good solution. The situation reminds me of the old web frameworks situation ("Python, the language with more web frameworks than keywords." har har) which was resolved when BDFL blessed Django.