RetroSearch Browse

Wed Oct 15 12:07:41 EDT 2003 · https://mail.python.org/pipermail/python-dev/2003-October/038757.html

> The other possibility that comes to mind is to not include *any* MS
> runtime dlls, and provide the MS package VCREDIST.EXE separately.

This sounds like a bad idea; all previous installers have included the
right DLLs and not gotten any problems.

> 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.

I can't think of anything better, so I think it's okay.  Adding a
letter would be confusing because normally suffixes like b2 or c1 come
*before* the final version.

Sigh indeed. :-(

--Guido van Rossum (home page: http://www.python.org/~guido/)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2003-October/038757.html below:

[Python-Dev] Python-2.3.2 windows binary screwed