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

Re: [pygame] ODE-ctpyes binding

To: pygame-users@xxxxxxxx
Subject: Re: [pygame] ODE-ctpyes binding
From: Matthias Baas <baas@xxxxxxxxxx>
Date: Fri, 14 Jul 2006 09:06:49 +0200
Delivered-to: archiver@seul.org
Delivered-to: pygame-users-outgoing@seul.org
Delivered-to: pygame-users@seul.org
Delivery-date: Fri, 14 Jul 2006 03:08:42 -0400
In-reply-to: <4e4a11f80607131802u2f25f5f8v7aabf20c73a16212@mail.gmail.com>
References: <4e4a11f80607120143v165d0e53ra93ec704616af1cd@mail.gmail.com> <be4fbf920607130919m85c3cb7n35919255a5860626@mail.gmail.com> <4e4a11f80607131802u2f25f5f8v7aabf20c73a16212@mail.gmail.com>
Reply-to: pygame-users@xxxxxxxx
Sender: owner-pygame-users@xxxxxxxx
User-agent: Thunderbird 1.5.0.4 (Windows/20060516)

Simon Wittber wrote:

What's wrong with PyODE?


Well, I found it doesn't cover the entire ODE API, and adding a
function means editing the pyrex source and recompiling. This also
means I need to maintain and distribute my own PyODE, which I would
rather not do.

Why would you have to maintain and distribute your own version? Why wouldn't you just make available your modification as patches so that they could be included in the official version? Or, if you're planning on doing more than just a few modifications, why don't you just ask for write access to the cvs repository? I'm sure you could get that... ;)

- Matthias -

Follow-Ups:
- Re: [pygame] ODE-ctpyes binding
  - From: Simon Wittber

References:
- [pygame] ODE-ctpyes binding
  - From: Simon Wittber
- Re: [pygame] ODE-ctpyes binding
  - From: Adam
- Re: [pygame] ODE-ctpyes binding
  - From: Simon Wittber

Prev by Author: [pygame] [RFC] clipboard support for various data types
Next by Author: Re: [pygame] pygame website - request for suggestions
Previous by thread: Re: [pygame] ODE-ctpyes binding
Next by thread: Re: [pygame] ODE-ctpyes binding
Index(es):
- Author
- Thread