<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[115938] trunk/dports/python</title>
</head>
<body>
<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; }
#msg dl a { font-weight: bold}
#msg dl a:link { color:#fc3; }
#msg dl a:active { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<dl class="meta">
<dt>Revision</dt> <dd><a href="https://trac.macports.org/changeset/115938">115938</a></dd>
<dt>Author</dt> <dd>stromnov@macports.org</dd>
<dt>Date</dt> <dd>2014-01-14 13:38:16 -0800 (Tue, 14 Jan 2014)</dd>
</dl>
<h3>Log Message</h3>
<pre>py-backports: new port</pre>
<h3>Added Paths</h3>
<ul>
<li>trunk/dports/python/py-backports/</li>
<li><a href="#trunkdportspythonpybackportsPortfile">trunk/dports/python/py-backports/Portfile</a></li>
<li>trunk/dports/python/py-backports/files/</li>
<li><a href="#trunkdportspythonpybackportsfiles__init__py">trunk/dports/python/py-backports/files/__init__.py</a></li>
<li><a href="#trunkdportspythonpybackportsfilessetuppy">trunk/dports/python/py-backports/files/setup.py</a></li>
</ul>
</div>
<div id="patch">
<h3>Diff</h3>
<a id="trunkdportspythonpybackportsPortfile"></a>
<div class="addfile"><h4>Added: trunk/dports/python/py-backports/Portfile (0 => 115938)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/dports/python/py-backports/Portfile (rev 0)
+++ trunk/dports/python/py-backports/Portfile 2014-01-14 21:38:16 UTC (rev 115938)
</span><span class="lines">@@ -0,0 +1,38 @@
</span><ins>+# -*- 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
+
+name py-backports
+version 1.0
+categories-append devel
+platforms darwin
+license Python
+supported_archs noarch
+
+python.versions 27 33
+
+maintainers stromnov openmaintainer
+
+description Namespace for backported Python features
+long_description ${description}
+
+homepage http://bitbucket.org/brandon/backports
+master_sites ${homepage}
+
+if {${name} ne ${subport}} {
+ distfiles
+
+ worksrcdir backports
+
+ post-extract {
+ file mkdir ${worksrcpath}
+ file copy ${portpath}/${filesdir}/setup.py ${worksrcpath}
+ file mkdir ${worksrcpath}/backports
+ file copy ${portpath}/${filesdir}/__init__.py ${worksrcpath}/backports
+
+ }
+}
+
+livecheck.type none
</ins><span class="cx">Property changes on: trunk/dports/python/py-backports/Portfile
</span><span class="cx">___________________________________________________________________
</span></span></pre></div>
<a id="svnkeywords"></a>
<div class="addfile"><h4>Added: svn:keywords</h4></div>
<a id="svneolstyle"></a>
<div class="addfile"><h4>Added: svn:eol-style</h4></div>
<a id="trunkdportspythonpybackportsfiles__init__py"></a>
<div class="addfile"><h4>Added: trunk/dports/python/py-backports/files/__init__.py (0 => 115938)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/dports/python/py-backports/files/__init__.py (rev 0)
+++ trunk/dports/python/py-backports/files/__init__.py 2014-01-14 21:38:16 UTC (rev 115938)
</span><span class="lines">@@ -0,0 +1,3 @@
</span><ins>+# This is a Python "namespace package" http://www.python.org/dev/peps/pep-0382/
+from pkgutil import extend_path
+__path__ = extend_path(__path__, __name__)
</ins></span></pre></div>
<a id="trunkdportspythonpybackportsfilessetuppy"></a>
<div class="addfile"><h4>Added: trunk/dports/python/py-backports/files/setup.py (0 => 115938)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/dports/python/py-backports/files/setup.py (rev 0)
+++ trunk/dports/python/py-backports/files/setup.py 2014-01-14 21:38:16 UTC (rev 115938)
</span><span class="lines">@@ -0,0 +1,105 @@
</span><ins>+# -*- coding: utf-8 -*-
+from distutils.core import setup
+setup(name='backports',
+ version='1.0',
+ description='Namespace for backported Python features',
+ long_description=u"""\
+A few minutes ago,
+my fingers were poised for a moment above the keyboard
+as I prepared to backport the essential ``match_hostname()`` function
+(without which the Secure Sockets Layer is not actually *secure!*)
+from the Python 3.2 version of the ``ssl`` Standard Library
+to earlier versions of Python.
+Suddenly, I paused: what would I call the new distribution
+that I created in the Package Index to hold this small function?
+
+It seemed a shame to consume an entire top-level name
+in the Package Index for what is, after all, a stopgap measure
+until older versions of Python are one day retired.
+
+And so I conceived this ``backports`` namespace package.
+It reserves a namespace beneath which we can happy place
+all of the various features that we want to cut-and-paste
+from later Python versions.
+I hope that this will provide two benefits:
+
+1. It should provide greater sanity, and a bit more organization,
+ in the Package Index.
+
+2. When you are ready to port a Python application
+ to a new version of Python,
+ you can search the code for any ``import`` statements
+ that name a ``backports`` package,
+ and remove the backports for features that have now “arrived”
+ in the version of Python to which you are upgrading.
+
+I have considered calling for all ``backports`` packages
+to issue a warning upon import if they detect that they are
+running under a version of Python that has now gained the feature
+they offer, but I think that will be unkind to actual users,
+since the most widespread versions of Python today still
+display warnings by default.
+
+Building your own backports module
+----------------------------------
+
+Placing a module of your own inside of the ``backports`` namespace
+requires only a few simple steps. First, set your project up like::
+
+ project/
+ project/setup.py
+ project/backports/
+ project/backports/__init__.py <--- SPECIAL - see below!
+ project/backports/yourpkg/
+ project/backports/yourpkg/__init__.py
+ project/backports/yourpkg/foo.py
+ project/backports/yourpkg/bar.py
+
+This places your own package inside of the ``backports`` namespace,
+so your package and its modules can be imported like this::
+
+ import backports.yourpkg
+ import backports.yourpkg.foo
+
+The one **absolutely essential rule** is that the ``__init__.py`` inside
+of the ``backports`` directory itself **must** have the following code
+as its content::
+
+ # A Python "namespace package" http://www.python.org/dev/peps/pep-0382/
+ # This always goes inside of a namespace package's __init__.py
+
+ from pkgutil import extend_path
+ __path__ = extend_path(__path__, __name__)
+
+If you fail to include this code, then the namespace package might fail
+to see all of the packages beneath it, and ``import`` statements might
+return errors.
+
+A live example of a package that implements all of this can be
+downloaded from the Python Package Index:
+
+http://pypi.python.org/pypi/backports.ssl_match_hostname/3.2a3
+
+What if the feature is present?
+-------------------------------
+
+An issue on which I am undecided is whether a ``backports`` package,
+if it finds itself on a modern enough version of Python,
+should simply import the “real” version of its feature
+from the Standard Library instead of offering the replacement.
+My guess is that this is *not* a good idea,
+because if — for some reason — an incompatibility crops up
+bewteen the tweaked code in a backport
+and the official code in the modern Standard Library,
+then it would be nice for developers using the backport
+to be faced with that breakage when they themselves
+try removing the backport,
+instead of being faced with it simply because a user
+tries running their program on more modern version of Python.
+
+""",
+ author='Brandon Craig Rhodes',
+ author_email='brandon@rhodesmill.org',
+ url='http://bitbucket.org/brandon/backports',
+ packages=['backports'],
+ )
</ins></span></pre>
</div>
</div>
</body>
</html>