Re: Frustrated trying to build beecrypt & rpm on a Debian system whereI'm not root

["Paul Johnson" <pauljohn32 gmail com>]

On Nov 25, 2007 11:41 AM, Mike Meyer <mwm-keyword-rpm 43b295 mired org> wrote:
> On Sun, 25 Nov 2007 06:31:58 -0500 "Johri, Mayank (GTI)" <mayank_johri ml com> wrote:
>
> > Paul,
> >
> > It should be
> > from os.path import curdir,... Instead of from os.path import (curdir,
>
> The "(curdir, ..." is from python 2.5, and causes the next line to be
> a continuation line (standard python parsing: an open paren always
> does that). That is, it probably said something like:
>
> from os.path import (curdir, pardir, sep, pathsep, defpath, extsep,
>       altsep, join)
>
> and you'll want to change it to
>
> from os.path import curdir, pardir, sep, pathsep, defpath, extsep, altsep, join
>
> or
>
> from os.path import curdir, pardir, sep, pathsep, defpath, extsep, \
>       altsep, join
>
> Of course, that this is in their sources means they haven't tested
> against 2.4, so you may encounter more such problems. In this case,
> the "What's new in 2.5" (http://docs.python.org/whatsnew/whatsnew25.html)
> is probably worth reading.
>
>    <mike
>

Wait a minute. The error is not in my python code. It is in the python
library itself.   This one:

>From /usr/lib/python2.4/os.py

sys.modules['os.path'] = path
from os.path import (curdir, pardir, sep, pathsep, defpath, extsep, altsep,
    devnull)

If RPM did compile against python2.4, then why is this cropping up now?

pj

-- 
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas