[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[pygame] Python, Pygame and Performance
- To: pygame-users@seul.org
- Subject: [pygame] Python, Pygame and Performance
- From: Jacob Schwartz <kevlarx@netidea.com>
- Date: Fri, 21 May 2004 17:48:12 -0700
- Delivered-to: archiver@seul.org
- Delivered-to: pygame-users-outgoing@seul.org
- Delivered-to: pygame-users@seul.org
- Delivery-date: Fri, 21 May 2004 20:47:46 -0400
- Reply-to: pygame-users@seul.org
- Sender: owner-pygame-users@seul.org
- User-agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007
Hello,
This is my first post on this mailing list, so please forgive my
countless errors :)
I am fairly new to programming in python (only a few months) and so far
have loved it. A _lot_.
Now here is my dilemma, whenever I talk about writing code in python
(especially game related things) people always seem to come back with
the same response 'its too slow!' ... or laugh off its feasibility.
I know that python is not an ideal language to write a full fledged game
in (it is more of a glue language after all), but lately I have been
spending a lot of time on a mini game project and the results have been
impressive.
I have written similar programs previously in C++, using DirectX (via my
own low level wrappers) and the performance of that was at most - only
slighter better then using pygame.
- But I didn't have the safety of python, the clean list semantics, and
rapid pace of development on my side. All major advantages that come
from using pygame.
I don't believe I'm alone in noticing this illogical dislike for
python/pygame.
Has anyone else experienced this?
Any tips on what to do about it (besides hitting the nay-sayer with a
stick)?
Would anyone be interested in writing an article, or some benchmarks to
actually give some *solid* evidence we could direct people to when the
'pygame's too slow' argument comes up?
Python advocacy is harder then it looks! :)
- Jacob