> I just see people doing it as if it was a mean to something and that's what eludes me (apart from, growing muscles to attract some girls, I get that).
If it helps put things into perspective - it's a rare person who wakes up and wishes that they were weaker than they were the day before. However, that's precisely what happens to you if you don't engage in resistance training; this is especially true the older one gets.
> I don't think anyone would seriously advocate using awk for complex projects these days,
Never underestimate the power of intellectual inertia, and the lengths people will go to in order to continue using their favorite tool - no matter how poorly suited to a task it might be. ):
> Why do you assume using Linux means you are training to be a programmer?
> Personally, I have installed Ubuntu Linux on friends' "old" laptops that have gotten "too slow" for Windows upgrades. Instead of being thrown out, these machines are still being used for common tasks such as internet browsing and e-mailing.
I'll vouch for this. My wife uses Xubuntu, and she's an accountant. There was a period of learning for her, but then again, part of that was due to the fact that one can automate just about anything via cron. (:
> has beta level support for loading CPython C extensions.
Is this via ctypes, or "real" support in much the same as how CPython would behave?
I ask because this is one of the features that I've been waiting (impatiently) for - I've run some Flask projects using PyPy and gunicorn, and love how fast it goes, but really want to be able to use the rest of my codebase, which unfortunately does rely on some C (and Cython) extensions. (:
It's "real" support, using your criteria. However, it's slower in PyPy than in CPython and than what the same thing based on ctypes would be on PyPy.
If there's a pure-Python version of the C extension, it might be faster on PyPy than the C extension support that cpyext (PyPy C-API compatibility module) provides.
Cython-based code is currently incompatible (it goes well beyond the public C-API), but a GSoC project to generate ctypes-based pure-Python code from Cython is (was?) going on.
> It's "real" support, using your criteria. However, it's slower in PyPy than in CPython and than what the same thing based on ctypes would be on PyPy.
> If there's a pure-Python version of the C extension, it might be faster on PyPy than the C extension support that cpyext (PyPy C-API compatibility module) provides.
That's fine, the mere ability to run them will be nice. (:
> Cython-based code is currently incompatible (it goes well beyond the public C-API), but a GSoC project to generate ctypes-based pure-Python code from Cython is (was?) going on.
I remember that GSoC! Any idea as to what happened to it, if it was scrapped, or whatever?
> I remember that GSoC! Any idea as to what happened to it,
> if it was scrapped, or whatever?
I know it made a lot of progress in Cython-land (updates at http://rguillebert.blogspot.com/) but no real overview or high level status update has been given yet (AFAIK). Since it's from GSoC 2011, it's about time for that to happen... and for other people to start contributing code <hint, hint> :).
Nice! I do remember having to install a crapload of packages in order to generate PDF docs, though if one uses a lot of software with Sphinx docs, it's more than worth it, IMHO.
If it helps put things into perspective - it's a rare person who wakes up and wishes that they were weaker than they were the day before. However, that's precisely what happens to you if you don't engage in resistance training; this is especially true the older one gets.