GSOC?<br><br><div class="gmail_quote">On Thu, Mar 26, 2009 at 6:05 AM, Steven Bethard <span dir="ltr"><<a href="mailto:steven.bethard@gmail.com">steven.bethard@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, Mar 25, 2009 at 7:08 AM, Paul Moore <<a href="mailto:p.f.moore@gmail.com">p.f.moore@gmail.com</a>> wrote:<br>
> I use Python for systems admin scripts, Windows services, and database<br>
> management. In my experience (and I agree, it's only one, limited, use<br>
> case) availability of download-and-run bdist_wininst installers for<br>
> every package I used was the only significant requirement I had for<br>
> Python package distribution (I remember pre-distutils days, when being<br>
> able to install a 3rd party package on Windows was a nightmare of<br>
> build-it-yourself guesswork).<br>
><br>
> Since setuptools came on the scene, I can state with some certainty<br>
> that many packages which would otherwise have been distributed as<br>
> bdist_wininst installers, now aren't. In some cases, only source<br>
> packages are provided (on the basis that easy_install will build what<br>
> you need). In those cases, I can accept that maybe the developer would<br>
> not have built Windows installers even before setuptools arrived. But<br>
> in a significant number of cases - including setuptools itself!!!! -<br>
> binary, version-specific eggs for Windows are provided, but no<br>
> bdist_wininst installers. If the developer is willing to build an egg,<br>
> he could just as easily have built an installer - but he now has to<br>
> choose - build one or the other, or both. And not everyone chooses the<br>
> same way.<br>
<br>
</div>I'd just like to chime in and agree with Paul here. I'm a Windows<br>
user, and I won't install a Python module that I can't get as a<br>
wininst (or preferably a .msi), because I prefer to use the Windows<br>
package management system, not some Python specific thing. I can<br>
generally build installers myself for Python-only packages, but binary<br>
ones are harder. And I've seen several projects with exactly the kind<br>
of thing Paul describes - where a good Windows installer would<br>
probably have been available if it weren't for the interference of<br>
setuptools.<br>
<br>
Steve<br>
<font color="#888888">--<br>
I'm not *in*-sane. Indeed, I am so far *out* of sane that you appear a<br>
tiny blip on the distant coast of sanity.<br>
--- Bucky Katt, Get Fuzzy<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-dev" target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/tleeuwenburg%40gmail.com" target="_blank">http://mail.python.org/mailman/options/python-dev/tleeuwenburg%40gmail.com</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>--------------------------------------------------<br>Tennessee Leeuwenburg<br><a href="http://myownhat.blogspot.com/">http://myownhat.blogspot.com/</a><br>"Don't believe everything you think"<br>