On 14 October 2012 02:01, Roman Shaposhnik <[email protected]> wrote: > On Sat, Oct 13, 2012 at 5:48 PM, Bruno Mahé <[email protected]> wrote: > > I wouldn't blame the language for your experience, > > I actually don't blame the language -- this is precisely why I said > that I blame Python as a platform for not making it easier for me to > manage the dendencies. > > > I would blame the script. > > If anything requires me to almost build dependencies out of trunk (or > > requires versions < 6months old), the issue doesn't lie with the language > > but with the script. > > You probably would have not been happy either with something written in > > clojure and requiring the latest jdk7 and latest gradle. > > I actually view it differently -- like I said -- I had no issue with > installing python3 environment, but I still got bitten by the script > requiring extra libraries and Python (as an environement) making > it next to impossible for me to install those extra dependencies > locally AND not providing a way for a script author to package > it all together. >
I see your point: anything that hits the OS-layer dependency manager can cause problems; even JSON handling in python on the mac meant I had to "brew install simplejson"; there's less consistency in a python installation than there is in a JDK > > All of the above is subjective, of course, and hence my honest > question: if you guys know of some magic python incantation > that would allow: > 1. fat-jars type of python distribution of scripts > 2. maven-like dendency management > 3. maven-like artifact control > I'd love to hear it. > > Thanks, > Roman. > Not convinced that M2-esque dependency management is what you want in production, where the ops team may need to push out an emergency release of something. What RPMs & debs do bring the table is the ability to review, roll or revert every use of an artifact in a system. That may not be what the apps want (DLL-hell anyone?), but there's no good answer here. The one thing neither CS nor Software engineering has ever solved is versioning, > > P.S. I was attending Puppet conf a couple of weeks ago > and got to a presentation on Logstash -- turns out it is written > in Ruby, but they got so sick of managing Ruby dependencies > that they are not running on top of JRuby fat-jar style: > http://logstash.net/ > and click on download ;-) > yea, I've seen puppet rpm resolution problems.
