[Python-Dev] Killing off bdist_dumb (original) (raw)
Thomas Heller theller@python.net
14 Nov 2002 20:55:45 +0100
- Previous message: [Python-Dev] Killing off bdist_dumb
- Next message: [Python-Dev] Killing off bdist_dumb
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Jp Calderone, about creating binary windows installers with distutils on non-windows systems]
> > 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 :) [me] > Great, but the binary doesn't show on which system it was created. [Guido] I don't understand the relevance of this comment. I don't either ;-) It was sent out too early. I simply meant that I didn't know that people actually were creating those bdist_wininst packages on Linux.
> 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.
Ouch, I didn't know this! (Or I'd forgotten. :-) It's well documented fortunately. This is what I don't understand.
(And the docs remind me that it would be neat if Python had a tarfile module.)
> Question for python-dev (Tim?): how would wininst.exe now find it's way > into the Python source distribution, or in Linux binary distributions? I don't understand the question, and I doubt that Tim does either.
I have seen that you entered the request to move the bdist_wininst sources into the Python tree. We can solve this problem later, I think.
Thanks,
Thomas
- Previous message: [Python-Dev] Killing off bdist_dumb
- Next message: [Python-Dev] Killing off bdist_dumb
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]