On 8/5/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> See bugs #1548891 and #1730114.
>
> In the former, it was reported that cStringIO works differently from StringIO
> when handling unicode strings; it used GetReadBuffer which returned the raw
> internal UCS-2 or UCS-4 encoded string.
>
> I change
> See bugs #1548891 and #1730114.
>
> In the former, it was reported that cStringIO works differently from StringIO
> when handling unicode strings; it used GetReadBuffer which returned the raw
> internal UCS-2 or UCS-4 encoded string.
>
> I changed it to use GetCharBuffer, which converts to a st
Hello Martin,
> > You mean I should list all of these in "Modules/Setup"?
> Exactly so. They are already listed - just uncomment them all
> (with proper command line flags and libraries where necessary).
OK, I will try to get it compiled and tested.
Meanwhile, you asked so:
> I still don't unders
Methinks that this was a fundamental limitation of cStringIO, not a
bug. Certainly not something to be "fixed" in a bugfix release.
On 8/5/07, Georg Brandl <[EMAIL PROTECTED]> wrote:
> See bugs #1548891 and #1730114.
>
> In the former, it was reported that cStringIO works differently from StringI
See bugs #1548891 and #1730114.
In the former, it was reported that cStringIO works differently from StringIO
when handling unicode strings; it used GetReadBuffer which returned the raw
internal UCS-2 or UCS-4 encoded string.
I changed it to use GetCharBuffer, which converts to a string using the
On 8/4/07, Jeffrey Yasskin <[EMAIL PROTECTED]> wrote:
> Well, regardless of the brokenness of the patch, I do get two
> different failures from this test on OSX. The first is caused by
> trying to socket.bind() a port that's already been bound recently:
> That looks pretty easy to fix.
It was fix
>> 2. Don't use extension modules. Edit Modules/Setup to statically link
>>all extension modules into the interpreter binary.
> This is the way. But how to do that?
>
> Shell output:
> ../configure --disable-shared
--disable-shared should be the default, so you don't need to specify
it explic
Hello Martin,
Thanks very much for answering.
> As for the static vs. shared libpython: On Unix, Python is typically
> built as a single executable (only linked shared with the system
> libraries). The challenge is then with extension modules, which are
> shared libraries. In particular, it is a c
