<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
pymssql uses Cython and the FreeTDS C library to support connections
to Microsoft SQL Server. We would like to distribute binary
packages to ease installation for users. Our current build matrix
looks like this:<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/pymssql/pymssql/wiki/Build-Matrix">https://github.com/pymssql/pymssql/wiki/Build-Matrix</a><br>
<br>
However, we are trying to cut that down some since, by the time we
support 5 versions of python (2.6,2.7,3.2,3.3,3.4), we are having to
release 30 and now, since we are considering .msi files, maybe 40
files per release.<br>
<br>
I'm trying to figure out if there are any downsides to:<br>
<ul>
<li>replacing our .exe with .msi (lxml uses .exe, but we noticed
Python itself is shipping .msi files now)<br>
</li>
<li>only shipping wheels and no longer shipping eggs</li>
</ul>
<p>I would also appreciate any other thoughts regarding what kind of
binary formats a "responsible" package owner would ship.<br>
</p>
<p>Thanks.<br>
</p>
<div class="moz-signature"><br>
<b>Randy Syring</b><br>
<small>Chief Executive Developer</small><br>
<small>Direct: 502.276.0459<br>
Office: 812.285.8766</small><br>
<a href="https://www.level12.io/"><img alt="Level 12 Technologies"
title="www.level12.io"
src="cid:part1.03000107.03000606@level12.io" border="0"></a><br>
<i><small>Principled People | Technology that Works</small></i>
<br>
<br>
</div>
</body>
</html>