Additional PLIST fixes.
Changes in 1.4:
An interesting new optimization: instances of user-defined classes
are now really supported, i.e. their attributes keep type information
and are stored quite compactly in memory. However, it only works
so far with instances of a new type ``psyco.compact`` (which is
subclassable). The line ``from psyco.classes import *`` has the
effect of turning your classes into psyco.compact subclasses, too.
Changes in 1.3:
Includes support for Python 2.4 (and of course still for 2.1-2.3).
As always comes with a few bug fixes, including a memory leak when
using the profiler. Another good news is that the built-in functions
that read the local variables -- locals(), eval(), execfile(),
vars(), dir(), input() -- now work correctly!
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
from the pkgsrc-wip pkg by Michal Pasternak
Psyco is a specializing compiler. In a few words let us first see:
What you can do with it
In short: run your existing Python software much faster, with no change in
your source.
Think of Psyco as a kind of just-in-time (JIT) compiler, a little bit like
Java's, that emit machine code on the fly instead of interpreting your Python
program step by step. The result is that your unmodified Python programs run
faster.
Benefits
2x to 100x speed-ups, typically 4x, with an unmodified Python interpreter and
unmodified source code, just a dynamically loadable C extension module.
Drawbacks
Psyco currently uses quite a lot of memory. It only runs on Intel
386-compatible processors (under any OS) right now. There are some subtle
semantic differences (i.e. bugs) with the way Python works; they should not be
apparent in most programs.
