| I'm sorry, it is most certainly NOT "FUD". I have an Intel(R) Xeon(R) CPU W3540 @ 2.93GHz workstation with two 500GB drives and 12GB of memory. The last time I ran the build process, it took hours while PyPy drew pretty pictures on the screen in ascii: https://twitter.com/erikjanss/status/112867649666564096 All I did was run the standard build target following the documentation provided. My understanding is that while it's busy drawing pretty ascii art (which I have no problem with, by the way) it's building PyPy from the RPython source, which according to other users as recently as December of 2012 "takes ages": https://groups.google.com/forum/#!msg/julia-dev/4TeGQh8wbmI/... Hence why I asked if this had been improved yet. I'm not trolling, or spreading FUD. I'm asking if a significantly negative experience I had has been improved. |