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

Re: [pygame] Executable creation blues

Brian Fisher wrote:

Hey Jasper,
It does seem like an obscure and difficult problem, but at least it
seems to be one a lot of people are having :)


[snip]

Pretty straight forward really, as I'd already seen most of the excerpts you posted, and so had a good idea of what to expect. I appreciate the help though!

On 9/28/06 Jasper <rabidpoobear@xxxxxxxxx> wrote:

> I've had less trouble getting crossplatform C++ code to statically
> compile than I'm having sorting this out for just Windows.

Haha... everybody has their success stories :) If you've done a lot
statically compiling different crossplatform C++ code libraries on a
windows platform, I'd be suprised if you never had any problems with
STL and iostream inconsistencies, or different files fighting over
new... not to mention the garbage you'll get just changing visual
studio versions (if you ever do that).

I'll take python with it's buggy and imperfect code+interpreter
packaging over the alternatives anyday


Ok, ok! So I exaggerated a little bit. ;-) It helped that I worked at a company that specifically made crossplatform C++ libraries, and so it is true that I never had as much trouble on any single platform as I've had making Python .exe's. It's a bit of an unfair analogy though, as most of these platforms were commercial software, and static compiliation was a common use case -- quite different from Python.

You're right though, despite the trouble creating .exe's, I still prefer Python far more than the alternatives. I'll still bitch about it though, as it's taking way more time than I originally estimated!


Luke wrote:

I'm sensing some python-hatin' going on here ;)
Let me just point out that cpython is meant to be installed on the
target machine once, not redistributed.

you are right in that python is wonderful at building packages for
extension libs and all that, but I say designed shmesigned - what
matters is what is tested and what works. py2exe is actively
maintained, and as long as windows users are still out there trying to
get good solid packaging taken care of, all problems will be solved
for getting good windows distribution.

Agreed. This is largely why I'm surprised Python .exe creation isn't smoother. I'd love to help out with this, but I simply don't have the budget.


I'm not sure why you're having problems but your hunch that Numeric and
Numpy are conflicting sounds reasonable.
Why do you have both installed, by the way?

I think the better question would be why pygame has had (thankfully
optional) dependencies on a pacakge that hasn't been maintained for
years (namely numeric) for as long as it has... (hope I'm not being
rude here, but I do find the numeric dependency to lame to be worth
using the surfarray sndarray stuff)


Hear hear! Having only just started to move to numpy myself, I can see why it's not been done, but it really should be done. Perhaps I'll take a look at it after I convert my own code to use numpy, but that's not exactly a pressing need as Numeric still works fine.

-Jasper