Message from discussion Pheonix buildbot update
Received: by 10.52.24.68 with SMTP id s4mr2190827vdf.3.1337198245375;
Wed, 16 May 2012 12:57:25 -0700 (PDT)
Received: by 10.220.153.198 with SMTP id l6ls281905vcw.6.gmail; Wed, 16 May
2012 12:57:24 -0700 (PDT)
Received: by 10.52.19.110 with SMTP id d14mr223468vde.10.1337198244857; Wed,
16 May 2012 12:57:24 -0700 (PDT)
Authentication-Results: ls.google.com; spf=pass (google.com: domain of
wxjmfa...@gmail.com designates internal as permitted sender)
Received: by v24g2000vbx.googlegroups.com with HTTP; Wed, 16 May 2012 12:57:24
Date: Wed, 16 May 2012 12:57:24 -0700 (PDT)
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:220.127.116.11)
Subject: Re: Pheonix buildbot update
From: jmfauth <wxjmfa...@gmail.com>
To: wxPython-dev <wxPythonemail@example.com>
Content-Type: text/plain; charset=ISO-8859-1
On 19 avr, 20:02, Robin Dunn <ro...@alldunn.com> wrote:
> Hi all,
> Just a quick note to let you know that I've been working on getting the
> Phoenix buildbot doing more for us than just a simple build on a single
> platform. =A0It's now got build slaves on OSX, Windows and Ubuntu. =A0I'v=
> also added builders that will run once daily for making a tarball with
> binaries for OSX and Windows, and also a once daily builder that will
> build the docs and make a tarball of them.
> You can view the buildbot waterfall, build logs, etc. athttp://buildbot.w=
xpython.org:8010. =A0The tarballs are uploaded tohttp://wxpython.org/Phoeni=
x/snapshot-builds/after they have been created.
>  There are no new OSX binaries on the server yet as that build slave
> had a problem which has just been resolved. =A0I'll trigger a new dist
> build once the current normal build succeeds.
>  Just the docs for the core modules are being built so far since
> wx.lib and etc. hasn't been copied into the Phoenix source tree yet.
> Robin Dunn
> Software Craftsmanhttp://wxPython.org
I am afraid, it is completely wrong by design. And it
For some reasons I can not explain, there is in this "coding of
the characters" field, something you do not get correctly.
If Xe(La)TeX were working in that way, it would be impossible
to produce a piece of text -- documents -- correctly. Why XeTeX
as exemple? To take something different and interestingly XeTeX is
working exactly as Python does!
I see and foresee what you are doing and expecting. Unfortunately,
it is impossible. You do not deeply realize this.
Among other things, you have wrongly reimplemented something
that Python (2) is already able to do. And it does it correctly!
from __future__ import unicode_literals