Re: Fatal Python error

2019-01-27 Thread songbird
Abdallah Adham wrote: > Hey > I am having this problem for about 2 weeks, I can't do anything, so please > give me some instructions so I can solve it. > > Fatal Python error: initfsencoding: unable to load the file system code. > ModuleNotFoundError: No module named 'encodings' > >:Current thread

Re: Fatal Python error

2016-08-31 Thread eryk sun
On Wed, Aug 31, 2016 at 9:04 AM, Wanderer <864483...@qq.com> wrote: > The system environment I alse configured.The Sigil project also build > successed. > But When I run the Sigil.exe that follow errors occured. > -- > Fatal Python error: Py_Initialize: unable to load the file syst

Re: Fatal Python error: PyCOND_WAIT(gil_cond) failed

2014-12-12 Thread dieter
keepplearningpython writes: > I am running ipython3 on Unix and constantly see this crash - > It happens when i try to issue commands on the ipython interactive shell. > > I have tried to set the PYTHONDIR to /var/tmp/ in case there was an issue > accessing the default location of the history fi

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-17 Thread alex23
On Jun 16, 2:09 pm, Larry Hudson wrote: > On 06/15/2013 03:10 PM, alex23 wrote: > > (Sorry for the ugly url, it's a Google translation of a french > > language page) > > Somewhat OT, but have you ever looked at tinyurl.com?  Very useful for this > sort of thing. >From past comments on this list,

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread Larry Hudson
On 06/15/2013 03:10 PM, alex23 wrote: On Jun 16, 7:29 am, lucabrasi...@gmail.com wrote: Here's a report of a similar issue with Blender (which also provides a local install of Python under Windows): http://translate.google.com.au/translate?hl=en&sl=fr&u=http://blenderclan.tuxfamily.org/html/m

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread Terry Reedy
On 6/15/2013 8:03 PM, MRAB wrote: On 15/06/2013 23:10, alex23 wrote: \__init__.py", line 123 raise CodecRegistryError,\ ^ SyntaxError: invalid syntax To me that traceback looks like it's Python 3 trying to run code written for Python 2. If that is the case, the ^ should be under the ',' (a

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread Dave Angel
On 06/15/2013 10:44 PM, lucabrasi wrote: On Saturday, June 15, 2013 5:03:27 PM UTC-7, MRAB wrote: On 15/06/2013 23:10, alex23 wrote: should be banned> Do you have a separate installation of Python? It's possible it may be conflicting. If you rename it's folder to something else

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread lucabrasi
On Saturday, June 15, 2013 7:44:09 PM UTC-7, lucabrasi wrote: > On Saturday, June 15, 2013 5:03:27 PM UTC-7, MRAB wrote: > > > On 15/06/2013 23:10, alex23 wrote: > > > > > > > On Jun 16, 7:29 am, lucabrasi...@gmail.com wrote: > > > > > > >> I get this error when I try to save .dxf files in I

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread lucabrasi
On Saturday, June 15, 2013 5:03:27 PM UTC-7, MRAB wrote: > On 15/06/2013 23:10, alex23 wrote: > > > On Jun 16, 7:29 am, lucabrasi...@gmail.com wrote: > > >> I get this error when I try to save .dxf files in Inkscape: > > >> > > >> Fatal Python error: Py_Initialize: can't initialize sys standard

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread MRAB
On 15/06/2013 23:10, alex23 wrote: On Jun 16, 7:29 am, lucabrasi...@gmail.com wrote: I get this error when I try to save .dxf files in Inkscape: Fatal Python error: Py_Initialize: can't initialize sys standard streams Then it seems to recover but it doesn't really recover. It saves the files a

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread lucabrasi
On Saturday, June 15, 2013 3:10:07 PM UTC-7, alex23 wrote: > On Jun 16, 7:29 am, lucabrasi...@gmail.com wrote: > > > I get this error when I try to save .dxf files in Inkscape: > > > > > > Fatal Python error: Py_Initialize: can't initialize sys standard streams > > > > > > Then it seems to rec

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread alex23
On Jun 16, 7:29 am, lucabrasi...@gmail.com wrote: > I get this error when I try to save .dxf files in Inkscape: > > Fatal Python error: Py_Initialize: can't initialize sys standard streams > > Then it seems to recover but it doesn't really recover. It saves the files > and then DraftSite won't ope

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread alex23
On Jun 16, 7:43 am, Mark Lawrence wrote: > Your Python version would help :)  How did you install Inkscape?  It > looks strange to see it in Program Files, I'd normally expect to see it > in the site packages directory. Inkscape is an application, not a library. It provides its own local install

Re: Fatal Python error: Py_Initialize: can't initialize sys standard streams

2013-06-15 Thread Mark Lawrence
On 15/06/2013 22:29, lucabrasi...@gmail.com wrote: I get this error when I try to save .dxf files in Inkscape: Fatal Python error: Py_Initialize: can't initialize sys standard streams Then it seems to recover but it doesn't really recover. It saves the files and then DraftSite won't open them.

Re: Fatal Python error

2013-05-31 Thread nn
On May 29, 10:05 am, Joshua Landau wrote: > On 29 May 2013 14:02, Dave Angel wrote: > > > On 05/29/2013 08:45 AM, Oscar Benjamin wrote: > > Joshua:  Avoid doing anything complex inside an exception handler. > > Unfortunately, Ranger (the file manager in question) wraps a lot of stuff > in one big

Re: Fatal Python error

2013-05-29 Thread Oscar Benjamin
On 29 May 2013 14:02, Dave Angel wrote: > On 05/29/2013 08:45 AM, Oscar Benjamin wrote: > > More likely a bug in the 2.x interpreter. Once inside an exception handler, > that frame must be held somehow. If not on the stack, then in some separate > list. So the logic will presumably fill memory,

Re: Fatal Python error

2013-05-29 Thread rusi
On May 29, 5:43 pm, Joshua Landau wrote: > On 29 May 2013 13:25, Dave Angel wrote: > > > On 05/29/2013 07:48 AM, Joshua Landau wrote: > > >> Hello all, again. Instead of revising like I'm meant to be, I've been > >> delving into a bit of Python and I've come up with this code: > > > To start with

Re: Fatal Python error

2013-05-29 Thread Joshua Landau
On 29 May 2013 14:02, Dave Angel wrote: > On 05/29/2013 08:45 AM, Oscar Benjamin wrote: > Joshua: Avoid doing anything complex inside an exception handler. Unfortunately, Ranger (the file manager in question) wraps a lot of stuff in one big exception handler. Hence there isn't much choice. The

Re: Fatal Python error

2013-05-29 Thread Marcel Rodrigues
I think the issue here has little to do with classes/objects/properties. See, for example, the code posted by Oscar Benjamin. What that code is trying to do is similar to responding to an "Out Of Memory" error with something that might require more memory allocation. Even if we consider the Py3 b

Re: Fatal Python error

2013-05-29 Thread Joshua Landau
On 29 May 2013 13:30, Marcel Rodrigues wrote: > > I just tried your code with similar results: it does nothing on PyPy 2.0.0-beta2 and Python 2.7.4. But on Python 3.3.1 it caused core dump. > It's a little weird but so is the code. You have defined a function that calls itself unconditionally. Thi

Re: Fatal Python error

2013-05-29 Thread Dave Angel
On 05/29/2013 08:45 AM, Oscar Benjamin wrote: On 29 May 2013 12:48, Joshua Landau wrote: Hello all, again. Instead of revising like I'm meant to be, I've been delving into a bit of Python and I've come up with this code: Here's a simpler example that gives similar results: $ py -3.3 Python 3

Re: Fatal Python error

2013-05-29 Thread Oscar Benjamin
On 29 May 2013 12:48, Joshua Landau wrote: > Hello all, again. Instead of revising like I'm meant to be, I've been > delving into a bit of Python and I've come up with this code: Here's a simpler example that gives similar results: $ py -3.3 Python 3.3.2 (v3.3.2:d047928ae3f6, May 16 2013, 00:03:

Re: Fatal Python error

2013-05-29 Thread Joshua Landau
On 29 May 2013 13:25, Dave Angel wrote: > On 05/29/2013 07:48 AM, Joshua Landau wrote: > >> Hello all, again. Instead of revising like I'm meant to be, I've been >> delving into a bit of Python and I've come up with this code: >> >> > To start with, please post in text mode. By using html, you'v

Re: Fatal Python error

2013-05-29 Thread Marcel Rodrigues
I just tried your code with similar results: it does nothing on PyPy 2.0.0-beta2 and Python 2.7.4. But on Python 3.3.1 it caused core dump. It's a little weird but so is the code. You have defined a function that calls itself unconditionally. This will cause a stack overflow, which is a RuntimeErro

Re: Fatal Python error

2013-05-29 Thread Dave Angel
On 05/29/2013 07:48 AM, Joshua Landau wrote: Hello all, again. Instead of revising like I'm meant to be, I've been delving into a bit of Python and I've come up with this code: To start with, please post in text mode. By using html, you've completely messed up any indentation you presumably

Re: "Fatal Python Error" Need Help

2011-04-19 Thread Ned Deily
In article , Yogesh Gupta wrote: > I am trying to run a python based program on MacOSX, which needs following > packages > > numpy > PIL > matplotlib > > I can successfully import all 3 using python2.5 (only using /sw64/bin/python > or /sw64/bin/python2.5) , although i have python2.6 and 2.7 in

Re: Fatal Python error: ceval: tstate mix-up

2009-01-09 Thread Laszlo Nagy
Meanwhile I'm trying to turn off threads in that program one by one. I just got this new type of error: Fatal Python error: PyThreadState_Delete: invalid tstate -- http://mail.python.org/mailman/listinfo/python-list

Re: Fatal Python error: ceval: tstate mix-up

2009-01-09 Thread Laszlo Nagy
I could start "gdb python python.core" but don't know what it means. Unfortunately, there are no debugging symbols. %gdb /usr/local/bin/python python.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and yo

Re: Fatal Python error using ctypes & python exceptions

2007-08-31 Thread Thomas Heller
mmacrobert schrieb: > Hi Everyone, > I've created a 'C' dll that is accessed via ctypes library containing > a bunch of functions. I've successfully been able to use the > functions. However, I would like to throw python exceptions from some > of them. > > I throw them using: ::PyErr_SetString(::P

Re: Fatal Python error: deallocating None

2006-10-26 Thread Fredrik Lundh
Gabriel Genellina wrote: > Mmm, it appears that one of these C extensions isn't managing the ref > count correctly - perhaps there is a return Py_None without a previous > Py_INCREF? If None were returned in certain functions to indicate > failure or something exceptional - and not a regular co

Re: Fatal Python error: deallocating None

2006-10-25 Thread Gabriel Genellina
At Wednesday 25/10/2006 21:28, George Sakkis wrote: It's the first time in the three years I've been using python that a program crashes without a nice traceback to give me a clue of what might be wrong. After searching a little, it seems it's one of those hard to get down to cases, so I've no i

Re: Fatal Python error: deallocating None

2006-10-25 Thread Chetan
"Delaney, Timothy (Tim)" <[EMAIL PROTECTED]> writes: > George Sakkis wrote: > > > What makes the problem worse is that it's not deterministic; I can > > restart it from (a little before) the point of crash and it doesn't > > happen again at the same point, but it might happen further down. Now, >

RE: Fatal Python error: deallocating None

2006-10-25 Thread Delaney, Timothy (Tim)
George Sakkis wrote: > What makes the problem worse is that it's not deterministic; I can > restart it from (a little before) the point of crash and it doesn't > happen again at the same point, but it might happen further down. Now, > I wouldn't mind restarting it manually every time since the cra

Re: Fatal Python error: Py_EndInterpreter: thread still has a frame

2006-02-04 Thread [EMAIL PROTECTED]
Thomas Korimort wrote: > Hi! > > Does anyone know the precise circumstances when the error > > "Fatal Python error: Py_EndInterpreter: thread still has a frame" > > does occur. I checked the source code of pythonrun.c, which tells me > that this error message is thrown in Py_EndInterpreter, when >