Benjamin Peterson wrote:
1. Switch the initialization order back to the original (io streams
first) and compile _bytesio and _stringio directly into the Python
binary. This is probably the easiest option.
Oh, the modules are still shared libraries? That's clearly a mistake. It
makes no sense t
On Fri, Sep 5, 2008 at 4:51 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
> Benjamin Peterson gmail.com> writes:
>>
>> That options as I see it are:
>> 1. Switch the initialization order back to the original (io streams
>> first) and compile _bytesio and _stringio directly into the Python
>> binar
Benjamin Peterson gmail.com> writes:
>
> That options as I see it are:
> 1. Switch the initialization order back to the original (io streams
> first) and compile _bytesio and _stringio directly into the Python
> binary. This is probably the easiest option.
Since io.py imports _bytesio and _strin
In a checkout, site.py is currently responsible for adding the
distutils extension module builddir to sys.path. Usually, this is
unproblematic. However, when the initialization code needed by site
(in this case the standard io streams and the builtin open) relies on
C modules added from the builddi
