Anand Balachandran Pillai wrote:
> Hi Amaury,
>
> This is the entry for _warnings.
>
> /* This lives in _warnings.c */
>{"_warnings", _PyWarnings_Init},
Did you find this in Modules/config.c?
> Btw, you said _warnings is not designed to be a .so module. So what type of
> module is _warnin
Hi Amaury,
This is the entry for _warnings.
/* This lives in _warnings.c */
{"_warnings", _PyWarnings_Init},
Btw, you said _warnings is not designed to be a .so module. So what type of
module is _warnings ?
Thanks
--Anand
On Fri, Jun 6, 2008 at 3:25 PM, Amaury Forgeot d'Arc <[EMAIL P
Anand Balachandran Pillai wrote:
> Hi Stefan,
>
> There are no build errors in the warnings module and _warnings.o is
> generated.
> However I looked at the make log and no _warnings.so is built by the
> linker. Instead
> _warnings.o is just archived into libpython3.0a.
...
Yes, _warnings is not
Hi Stefan,
There are no build errors in the warnings module and _warnings.o is
generated.
However I looked at the make log and no _warnings.so is built by the
linker. Instead
_warnings.o is just archived into libpython3.0a.
Cannot find any error in config.log either. I tried to check how
_warn
Amaury Forgeot d'Arc schrieb:
It seems that there are two problems here:
- First, there is a bug in the sys.flags structure: revision 62322
added a new flag in the underlying C structure, but did not increase
the number of fields visible from python code. This should be
corrected: in sysmodules.
Anand Balachandran Pillai wrote:
> After commenting out the code which catches the ImportError,
> this is the trace.
>
> [EMAIL PROTECTED] ~]$ python3
> Fatal Python error: Py_Initialize: can't initialize sys standard streams
> Traceback (most recent call last):
> File "/usr/local/lib/python3.0/
Hi Amaury,
After commenting out the code which catches the ImportError,
this is the trace.
[EMAIL PROTECTED] ~]$ python3
Fatal Python error: Py_Initialize: can't initialize sys standard streams
Traceback (most recent call last):
File "/usr/local/lib/python3.0/io.py", line 63, in
import war
Hello,
Anand Balachandran Pillai wrote:
> Hi,
>
>I have been getting the following persistent error with Python 3.0
> since an April 15 update of the subversion trunk (svn version 62349)
>
> I am running Fedora Core 6, with kernel 2.6.22.7-57.fc6 on
> an Intel i686 SMP box. Python was compile
Hi,
I have been getting the following persistent error with Python 3.0
since an April 15 update of the subversion trunk (svn version 62349)
I am running Fedora Core 6, with kernel 2.6.22.7-57.fc6 on
an Intel i686 SMP box. Python was compiled with gcc
version 4.1.2 (Redhat - 4.1.2-13). Python
