[Python-Dev] Killing off bdist_dumb

[Thomas Heller]

Jp Calderone <exarkun@meson.dyndns.org> writes:

> On Thu, Nov 14, 2002 at 09:00:44AM -0500, Guido van Rossum wrote:
> > [ Who wrote this? ]
That was me.
> > > [snip]
> > >   
> > > bdist_wininst installers *can* also be created on other systems
> > > as long as they only contain pure Python code - although I've never
> > > heard of someone actually doing this.
> > [snip]
> 
>   FWIW, I do this with just about every release I make (and I'm a bit
> surprised to hear that this isn't a common thing).  While I do have a
> Windows machine I *could* build releases on (with cygwin though, not MSVC),
> my release process is mostly automated, and runs on a Linux box.  I don't
> think the thread is headed in this direction, but just in case, *please*
> don't break this feature :)
> 
Great, but the binary doesn't show on which system it was created.

I have more the impression, that people release .tar.gz files
containing a distutils setup.py script, but no PKG-INFO, so the
tarball isn't created by distutils sdist command. PyChecker is such an
example, IIRC.

Question for python-dev (Tim?): how would wininst.exe now find it's way
into the Python source distribution, or in Linux binary distributions?

Thomas