Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion PythonOgre Development

Received: by 10.223.108.201 with SMTP id g9mr394932fap.25.1282106057847;
        Tue, 17 Aug 2010 21:34:17 -0700 (PDT)
X-BeenThere: python-ogre-developers@googlegroups.com
Received: by 10.223.26.6 with SMTP id b6ls48320fac.1.p; Tue, 17 Aug 2010
 21:34:17 -0700 (PDT)
Received: by 10.223.108.70 with SMTP id e6mr428202fap.4.1282106057308;
        Tue, 17 Aug 2010 21:34:17 -0700 (PDT)
Received: by 10.223.108.70 with SMTP id e6mr428201fap.4.1282106057269;
        Tue, 17 Aug 2010 21:34:17 -0700 (PDT)
Return-Path: <nzmill...@gmail.com>
Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com [209.85.161.46])
        by gmr-mx.google.com with ESMTP id b20si2262716fak.3.2010.08.17.21.34.16;
        Tue, 17 Aug 2010 21:34:16 -0700 (PDT)
Received-SPF: pass (google.com: domain of nzmill...@gmail.com designates 209.85.161.46 as permitted sender) client-ip=209.85.161.46;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nzmill...@gmail.com designates 209.85.161.46 as permitted sender) smtp.mail=nzmill...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by fxm13 with SMTP id 13so49321fxm.5
        for <python-ogre-developers@googlegroups.com>; Tue, 17 Aug 2010 21:34:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:received:date:message-id
         :subject:from:to:content-type;
        bh=fxvGP7CpILd7maGyeJLgyS2TX43CTW2mj/DKTrGT73o=;
        b=YQWZLhh7iCRZ9a9IMbnVvvacOF2kqd1xJ3P9dSFLs0HOngh05g2yciAtvMnIMic0yd
         OP6GEV8wje+Z4LonGmKhXDlLTueDIicdY5xjyylBDtPzzC5s/2GexQFNX+tBd8JqX7yW
         NHWB2yL5OjG7deU5H0iQ7XanMn/b1V0/jnrxA=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=bnj60y3Dg23t+xGONDqgxx0+9xR94HxvQATC8kNPCw2Un4yEjZA6niidoDOIgT0Emt
         04xjXc+tqbx23KRt8w2E+vAzyNvV1i/fHUmyRk1iA7WJXJr5Fuu4BgUHW94/rQN+NpCp
         HU1aMEfGddmy+UtxyAi9EHf0aSbVAiSSJCh7k=
MIME-Version: 1.0
Received: by 10.239.142.194 with SMTP id h2mr359026hba.95.1282106056101; Tue,
 17 Aug 2010 21:34:16 -0700 (PDT)
Received: by 10.239.183.77 with HTTP; Tue, 17 Aug 2010 21:34:16 -0700 (PDT)
Date: Wed, 18 Aug 2010 12:34:16 +0800
Message-ID: <AANLkTik196tnYhQRrhObNgtpjrEVRSkY8qiuJJ7wT...@mail.gmail.com>
Subject: PythonOgre Development
From: Andy Miller <nzmill...@gmail.com>
To: python-ogre-developers <python-ogre-developers@googlegroups.com>
Content-Type: multipart/alternative; boundary=001485f423f609cfb1048e1194e6

--001485f423f609cfb1048e1194e6
Content-Type: text/plain; charset=ISO-8859-1

Team

As you've no doubt noticed PythonOgre development has stabilised (or slowed
to a crawl based upon it being fairly complete :) )

I've been looking at future projects and wanted a little feedback/debate on
a couple to see if there is any interest (any thoughts would be welcome) --
and of course please add anything else you see fit to this thread....

*'Faster Python'*
1. *ShedSkin*:  A nice python to C++ 'compiler' - I helped out with the MSVC
support and have been thinking about how best to link PythonOgre modules
with it -- challenge is that it's unlikely to support a "complete" python
app due to a number of limitations -- however possibly ideal to create
'speed-up' modules.
2. *PYPY*: More of a JIT compiler which recently added a 'ctypes' style
interface -- I've done initial work to show that Boost can be compiled
against it and now looking at testing a module or two (OIS for example)

*'Something Different with GO'*
The GO language from google looks rather interesting, admittedly it's
intended for systems programing (which I like) so more complex than Python
(perhaps) -- for me it fills a middle ground between 'C' (which at times is
just too much work), Java (which I've never liked due to performance,
portability and the size of the library documentation -- much of which is
getting better), C++ (which I like 60% of but complex templates, STL, and
debugging multiple inheritance drive me nuts) and Python (which I'd like to
see as a compiled language, but appreciate the fantastic out of the box
usability)

Of course GO is lacking as there is currently no C++ interface or ability to
call existing C++ libraries, and the discussion I've seen is that SWIG will
be the wrapper of choice which is concerning from an Ogre perspective -- yes
there is a 'C' interface wrapper and from what I see this is currently
manual and not sure about the performance...

Would appreciate thoughts on Shedskin/Pypy/Go/etc, other random thoughts on
PythonOgre development in general, etc

Thanks
Andy

--001485f423f609cfb1048e1194e6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Team<div><br></div><div>As you&#39;ve no doubt noticed PythonOgre developme=
nt has stabilised (or slowed to a crawl based upon it being fairly complete=
 :) )</div><div><br></div><div>I&#39;ve been looking at future projects and=
 wanted a little feedback/debate on a couple to see if there is any interes=
t (any thoughts would be welcome) -- and of course please add anything else=
 you see fit to this thread....</div>
<div><br></div><div><b>&#39;Faster Python&#39;</b></div><div>1. <i>ShedSkin=
</i>: =A0A nice python to C++ &#39;compiler&#39; - I helped out with the MS=
VC support and have been thinking about how best to link PythonOgre modules=
 with it -- challenge is that it&#39;s=A0unlikely=A0to support a &quot;comp=
lete&quot; python app due to a number of limitations -- however possibly id=
eal to create &#39;speed-up&#39; modules.</div>
<div>2. <i>PYPY</i>: More of a JIT compiler which recently added a &#39;cty=
pes&#39; style interface -- I&#39;ve done initial work to show that Boost c=
an be compiled against it and now looking at testing a=A0module=A0or two (O=
IS for example)</div>
<div><br></div><div><b>&#39;Something Different with GO&#39;</b></div><div>=
The GO language=A0from google looks rather interesting,=A0admittedly=A0it&#=
39;s intended for systems programing (which I like) so more complex than Py=
thon (perhaps) -- for me it fills a middle=A0ground=A0between &#39;C&#39; (=
which at times is just too much work), Java (which=A0I&#39;ve never liked d=
ue to performance, portability and the size of the library documentation --=
 much of which is getting better), C++ (which I like 60% of but complex tem=
plates, STL, and debugging multiple=A0inheritance=A0drive me nuts) and Pyth=
on (which I&#39;d like to see as a compiled language, but appreciate the fa=
ntastic out of the box usability)</div>
<div><br></div><div>Of course GO is lacking as there is currently no C++ in=
terface or ability to call=A0existing=A0C++ libraries, and the discussion I=
&#39;ve seen is that SWIG will be the wrapper of choice which is concerning=
 from an Ogre perspective -- yes there is a &#39;C&#39; interface wrapper a=
nd from what I see this is currently manual and not sure about the performa=
nce...=A0<br>
</div><div><br></div><div>Would appreciate thoughts on Shedskin/Pypy/Go/etc=
, other random thoughts on PythonOgre development in general, etc</div><div=
><br></div><div>Thanks</div><div>Andy</div>

--001485f423f609cfb1048e1194e6--