PyPy is a fast, compliant alternative implementation of the Python language
(2.7.1). It has several advantages and distinct features:
- Speed: thanks to its Just-in-Time compiler, Python programs often run faster
on PyPy.
- Memory usage: large, memory-hungry Python programs might end up taking less
space than they do in CPython.
- Compatibility: PyPy is highly compatible with existing python code. It
supports ctypes and can run popular python libraries like
twisted and django.
- Sandboxing: PyPy provides the ability to run untrusted code in a fully
secure way.
- Stackless: PyPy can be configured to run in stackless mode, providing
micro-threads for massive concurrency.
- As well as other features.
WWW: http://pypy.org/
===> The following configuration options are available for pypy3-2.4.0:
====> Options available for the group PYINST
SANDBOX=off: Translate a sandboxed pypy
===> Use 'make config' to modify these settings
lang/pypy3: update to 5.2.0-alpha1
Changes to lang/pypy3:
- "Rename" from pypy3-devel (functionaly it is a rename, technically pypy3
is a new port and pypy3-devel is deleted).
- Make lang/pypy3 a slave port of lang/pypy
Changes to lang/pypy:
- Use DISTVERSION instead of PORTVERSION (lang/pypy3 is not
PORTVERSION clean)
- Change PYPY_CFFI_VER to include the 'pypy-' prefix (lang/pypy3 has
'pypy3-' as a prefix)
- Only make PYPY_MINMEM the default is ${LOCALBASE}/lang/pypy exists
- Fix build depends for PYPY_MINMEM
- Allow slave port to have custom patch directory
(Only the first 15 lines of the commit message are shown above )
Update lang/pypy3-devel to 2.4.0.
Changes:
* Carry across _sqlite.py fix from lang/pypy
* Strip cffi shared libraries (from lang/pypy)
Change Log:
- Various fsencode PEP 383 related fixes to the posix module (readlink, uname,
ttyname and ctermid) and improved locale handling
- Fixed a couple different crashes related to parsing Python 3 source code
- internal refactoring in string and GIL handling which led to significant
speedups
- improved handling of multiple objects (like sockets) in long-running
programs. They are collected and released more efficiently, reducing memory
use. In simpler terms - we closed what looked like a memory leak
Update my ports to be compliant with new USES framework and fix other issues.
Changes:
* various: migrate USE_BZIP2 to USES=tar:bzip2
* various: migrate USE_XZ to USES=tar:xz
* multimedia/py-ffmpeg: add and prefer github (GH) as master site
* ports-mgmt/portbuilder: specify license as BSD2CLAUSE (instead of just BSD)
Most ports are updated infrequently so a single batch commit is preferred over
collating changes per port.
Add stage support to lang/pypy, lang/pypy-devel and lang/pypy3-devel.
Also, require a modern compiler that can handle c11. Although this is
not strictly required (just about any C compiler would do) the base GCC
compiler has a memory bug and thus cannot reasonably compile the ports.
Fix the pypy ports.
Be more aggresive in cleaning up temporary directories that pypy leaves
behind in the copied directories (files and directories in __pycache__).
Only .so and .pyc should be left behind in those __pycache__ directories
and no subdirectories.
Also remove the manual requirement for building lang/pypy. Redports
successfully built lang/pypy3-devel (with leftovers) in 19 hours.
Reported by: Redports
Introducing lang/pypy3-devel version 2.1.b1.
Highlights
- The first release of PyPy3: support for Python 3, targetting CPython 3.2.3!
- There are some known issues including performance regressions (issues
#1540 & #1541) slated to be resolved before the final release.
