Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #100228 > unrolled thread

SystemError in python 2.5.4

Started byPalpandi <palpandi111@gmail.com>
First post2015-12-10 03:29 -0800
Last post2015-12-11 09:38 +0100
Articles 6 — 4 participants

Back to article view | Back to comp.lang.python


Contents

  SystemError in python 2.5.4 Palpandi <palpandi111@gmail.com> - 2015-12-10 03:29 -0800
    Re: SystemError in python 2.5.4 Chris Angelico <rosuav@gmail.com> - 2015-12-10 22:37 +1100
      Re: SystemError in python 2.5.4 Palpandi <palpandi111@gmail.com> - 2015-12-10 05:14 -0800
        Re: SystemError in python 2.5.4 Chris Angelico <rosuav@gmail.com> - 2015-12-11 00:25 +1100
    Re: SystemError in python 2.5.4 Steven D'Aprano <steve@pearwood.info> - 2015-12-11 19:21 +1100
    Re: SystemError in python 2.5.4 dieter <dieter@handshake.de> - 2015-12-11 09:38 +0100

#100228 — SystemError in python 2.5.4

FromPalpandi <palpandi111@gmail.com>
Date2015-12-10 03:29 -0800
SubjectSystemError in python 2.5.4
Message-ID<5ad8e3de-4ebb-4d60-b106-cd12fdafc0c3@googlegroups.com>
Hi All,

I am getting the error mentioned below in python 2.5.4.

SystemError: \loewis\25\python\Objects\longobject.c:225: bad argument to internal function.

I also ran the same code in python 2.7.
There I am not getting this error.

I don't know which causes this error. Any solution for this?

Note: The error is coming from the method call findall(path).


Thanks.

[toc] | [next] | [standalone]


#100229

FromChris Angelico <rosuav@gmail.com>
Date2015-12-10 22:37 +1100
Message-ID<mailman.111.1449747470.12405.python-list@python.org>
In reply to#100228
On Thu, Dec 10, 2015 at 10:29 PM, Palpandi <palpandi111@gmail.com> wrote:
> Hi All,
>
> I am getting the error mentioned below in python 2.5.4.
>
> SystemError: \loewis\25\python\Objects\longobject.c:225: bad argument to internal function.
>
> I also ran the same code in python 2.7.
> There I am not getting this error.
>
> I don't know which causes this error. Any solution for this?
>
> Note: The error is coming from the method call findall(path).
>

Interesting! What platform (OS, etc) are you running this on? Python
2.5 isn't supported any more, so you might have to talk to Red Hat or
someone. Alternatively, given that 2.7 doesn't have this problem, can
you simply write it off as an issue with the older Python, and use 2.7
instead?

ChrisA

[toc] | [prev] | [next] | [standalone]


#100231

FromPalpandi <palpandi111@gmail.com>
Date2015-12-10 05:14 -0800
Message-ID<f876a5da-f891-41ab-9752-2001fbac3cb5@googlegroups.com>
In reply to#100229
On Thursday, December 10, 2015 at 5:08:05 PM UTC+5:30, Chris Angelico wrote:
> On Thu, Dec 10, 2015 at 10:29 PM, Palpandi <palpandi111@gmail.com> wrote:
> > Hi All,
> >
> > I am getting the error mentioned below in python 2.5.4.
> >
> > SystemError: \loewis\25\python\Objects\longobject.c:225: bad argument to internal function.
> >
> > I also ran the same code in python 2.7.
> > There I am not getting this error.
> >
> > I don't know which causes this error. Any solution for this?
> >
> > Note: The error is coming from the method call findall(path).
> >
> 
> Interesting! What platform (OS, etc) are you running this on? Python
> 2.5 isn't supported any more, so you might have to talk to Red Hat or
> someone. Alternatively, given that 2.7 doesn't have this problem, can
> you simply write it off as an issue with the older Python, and use 2.7
> instead?
> 
> ChrisA

ChrisA, Thanks for your quick response. 
I am using Windows and we are using 2.5.4 only.
Is there any workaround?

[toc] | [prev] | [next] | [standalone]


#100232

FromChris Angelico <rosuav@gmail.com>
Date2015-12-11 00:25 +1100
Message-ID<mailman.112.1449753958.12405.python-list@python.org>
In reply to#100231
On Fri, Dec 11, 2015 at 12:14 AM, Palpandi <palpandi111@gmail.com> wrote:
> ChrisA, Thanks for your quick response.
> I am using Windows and we are using 2.5.4 only.
> Is there any workaround?

I wouldn't know. All I know is, upgrading to 2.7 gives you a lot of
other improvements too, so unless there's something serious holding
you back, move forward!

ChrisA

[toc] | [prev] | [next] | [standalone]


#100253

FromSteven D'Aprano <steve@pearwood.info>
Date2015-12-11 19:21 +1100
Message-ID<566a8783$0$1595$c3e8da3$5496439d@news.astraweb.com>
In reply to#100228
On Thu, 10 Dec 2015 10:29 pm, Palpandi wrote:

> Hi All,
> 
> I am getting the error mentioned below in python 2.5.4.
> 
> SystemError: \loewis\25\python\Objects\longobject.c:225: bad argument to
> internal function.

Sounds like your installation of Python is broken. You should never get an
internal error like that.

If it was working, and now isn't, I would strongly suspect the application
has been corrupted, or possibly infected by a virus. I would start with a
virus scan and a disk check, and after fixing any faults that come up,
re-install Python 2.5 (or upgrade to 2.7, which is much better).



-- 
Steven

[toc] | [prev] | [next] | [standalone]


#100254

Fromdieter <dieter@handshake.de>
Date2015-12-11 09:38 +0100
Message-ID<mailman.129.1449823103.12405.python-list@python.org>
In reply to#100228
Palpandi <palpandi111@gmail.com> writes:

> I am getting the error mentioned below in python 2.5.4.
>
> SystemError: \loewis\25\python\Objects\longobject.c:225: bad argument to internal function.
>
> I also ran the same code in python 2.7.
> There I am not getting this error.
>
> I don't know which causes this error. Any solution for this?
>
> Note: The error is coming from the method call findall(path).

I do not have the code for Python 2.5.4 around - therefore,
I looked into that for Python 2.4.6. Based on this (older) version,
the "SystemError" above may come from the "PyLong_AsLong" function
(converting a Python "long" into a "C" "long"). In this case,
the error would be caused by provding a wrong parameter
(neither Python "int" nor Python "long") to "PyLong_AsLong".

At your place, I would have a look at the Python 2.5.4 code
and check there where precisely the "SystemError" comes from.
Then I would try to find out why it gets wrong (this might
require the use of a "C" level debugger).

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web