[96380] trunk/dports/python/py-greenlet/Portfile

stromnov at macports.org stromnov at macports.org
Wed Aug 8 03:02:10 PDT 2012


Revision: 96380
          https://trac.macports.org/changeset/96380
Author:   stromnov at macports.org
Date:     2012-08-08 03:02:06 -0700 (Wed, 08 Aug 2012)
Log Message:
-----------
py-greenlet: fix whitespaces

Modified Paths:
--------------
    trunk/dports/python/py-greenlet/Portfile

Modified: trunk/dports/python/py-greenlet/Portfile
===================================================================
--- trunk/dports/python/py-greenlet/Portfile	2012-08-08 09:01:35 UTC (rev 96379)
+++ trunk/dports/python/py-greenlet/Portfile	2012-08-08 10:02:06 UTC (rev 96380)
@@ -1,50 +1,58 @@
 # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
 # $Id$
 
-PortSystem 1.0
-PortGroup python 1.0
+PortSystem          1.0
+PortGroup           python 1.0
 
-name                    py-greenlet
-version                 0.3.4
-python.versions         24 25 26 27 31 32
-python.default_version  24
-categories-append       devel
-license                 MIT
-platforms               darwin
-maintainers             nomaintainer
-description             Lightweight in-process concurrent programming
-long_description        The \"greenlet\" package is a spin-off of \
-                        Stackless, a version of CPython that supports \
-                        micro-threads called \"tasklets\". Tasklets run \
-                        pseudo-concurrently (typically in a single or \
-                        a few OS-level threads) and are synchronized \
-                        with data exchanges on \"channels\". \
-                        \
-                        A \"greenlet\", on the other hand, is a still \
-                        more primitive notion of micro-thread with no \
-                        implicit scheduling\; coroutines, in other \
-                        words. This is useful when you want to control \
-                        exactly when your code runs. You can build \
-                        custom scheduled micro-threads on top of \
-                        greenlet\; however, it seems that greenlets are \
-                        useful on their own as a way to make advanced \
-                        control flow structures. For example, we can \
-                        recreate generators\; the difference with \
-                        Python's own generators is that our generators \
-                        can call nested functions and the nested \
-                        functions can yield values too. Additionally, \
-                        you don't need a \"yield\" keyword. See the \
-                        example in test_generator.py. \
-                        \
-                        Greenlets are provided as a C extension module \
-                        for the regular unmodified interpreter.
+name                py-greenlet
+version             0.3.4
+revision            0
+categories-append   devel
+license             MIT
+platforms           darwin
 
-homepage                http://undefined.org/python/#greenlet
-master_sites            http://pypi.python.org/packages/source/g/greenlet/
-distname                greenlet-${version}
-use_zip                 yes
-checksums               rmd160  0a866b8e70e43a4f0ac88a57503ceb4d0905bb4a \
-                        sha256  259ed0f34de9b0c948f42bdaffe378ea53d210d38377c6dcb0c6b728fccad1b0
+maintainers         nomaintainer
+
+description         Lightweight in-process concurrent programming
+
+long_description    The \"greenlet\" package is a spin-off of \
+                    Stackless, a version of CPython that supports \
+                    micro-threads called \"tasklets\". Tasklets run \
+                    pseudo-concurrently (typically in a single or \
+                    a few OS-level threads) and are synchronized \
+                    with data exchanges on \"channels\". \
+                    \
+                    A \"greenlet\", on the other hand, is a still \
+                    more primitive notion of micro-thread with no \
+                    implicit scheduling\; coroutines, in other \
+                    words. This is useful when you want to control \
+                    exactly when your code runs. You can build \
+                    custom scheduled micro-threads on top of \
+                    greenlet\; however, it seems that greenlets are \
+                    useful on their own as a way to make advanced \
+                    control flow structures. For example, we can \
+                    recreate generators\; the difference with \
+                    Python's own generators is that our generators \
+                    can call nested functions and the nested \
+                    functions can yield values too. Additionally, \
+                    you don't need a \"yield\" keyword. See the \
+                    example in test_generator.py. \
+                    \
+                    Greenlets are provided as a C extension module \
+                    for the regular unmodified interpreter.
+
+homepage            http://undefined.org/python/#greenlet
+master_sites        http://pypi.python.org/packages/source/g/greenlet/
+
+distname            greenlet-${version}
+use_zip             yes
+
+checksums           rmd160  0a866b8e70e43a4f0ac88a57503ceb4d0905bb4a \
+                    sha256  259ed0f34de9b0c948f42bdaffe378ea53d210d38377c6dcb0c6b728fccad1b0
+
+python.default_version  27
+python.versions     24 25 26 27 31 32
+
 if {$name != $subport} {
     depends_lib-append  port:py${python.version}-distribute
 }
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20120808/2801566a/attachment.html>


More information about the macports-changes mailing list