Re: [Cooker] noarch python packages shared berween i586 and x86_64 ?

[Michael Scherer]

On Sunday 22 May 2005 16:34, Olivier Thauvin wrote:
> Le Sunday 22 May 2005 15:43, Gaetan Lehmann a écrit :
> > Hi !
> >
> > I tried to use ipython on a x86_64 cooker and I get :
> >
> > [gaetan@hop SPECS]$ ipython
> > Traceback (most recent call last):
> >   File "/usr/bin/ipython", line 26, in ?
> >     import IPython
> > ImportError: No module named IPython
> >
> >
> > ipyhon is not installed in /usr/lib/python2.4, but python is
> > in /usr/lib64/python2.4
> > I suppose ipython is in /usr/lib/python2.4 because it is tagged as
> > noarch
> >
> > Shouldn't we have a file noarch.pth in
> > /usr/lib64/python2.4/site-packages with
> > "/usr/lib/python2.4/site-packages" in it to be able to use noarch
> > packages ? Can it be a problem if .so files or in
> > /usr/lib/python2.4/ ?
>
> This problem is know, but the only way find by Gwenole was to rebuild
> noarch rpm on amd64 and duplicate it on mirrors.
>
> This should be fix in python package IMHO. Workaround: don't tag
> python package as noarch and let it rebuild by bot.

Or use this :
~ $ ssh sisay cat /etc/profile.d/fix_python_path.sh 
#!/bin/bash
export PYTHONPATH="/usr/lib/python2.4/site-packages/:$PYTHONPATH"

~ $ ssh sisay uname -a  
Linux sisay.ephaone.org 2.6.11-6mdk #1 Tue Mar 22 10:20:32 EST 2005 
x86_64 AMD Athlon(tm) 64 Processor 3000+ unknown GNU/Linux

However, i never tried to install a .so compiled for i586.

> BTW: a noarch package should works on all arch, if the path change,
> so it should not be a noarch... that's my point.

The problem is that Python use the same directory for compiled C module 
and python module.
And there is no distinction for this in the distutils modules ( at least 
for installation. ).

Maybe a more knowledgeable pythonist ( like gustavo ) can enligthen us ?


-- 
Michaël Scherer

On the importance to respond to proposal email :
http://www.nntp.perl.org/group/perl.bootstrap/1127