6 ms·
For a language that prides itself on simplicity, this seems really painful...
by girvo 13y ago
For a language that prides itself on simplicity, this seems really painful...
- pak 13y agoYes, it is. Coming to this mess from the joy of bundler/gems, npm, or hell, even CPAN will ruin your afternoon. It is just an unfortunate circumstance of the community not efficiently converging on well designed standards quickly enough, and so, the rocky soil has sprouted strange twisty crops. There are articles on how the setuptools/distutils frankenhack pretty much set off the whole trainwreck that you see today, e.g.: http://blog.startifact.com/posts/older/a-history-of-python-packaging.html http://blog.startifact.com/posts/older/a-history-of-python-p... Armin (the OP) has also written about this sad history previously: http://lucumr.pocoo.org/2012/6/22/hate-hate-hate-everywhere/ http://lucumr.pocoo.org/2012/6/22/hate-hate-hate-everywhere/
- mixmastamyk 13y agoWould be nice if there were one packaging tool all those languages were using instead of each one reinventing it.
- rmc 13y agoSomething that integrated into your operating system distribution perhaps....
- mh- 13y agoaptly put. you might be onto something.
- Debilski 13y agoAn OS solution which allowed for versioned packages to be installed on a per-project base. That’d be something…
- the_mitsuhiko 13y agoUnfortunately most linux systems do not support multi-version installs or installs local to a user or path.
- muraiki 13y agoThis comes very close: http://nixos.org/nixos/ http://nixos.org/nixos/
- singingfish 13y ago> or even CPAN ? Cpan, particularly cpanminus is excellent.
- flavor8 13y agoAlso maven. It may require an XML manifest, but it's robust, easy to use, and has come to be a solid standard. Python may be a (mostly) nice language, but the infrastructure and tooling badly lags the Java world.
- gbog 13y agoYou know that simplicity of use is very complex to achieve, and requires complex tools behind, right? Actually it is even true for music instruments: A piano is very complex inside and can be played relatively easily, while a violin is much more simple in the fabric but much harder to play.
- 1stop 13y agoJust go and copy bundler or even npm. This is a solved problem with a really bad case of "Not-Invented-here" in the python community. What's funny is I'm pretty sure gems/bundler and npm/packages were heavily influenced by pythons plethora of crappy attempts (eggs, distutils...etc) at package management.
- camus2 13y agogiven how npm "scales" i would not say they solved the problem,and npm lacks of namespaces. Why cant I name my package the way I want ?
- 1stop 13y agoAs oppose to python "name it whatever you like because no one will ever find it" naming convention? Every solution has drawbacks, but python's solution has almost every drawback.
- acdha 13y ago> Just go and copy bundler or even npm. Anyone who's worked with all three of those would tell you that this isn't yet a “rest on your laurels” situation.
- 1stop 13y agoI've worked with all three (if I count pythons ~4 as 1). There are improvements to be made to all of them but gosh python is a complete mess in this regard.
- coldtea 13y ago
- Too 13y agoIt is like a farce on the "there shall only be one way to do it" mantra. Not to mention that some of the package managers has to be installed through one of the other packet manager, creating a very long dependency chain if you want to install a package through the former.
- Rapidwire 13y agoNo, the mantra is actually "There should be one-- and preferably only one --obvious way to do it." And yes, one usually installs easy_install to install pip, but I don't see how that can create a "very long dependency chain". Even when both tools are installed, you can use either to install packages.
- mmcnickle 13y agoPython 3.4 will have a pip installer bundled with it, which removes the easy_install pip farce.
- donaldstufft 13y agoThe recommended way to install pip has not been via easy_install for awhile. Generally we recommend using the ``get-pip.py`` script. Which with recent versions will also install setuptools for you.
- pak 13y agoThe more that I use Python in the context of other languages, the more the "there should only be one [obvious] way to do it" mantra irks me. First of all, there's the cases in which reality fails to live up to expectations, like this packaging debacle. If there was an obvious and best way to do everything, we wouldn't need to spend so much money and time engineering software. We wouldn't spend so much time arguing about distributed vs. centralized, OOP vs. declarative vs. functional, type systems, build/test systems, etc. The mantra is arrogant on its face. Secondly, it flies in the face of innovation. It works against building a creative community of users. So often, when Python users point out the holes in the ecosystem, they are simply told "well the long and outdated PEP 5991834 already establishes the obvious way to do it" or "just shim it on top of this inadequate corner of the standard lib" or the use case itself is questioned, which patronizes the criticizer. The mantra becomes an excuse for reinforcing a hive mind philosophy. In this case, I wonder if it has subtly undermined the development of a diverse and widely supported package index. The whole point of such a package system is to support the belief that there are actually many ways to do the same thing, and some may be better for certain styles/teams/circumstances. Having the opposite outlook as a design principle for a language will attract users less inclined to contribute to or build such a diverse packaging system. I wonder this particularly because the more "laissez-faire" languages like Perl, Ruby, and JavaScript are precisely the ones that have such great packaging systems and ecosystems.
- sdegutis 13y agoManaging dependencies correctly is probably the most important long-term problem to solve in programming, but for some reason it always seems to be given a low priority by language authors and communities, until one day it's become a tangled mess that isn't logistically possible to get out of. I don't get it, and it's frustrating.[1] [1]: Somehow, all my lines aligned perfectly in this comment box at its default size! https://www.dropbox.com/s/slq8x0rqkj7ydzn/aligned.png https://www.dropbox.com/s/slq8x0rqkj7ydzn/aligned.png
- ithkuil 13y agoManaging dependencies correctly is probably the most important long-term problem to solve in programming ... and naming things
- 7952 13y agoIt is interesting to think of this in terms of basic computer science problems. A package is a cache of the developers master version which need to be invalidated. It has to be named in such a way that you can decide if it is the correct version. And sometimes it needs to be handled in a transactional way so that you have a view of the data that is consistent. Put like that the reliable solution would be a locally replicated SQL database. Perhaps the PostgreSQL or SQLite would be a better target for development than the underlying OS?
- donaldstufft 13y agoA great deal of the pain that Armin experienced is mostly due to the fact that Wheels are very new and aren't very polished yet. Additionally there is a vast wealth of technical debt in the packaging tools so it's quite easy to introduce these kinds of problems because of the general architecture (Something that we're trying to fix long term!).
- rm445 13y agoIs there any reason to believe wheels will ever become polished, or might they simply be replaced with the next idea that comes along? Apologies for acting the cynic, but this is the kind of uncertainty that comes when there is constant reinvention, instead of improvement of existing tools.