4 ms·
Well, there are languages better at incorporating the Zen of Python than Python itself, vide (full disclosure: my blog post) https://p.migdal.pl/blog/2020/03/ty
by stared 3y ago
Well, there are languages better at incorporating the Zen of Python than Python itself, vide (full disclosure: my blog post) https://p.migdal.pl/blog/2020/03/types-test-typescript/ https://p.migdal.pl/blog/2020/03/types-test-typescript/.
When it comes to package managers, as you noted, the situation is even more ironic, as nicely depicted in https://xkcd.com/1987/ https://xkcd.com/1987/.
- surfingdino 3y agoWhat's your view on how Golang deals with this problem? Serious question.
- zadokshi 3y agoGolang users don’t sit around arguing about package managers, nor do they have trouble with trying to make sure they have the right version of go installed. Early versions of go didn’t solve things well, but go has had this fixed for a long time now. Any arguments about packaging issues are likely related to older out of date problems people had. The only real problem people have these days is around private non open source packages. You can do it, but you need to learn how to set environment variables.
- mixmastamyk 3y agoOne way to do things becomes impossible to after thirty years unless one wants to make large, breaking changes. After Python 3: >>> from __future__ import braces File "<stdin>", line 1 SyntaxError: not a chance
- lijok 3y agoHaha, didn't know about this easter egg, amazing
- endgame 3y agoThat's been around since at least Python 2.6, and I think I remember seeing it before then: $ LC_ALL=C NIX_PATH=nixpkgs=https://github.com/NixOS/nixpkgs/archive/release-13.10.tar.gz nix-shell -p python26 --run 'python -c "from __future__ import braces"' File "<string>", line 1 SyntaxError: not a chance
- mixmastamyk 3y ago“After Python 3” doesn’t mean it arrived then. It was supposed to be read, “after Python three … not a chance.”