> > 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 don't understand the relevance of this comment. > 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. (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. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4