[Python-Dev] Python-2.3.2 windows binary screwed
Thomas Heller
theller at python.net
Wed Oct 15 11:11:37 EDT 2003
More information about the Python-Dev mailing list
Wed Oct 15 11:11:37 EDT 2003
- Previous message: [Python-Dev] Python-2.3.2 windows binary screwed
- Next message: [Python-Dev] Python-2.3.2 windows binary screwed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Anthony Baxter <anthony at interlink.com.au> writes: > [resend - my adsl fell over, don't think the original went out] > > I've put a note on the 2.3.2 page. Please email me when you've got a fixed > installer, and I'll do the magic to install it on creosote and gpg sign it. Before I'd like some questions to be answered, probably Martin or Tim have an opinion here (but others are also invited). First, I hope that it's ok to build the installer with the VC6 SP5 dlls. The other possibility that comes to mind is to not include *any* MS runtime dlls, and provide the MS package VCREDIST.EXE separately. Second, what about the filename / version number / build number? IMO one should be able to distinguish the new installer from the old one. The easiest thing would be to just change the filename into maybe Python-2.3.2.1.exe. Thomas
- Previous message: [Python-Dev] Python-2.3.2 windows binary screwed
- Next message: [Python-Dev] Python-2.3.2 windows binary screwed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list