[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] MSVCR71.dll

To: <pygame-users@xxxxxxxx>
Subject: Re: [pygame] MSVCR71.dll
From: Brian Fisher <brian_fisher@xxxxxxx>
Date: Sun, 28 Aug 2005 12:44:15 -0700
Delivered-to: archiver@seul.org
Delivered-to: pygame-users-outgoing@seul.org
Delivered-to: pygame-users@seul.org
Delivery-date: Sun, 28 Aug 2005 15:45:00 -0400
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx
Z-usanet-msgid: XID235JHbTSP0050X30

------ Original Message ------
From: andrew baker <failrate@xxxxxxxxx>
> This is a known issue with all py2exe/pygame2exe distributions with
> Python 2.4.  For this reason, I am boycotting 2.4 and dependant
> modules until it's made free of this burdensome yoke.
> 
> I hope that didn't sound too melodramatic, but I'm really salty about
> how the issue affects distribution.
> 
I agree. I know the whole msvcr71.dll is discussed ad naseum on other forums,
but I don't plan on using pygame over python 2.4 for similar reasons. I
actually have a licensed copy of .NET 2003, but I don't want to deal with
having my EULA right to satisfy the redistribution requirements or to even
have to add the file size of the dll.

Follow-Ups:
- Re: [pygame] MSVCR71.dll
  - From: andrew baker

Prev by Author: Re: [pygame] Desperate for a Mac OS Xer
Next by Author: Re: [pygame] Re: PyWeek release of LGT
Previous by thread: Re: [pygame] MSVCR71.dll
Next by thread: Re: [pygame] MSVCR71.dll
Index(es):
- Author
- Thread