| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight
Notes:
svn path=/head/; revision=472884
|
| |
|
|
|
|
|
| |
With hat: portmgr
Notes:
svn path=/head/; revision=469459
|
| |
|
|
| |
Notes:
svn path=/head/; revision=469458
|
| |
|
|
|
|
|
|
|
|
| |
* add Python3 support
PR: 228096
Submitted by: maintainer
Notes:
svn path=/head/; revision=469457
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
current python flavor. It can be used in dependency lines when the
port itself is not python flavored. For example, deskutils/calibre.
By default, all the flavors are generated. To only generate flavors
for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
In all the ports with Python dependencies, the *_DEPENDS entries MUST
end with the flavor so that the framework knows which to build/use.
This is done by appending '@${PY_FLAVOR}' after the origin (or
@${FLAVOR} if in a Python module with Python flavors, as the content
will be the same). For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
PR: 223071
Reviewed by: portmgr, python
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D12464
Notes:
svn path=/head/; revision=455210
|
|
|
The traitsui project contains a toolkit-independent GUI abstraction
layer, which is used to support the "visualization" features of the
Traits package. Thus, you can write code in terms of the Traits
API (views, items, editors, etc.), and let traitsui and your selected
toolkit and back-end take care of the details of displaying them.
The following GUI backends are supported:
* wxPython
* PyQt
* PySide
WWW: https://docs.enthought.com/traitsui
PR: 204433
Submitted by: Vladimir Chukharev <vladimir.chukharev@gmail.com>
Notes:
svn path=/head/; revision=419645
|
