> > > > 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. > > > > 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. This is correct. I do release PyChecker as a .tar.gz which contains a setup.py, but no PKG-INFO. Should there be one? I don't use setup.py to create the .tar.gz. I've never found the proper way to make releases when I looked. But that was a long time ago. Neal
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